[jboss-jira] [JBoss JIRA] Resolved: (JBAS-4735) Upon Shutdown connectors should be stopped before applications are undeployed

Tue Nov 27 13:42:46 EST 2007

     [ http://jira.jboss.com/jira/browse/JBAS-4735?page=all ]

Remy Maucherat resolved JBAS-4735.
----------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
       Resolution: Done

This cannot be addressed properly in the java.io connectors, but the APR (HTTP and AJP) connectors should have much more predictable shutdown behavior in the AS 5 branch.

> Upon Shutdown connectors should be stopped before applications are undeployed
> -----------------------------------------------------------------------------
>
>                 Key: JBAS-4735
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4735
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service, Clustering
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Dominik Pospisil
>         Assigned To: Remy Maucherat
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> In clustered environment the process of shutting down single AS instance should be transparent to clients. This is not the case since applications are undeployed at first while connectors are still servicing requests. This causes clients not to be redirected to another cluster nodes and to receive resource not available exceptions.
> From the client perspective, shutdown process should work as follows:
> 1) stop connectors so they refuse servicing new requests
> 2) complete running requests
> 3) undeploy applications

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