[SMXCOMP-227] Improve shutdown process: consumer endpoints should first stop accepting new request while all pending exchanges are being finished up

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Fix Version/s: servicemix-bean-2008.01, servicemix-camel-2008.01, servicemix-cxf-bc-2008.01, servicemix-cxf-se-2008.01, servicemix-drools-2008.01, servicemix-eip-2008.01, servicemix-file-2008.01, servicemix-ftp-2008.01, servicemix-http-2008.01, servicemix-jms-2008.01, servicemix-jsr181-2008.01, servicemix-mail-2008.01, servicemix-osworkflow-2008.01, servicemix-quartz-2008.01, servicemix-saxon-2008.01, servicemix-script-2008.01, servicemix-scripting-2008.01, servicemix-shared-2008.01, servicemix-truezip-2008.01, servicemix-validation-2008.01, servicemix-wsn2005-2008.01, servicemix-xmpp-2008.01
• Component/s: 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-script, servicemix-scripting, servicemix-truezip, servicemix-wsn2005
• Assignee: Gert Vanthienen
• Reporter: Gert Vanthienen
• Created: 12/Sep/08 11:22
• Updated: 14/Feb/09 22:21
• Resolved: 15/Sep/08 08:19

Description

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.