Uploaded image for project: 'Mule'
  1. Mule
  2. MULE-5755

JMS Reconnection fails due to inconsistent connector lifecycle state

    Details

    • User impact:
      High
    • Log Output:
      Hide
      testing with ActiveMQ:

      ERROR 2011-08-26 12:47:44,052 [MuleServer.2] org.mule.transport.jms.activemq.ActiveMQJmsConnector: org.mule.api.lifecycle.CreateException: Failed to schedule work with the Work manager
      ERROR 2011-08-26 12:48:12,048 [MuleServer.2] org.mule.retry.notifiers.ConnectNotifier: Failed to connect/reconnect: ActiveMQJmsConnector
      Show
      testing with ActiveMQ: ERROR 2011-08-26 12:47:44,052 [MuleServer.2] org.mule.transport.jms.activemq.ActiveMQJmsConnector: org.mule.api.lifecycle.CreateException: Failed to schedule work with the Work manager ERROR 2011-08-26 12:48:12,048 [MuleServer.2] org.mule.retry.notifiers.ConnectNotifier: Failed to connect/reconnect: ActiveMQJmsConnector
    • Similar Issues:

      Description

      When the jms broker is ungracefully shut down, during the connector stop phase a JMSException is thrown that then is wrapped as a StopException that leaves the connector in "start" state.
      Once the broker is up again and the connector is reconnected, is not being started again as its status is already "start". This is causing NPEs because the halfway executed stop process managed to close the scheduler.

        Attachments

          Activity

            People

            • Assignee:
              svacas Santiago Vacas
              Reporter:
              svacas Santiago Vacas
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Fix Release Date:
                12/Sep/11