Fwd: (AMQ-2114) & (AMQCPP-545)

[savita <sa...@gmail.com>]

---------- Forwarded message ----------
From: savita <sa...@gmail.com>
Date: Mon, Feb 16, 2015 at 6:18 PM
Subject: (AMQ-2114) & (AMQCPP-545)
To: tim.bish@redhat.com


Hi Tim,

I am having issues discussed in the 2 defects (AMQ-2114) & (AMQCPP-545)
(AMQ-2114) Failover transport should not hang on startup if it cannot
connect

(AMQCPP-545) Failover transport timeout options should only operate on
Message sends.

If AMQ is down while on startup, the reconnect strategy does not work and
blocks there forever.
To overcome this blocking issue, we are setting timeout on the broker. But,
this will throw a Failover timeout exception.

Once this exception occurs, the mule server is not able to deploy the
applications which are depending on this connection. However, we have no
issues if the connection goes down after the applications are deployed. The
applications successfully reconnect to AMQ once, the connection is up.

*This problem is happening if the mule server is started while the AMQ is
down. The applications fail to get deployed despite the <reconnect-forever
blocking="false" frequency="3000"/> strategy. This is because of the
Failover timeout exception.*

Here is the part of log:
Caused by: java.io.IOException: Failover timeout of 30000 ms reached.
        at
org.apache.activemq.transport.failover.FailoverTransport.oneway(FailoverTransport.java:532)
        at
org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:40)
        at
org.apache.activemq.transport.ResponseCorrelator.asyncRequest(ResponseCorrelator.java:81)
        at
org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorrelator.java:86)
        at
org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1284)

Please, help me with the fix. We are using Unix servers.

Let me know if you need more information.

-- 
Rgds,
Savita Eli



-- 
Rgds,
Savita Eli