[UIMA-1658] UIMA AS worker does not respond to client initialize after failover

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.3AS
• Component/s: Async Scaleout

Environment

Ubuntu 8.10 Server, Java 1.6 and ActiveMQ 5.3.0

• Assignee: Unassigned
• Reporter: Jörn Kottmann
• Created: 11/Nov/09 14:01
• Updated: 30/Nov/10 16:40
• Resolved: 30/Nov/10 16:40

Description

A Pure Master Slave Broker is used to increase availability of the broker.
More information about it can be found in the activemq documentation:
http://activemq.apache.org/pure-master-slave.html

In a test we simulated Master failure through killing the process with kill -9.

Here is the log output from the worker node:
INFO FailoverTransport - Successfully connected to tcp://XXX1:61616

Here I stopped the master broker process with kill -9

WARN FailoverTransport - Transport failed to tcp://XXX1:61616 , attempting to automatically reconnect due to: java.io.EOFException
WARN FailoverTransport - Transport failed to tcp://XXX1:61616 , attempting to automatically reconnect due to: java.io.EOFException
WARN FailoverTransport - Transport failed to tcp://XXX1:61616 , attempting to automatically reconnect due to: java.io.EOFException
INFO FailoverTransport - Successfully reconnected to tcp://XXX2:61616
INFO FailoverTransport - Successfully reconnected to tcp://XXX2:61616
INFO FailoverTransport - Successfully reconnected to tcp://XXX2:61616

Afterwards the client was restarted but got a time out error during initialize.
During initializes it sends a message to the worker nodes input queue, but this
message if never retrieved.

I used the activemq web interface to get some information about the message:
Command 2001
MessageFrom ID:XXXX-51032-1257865414664-0:1:1
ServerURI failover:(tcp://XXX1:61616,tcp://XXX2:61616)?randomize=false
MessageType 3000