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:
    None

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

Ascending order - Click to sort in descending order
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
26/Aug/11 05:22 PM
View full commit
MULE-5755: JMS Reconnection fails due to inconsistent connector lifecycle state allow the doStop process to continue even when a JMSException is thrown. The exception is expected when the jms broker is down. git-svn-id: https://svn.codehaus.org/mule/branches/mule-3.1.x@22762 bf997673-6b11-0410-b953-e057580c5b09
3.1.x
+3
-2
transports/jms/src/main/java/org/mule/transport/jms/JmsConnector.java
+24
-7
transports/jms/src/test/java/org/mule/transport/jms/JmsConnectorTestCase.java
Santiago Vacas
26/Aug/11 05:30 PM
View full commit
Merged revisions 22762 via svnmerge from https://svn.codehaus.org/mule/branches/mule-3.1.x ........ r22762 | svacas | 2011-08-26 19:22:41 -0300 (Fri, 26 Aug 2011) | 5 lines MULE-5755: JMS Reconnection fails due to inconsistent connector lifecycle state allow the doStop process to continue even when a JMSException is thrown. The exception is expected when the jms broker is down. ........ git-svn-id: https://svn.codehaus.org/mule/branches/mule-3.x@22763 bf997673-6b11-0410-b953-e057580c5b09
mule-3.2.x
+3
-2
transports/jms/src/main/java/org/mule/transport/jms/JmsConnector.java
+24
-7
transports/jms/src/test/java/org/mule/transport/jms/JmsConnectorTestCase.java
Santiago Vacas made changes -
Status Open [ 1 ] In Progress [ 3 ]
Santiago Vacas made changes -
Fix Version/s 3.2.0 [ 10942 ]
Fix Version/s 3.1.3 [ 10988 ]
Santiago Vacas made changes -
Status In Progress [ 3 ] To Be Merged [ 10001 ]
Santiago Vacas made changes -
Resolution Fixed [ 1 ]
Status To Be Merged [ 10001 ] Closed [ 6 ]
Transition Time In Source Status Execution Times Last Executer Last Execution Date
Open Open In Progress In Progress
89d 3h 56m 1 Santiago Vacas 23/Nov/11 02:17 PM
In Progress In Progress To Be Merged To Be Merged
4m 9s 1 Santiago Vacas 23/Nov/11 02:21 PM
To Be Merged To Be Merged Closed Closed
10s 1 Santiago Vacas 23/Nov/11 02:21 PM
This list may be incomplete, as errors occurred whilst retrieving source from linked applications:
  • Repository mule on http://foo.bar/ failed: Error in remote call to 'FishEye 0 (http://foo.bar/)' (http://foo.bar) [AbstractRestCommand{path='/rest-service-fe/changeset-v1/listChangesets/', params={expand=changesets[-21:-1].revisions[0:29], comment=MULE-5755, p4JobFixed=MULE-5755, rep=mule}, methodType=GET}] : java.net.UnknownHostException: foo.bar

People

  • Assignee:
    Santiago Vacas
    Reporter:
    Santiago Vacas
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: