[
https://jira.jboss.org/jira/browse/JBAS-4735?page=com.atlassian.jira.plug...
]
Remy Maucherat commented on JBAS-4735:
--------------------------------------
Yes, this case is specifically about the shutdown of the web connectors.
Upon Shutdown connectors should be stopped before applications are
undeployed
-----------------------------------------------------------------------------
Key: JBAS-4735
URL:
https://jira.jboss.org/jira/browse/JBAS-4735
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Clustering, Web (Tomcat) service
Affects Versions: JBossAS-4.2.1.GA
Reporter: Dominik Pospisil
Assignee: 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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira