[
https://issues.apache.org/activemq/browse/SM-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45671#action_45671
]
Guillaume Nodet commented on SM-1576:
-------------------------------------
Yes, I think so. The startup / shutdown of the container should take care of
transitioning all the SA / SU to the same stage before goind to another stage.
I.e. when starting the container, it should first init all SUs (i.e. register
all endpoints, but no endpoints should start sending exchanges), then start
them all.
When shutting down, it would stop all SUs, stopping servicing new requests from
the ouside world, while enabling pending requests to be processed.
> Change endpoints lifecycle to use init / start / stop / shutdown
> ----------------------------------------------------------------
>
> Key: SM-1576
> URL: https://issues.apache.org/activemq/browse/SM-1576
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-common
> Reporter: Guillaume Nodet
> Fix For: 3.3
>
>
> Change servicemix-common in the following way:
> * refactor the existing start / stop method into init / shutdown (along
> with the doStart and doStop methods)
> * add new start / stop methods with empty implementation in the Endpoint
> class
> * use these new init / start / stop / shutdown lifecycle in the service
> unit
> * implement start / stop for the polling endpoints
> * implement start / stop for the jms consumer endpoint (it should start /
> stop the listener container)
> * implement start / stop for the http consumer (a stopped endpoint should
> return an 503 Service Unavailable http status code)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
