You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2008/10/07 09:04:53 UTC
[jira] Updated: (SM-1575) Improve shutdown process: consumer
endpoints should first stop accepting new request while all pending
exchanges are being finished up
[ https://issues.apache.org/activemq/browse/SM-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet updated SM-1575:
--------------------------------
Affects Version/s: servicemix-bean-2008.01
(was: 3.2.2)
> Improve shutdown process: consumer endpoints should first stop accepting new request while all pending exchanges are being finished up
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-1575
> URL: https://issues.apache.org/activemq/browse/SM-1575
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-bean, servicemix-camel, servicemix-cxf-bc, servicemix-cxf-se, servicemix-drools, servicemix-eip, servicemix-file, servicemix-ftp, servicemix-http, servicemix-jms, servicemix-jsr181, servicemix-mail, servicemix-osworkflow, servicemix-quartz, servicemix-saxon, servicemix-sca, servicemix-script, servicemix-scripting, servicemix-truezip, servicemix-wsn2005
> Reporter: Gert Vanthienen
> Assignee: Gert Vanthienen
> Fix For: servicemix-bean-2008.01
>
>
> The endpoints should have a two stage shutdown too (using a stop() and shutdown() like e.g. the components).
> This would allow us to stop a consumer endpoint from receiving new request, while still keeping the broker and flows running to handle all pending request.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.