Uploaded image for project: 'ZZZ-WSO2 ESB'
  1. ZZZ-WSO2 ESB
  2. ESBJAVA-1821

Error was thrown continuously when one message broker instance is down.

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Highest
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.6.0
    • Component/s: Message Stores
    • Labels:
      None
    • Environment:

      ESB 4.0.6 + ActiveMQ 5.1.1

    • Severity:
      Blocker
    • Estimated Complexity:
      Moderate
    • Test cases added:
      Yes

      Description

      Basically we started two activeMQ instances and created two proxies to accept messages via HTTP and send them to JMS queues. And created JMS proxies which listen to the JMS queues and consume messages. After setting up this environment, we shutdown one activeMQ instance and check the queues by sending message to both queues. As we have observed, active queue is behaving correctly. To verify ESB hanging issues, we restarted the ESB and send messages again. The active queue is performing well even under this situation. However we have seen connection refuse exception on server console continuously. And ESB management console was accessible even backend is throwing continuous error. So we haven't got the same connection dropping issue with broker instance. However you should see the same continuous connection message on ESB console. So I suspect some loggin configuration might hiding those errors in your environment.

      Exception
      ========
      [2013-02-27 19:43:03,336] ERROR - NativeWorkerPool Uncaught exception
      org.apache.axis2.transport.jms.AxisJMSException: Error acquiring a JMS connection to : QueueConnectionFactory using JNDI properties :

      {java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory, java.naming.provider.url=tcp://localhost:61617, transport.jms.DestinationType=queue, transport.jms.ConnectionFactory=myQueueConnectionFactory2, transport.jms.ConnectionFactoryType=queue, serviceType=proxy}

      at org.apache.axis2.transport.jms.ServiceTaskManager.handleException(ServiceTaskManager.java:1000)
      at org.apache.axis2.transport.jms.ServiceTaskManager.access$700(ServiceTaskManager.java:50)
      at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.createConnection(ServiceTaskManager.java:835)
      at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.getConnection(ServiceTaskManager.java:706)
      at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.receiveMessage(ServiceTaskManager.java:496)
      at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.run(ServiceTaskManager.java:420)
      at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:173)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      at java.lang.Thread.run(Thread.java:662)
      Caused by: javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61617. Reason: java.net.ConnectException: Connection refused
      at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:35)
      at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:286)
      at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:230)
      at org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:178)
      at org.apache.axis2.transport.jms.JMSUtils.createConnection(JMSUtils.java:555)
      at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.createConnection(ServiceTaskManager.java:824)
      ... 7 more

        Attachments

          Activity

            People

            • Assignee:
              shafreen@wso2.com shafreen anfar
              Reporter:
              krishantha@wso2.com krishantha Samaraweera
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: