Problem with resending messages for JMS bridge configuration

[armsargis_sargis]

Hi all, I am using:

INFO  BrokerService                  - ActiveMQ 5.3.0.0-fuse JMS Message Broker (localhost) is starting

and have problem with JMS bridge configuration. I've defined my factories following way:

and it works fine if I first start remote ActiveMQ 5.2 server after local FUSE server, all messages are forwarded without any problem. But when I stop both servers and start local its started with exception(which is normal):

INFO  FailoverTransport              - Failover timed out after 30022ms

ERROR JmsQueueConnector              - Failed to initialize the JMSConnector

javax.jms.JMSException: Failover timeout of 3000 ms reached

after I start remote server and I have in bridge side console following:

INFO  FailoverTransport              - Successfully connected to tcp://192.168.100.78:61616

now if I try to send messages, all messages are remained in local server queue and JMS bridge stoped to work. I've attached fuse config file as well, hope it will help.

Thanks in advance.

Edited by: armsargis on Apr 10, 2009 12:14 PM

Edited by: armsargis on Apr 10, 2009 12:16 PM

[armsargis_sargis]

it seams problem in JmsQueueConnector class if in

    public boolean init() {

        boolean result = super.init();

        if (result) {

            try {

                initializeForeignQueueConnection();

                initializeLocalQueueConnection();

                initializeInboundJmsMessageConvertor();

                initializeOutboundJmsMessageConvertor();

                initializeInboundQueueBridges();

                initializeOutboundQueueBridges();

            } catch (Exception e) {

                LOG.error("Failed to initialize the JMSConnector", e);

            }

        }

        return result;

    }

initializeForeignQueueConnection() throws exception like:

INFO  FailoverTransport              - Failover timed out after 3001ms

ERROR JmsQueueConnector              - Failed to initialize the JMSConnector

javax.jms.JMSException: Failover timeout of 3000 ms reached.

     at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:62)

     at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1266)

     at org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1350)

     at org.apache.activemq.ActiveMQConnection.start(ActiveMQConnection.java:495)

     at org.apache.activemq.network.jms.JmsQueueConnector.initializeForeignQueueConnection(JmsQueueConnector.java:216)

     at org.apache.activemq.network.jms.JmsQueueConnector.init(JmsQueueConnector.java:54)

     at org.apache.activemq.network.jms.JmsConnector.start(JmsConnector.java:116)

     at org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:1872)

     at org.apache.activemq.broker.BrokerService.start(BrokerService.java:474)

     at org.apache.activemq.xbean.XBeanBrokerService.afterPropertiesSet(XBeanBrokerService.java:56)

it means the rest method is not executed and bridges is not initialized,  and there is no any scheduler or listener if connection is up try to reinit JmsQueueConnector

[socallag]

Thanks for the feedback, we will look into reproducing this with a unit test (unless you already have one?) and raising a JIRA with AMQ

[socallag]

Hi,

We have confirmed this is a bug, the AMQ JIRA bug no. is http://fusesource.com/issues/browse/MB-470

[armsargis_sargis]

Thanks a lot for response