[
https://issues.apache.org/jira/browse/HTTPCORE-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha C. Perera resolved HTTPCORE-127.
----------------------------------------
Resolution: Fixed
Oleg
Thanks for your review and comments, and I have not exposed the
ServerSocketChannel over the public API as you suggested. Also I have removed
the maintenance shutdown method for now, and kept only pause() and resume()
Please feel free to make any more changes to the code if required, and I have
checked in this code to svn
thanks
asankha
> Expose improved API for lifecycle management
> --------------------------------------------
>
> Key: HTTPCORE-127
> URL: https://issues.apache.org/jira/browse/HTTPCORE-127
> Project: HttpComponents Core
> Issue Type: Improvement
> Components: HttpCore NIO
> Affects Versions: 4.0-alpha6
> Reporter: Asankha C. Perera
> Fix For: 4.0-beta1
>
> Attachments: httpcore-127.patch
>
>
> 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)"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
