[
https://issues.apache.org/activemq/browse/SM-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50186#action_50186
]
Jean-Baptiste Onofré commented on SM-1818:
------------------------------------------
In the JBI spec, we have :
- stop(serviceAssemblyName). This method MUST attempt to stop each of the
service units of the assembly that is currently in the Started state.
So, if the SA is not in started state, the stop or shutdown can't be applied.
> 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.
