[jboss-jira] [JBoss JIRA] Commented: (JBAS-4735) Upon Shutdown connectors should be stopped before applications are undeployed
[
https://jira.jboss.org/jira/browse/JBAS-4735?page=com.atlassian.jira.plug...
]
Bjørn Ola Smievoll commented on JBAS-4735:
------------------------------------------
Is this regarded as only related to Tomcat connectors? I'm currently investigating the
same type of problem with remote EJB clients where they are not disconnected and failed
over before undeployment initiates. It even looks like calls fail in the JMX-kernel with
beans having been removed midway trough the excecution (shutdown is rather slow).
Seen in comments on the related issues this new behaviour won't be back-ported to the
4.2 branch, is there in that case some workaround available?
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