[
https://issues.apache.org/activemq/browse/SM-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50285#action_50285
]
Jean-Baptiste Onofré commented on SM-1818:
------------------------------------------
I have checked in the stop() method of the ServiceAssemblyLifeCycle class and
you behavior is stranged.
Currently, the SA can be stopped only if it's started state :
if (sus[i].isStarted()) {
try {
sus[i].stop();
} catch (DeploymentException e) {
componentFailures.add(getComponentFailure(e, "stop",
sus[i].getComponentName()));
}
}
So, if the SA is in the shutdown state, calling the stop() method should not
affect the SA state.
I have tried to reproduce your behavior without success (calling stop() using
JMX jConsole) on the SMX 3.3 trunk.
I change the state of this Jira issue. Please reopen the Jira with a quick
environment describe : JVM, SMX, kind of SA/SU.
> invoking stop on SA in SHUTDOWN state brings it to STOPPED state
> ----------------------------------------------------------------
>
> Key: SM-1818
> URL: https://issues.apache.org/activemq/browse/SM-1818
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-core
> Affects Versions: 3.3
> Reporter: Maciej Prochniak
> Assignee: Jean-Baptiste Onofré
>
> Currently it is possible to successfully invoke (e.g. with JMX operations)
> stop() on SA that is in SHUTDOWN state. The start() method is not invoked
> then. The SUs remain in SHUTDOWN state. This leads to unexpected behaviour -
> the SA is stopped, but it doesn't accept (internal) requests for it's
> services. While invoking stop() on
> component it's checked whether it's started - maybe it should be the same for
> SA.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
