[wsas-java-dev] [jira] Resolved: (WSAS-614) Switch node to maintenance mode

[Afkham Azeez (JIRA)]

     [ http://wso2.org/jira/browse/WSAS-614?page=all ]

Afkham Azeez resolved WSAS-614.
-------------------------------

    Resolution: Fixed

> Switch node to maintenance mode
> -------------------------------
>
>                 Key: WSAS-614
>                 URL: http://wso2.org/jira/browse/WSAS-614
>             Project: WSO2 WSAS
>          Issue Type: New Feature
>            Reporter: Afkham Azeez
>         Assigned To: Afkham Azeez
>            Priority: Critical
>             Fix For: 2.2
>
>
> Add new methods to the Axis2 Transport interface
>     void pause()
>     void resume()
> This will go into the Axis2 trunk. However, we do not want to take a dependency on trunk yet.
> Implement these methods for the transports we want to care about - NHTTP (for ESB) and HTTP (Tomcat; for WSAS).
> Use JMX to invoke these methods instead of via our service model.
> Introduce a system level call to enterMaintenanceMode()
>     - call pause() on all transports (via JMX)
>     - wait for all in-flight requests to complete
>     - turn on property saying its in maintenance mode
>     - also need another property that shows how many requests are currently being processed (to the best possible level; this may not be possible for all scenarios ... maybe by checking the size of the active threadpool)
> Usage pattern:
> - operator connects to a node in cluster
> - asks the node to enter maintenance mode
> - waits for confirmation (or until he's tired of waiting)
> - do whatever to the node and bring it back up (load balancer will auto detect that the node is up and start delivering messages to it)
> - move onto next node
> We need to do this same for WSAS and ESB both. Currently WSAS immediately shuts nodes down when it does cluster management - we need to change that to allow the system to first finish inflight requests before shutting down; basically call enterMaintainance mode and then shutdown.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira