[HTTPCORE-127] Expose improved API for lifecycle management

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0-alpha6
• Fix Version/s: 4.0-beta1
• Component/s: HttpCore NIO
• Assignee: Unassigned
• Reporter: Asankha Chamath Perera
• Created: 31/Oct/07 12:12
• Updated: 09/Feb/09 21:38
• Resolved: 13/Dec/07 18:57

Description

Apache Synapse uses HttpCore and we would like to stop accepting new connections to put our servers into a "maintenance" mode. In this mode any in-flight requests already being served will continue as normal (i.e. reading, writing etc) but new connections should be rejected, so that a load balancer could direct new connections to another instance in the cluster. The requirement is to then update configuration, apply patches or cleanly shutdown etc. for maintenance without effecting any in-flight requests.

Implementation wise I think this would be fairly straightforward as we can remove OP_ACCEPT from the interested ops.

On the mailing list Odi suggested that we tackle this at a broader level by exposing lifecycle management APIs
"I suggest create, start, stop, destroy methods in some classes/APIs (semantics of JBoss Service MBeans)"