[
https://jira.jboss.org/jira/browse/JBESB-1997?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-1997:
-------------------------------------
This is correct behaviour as the controller state, prior to a start, should be
uninitialised. The start will also be called from the deployment MBean, which is created
by the deployer, and will be executed in a different context.
On start, initialiseInstances is called in
ManagedLifecycleController
---------------------------------------------------------------------
Key: JBESB-1997
URL:
https://jira.jboss.org/jira/browse/JBESB-1997
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployment
Affects Versions: 4.3
Reporter: Tom Cunningham
If you stop a service, the message counters should not reset if you start it once again.
When we start a service, we are calling initialiseInstances (see
ManagedLifecycleController.java:69) which creates a new ActionProcessingPipeline.
Shouldn't we be able to use the current ActionProcessingPipeline on a start?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira