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:
      MULE-5354A failed connector ends up in a state where it can not reconnect
      MULE-5124ActiveMQ connectors fail to reconnect after JMS server restart
      MULE-3446StackOverflowError reconnecting JMS through SimplyRetryConnectionStrategy
      MULE-7110Improve jms transport to support reconnection at the endpoint level
      MULE-5653Weblogic JMS transport, error in the reconnection to JMS
      MULE-2241Failed to create JMS connector & ReconnectStrategy
      MULE-5564Periodic errors after JMS reconnect
      MULE-8471Race condition on <reconnect-forever> and deployment lifecycle
      MULE-2980Connector lifecycle needs clarification
      MULE-1041Misleading exception message due to missing MQ jars

      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.

        Activity

        Santiago Vacas created issue -
        Santiago Vacas made changes -
        Field Original Value New Value
        Link This issue relates to EE-1858 [ EE-1858 ]
        Santiago Vacas made changes -
        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".
        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.
        Santiago Vacas made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Santiago Vacas made changes -
        Fix Version/s 3.1.3 [ 10988 ]
        Fix Version/s 3.2.0 [ 10942 ]
        Santiago Vacas made changes -
        Status In Progress [ 3 ] To Be Merged [ 10001 ]
        Santiago Vacas made changes -
        Status To Be Merged [ 10001 ] Closed [ 6 ]
        Resolution Fixed [ 1 ]
        Ramiro Rinaudo made changes -
        Workflow Fixed Main Mule Workflow (after JIRA upgrade) [ 83138 ] Main Mule Workflow v1.0 [ 135694 ]

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development