[JBoss JIRA] Created: (JBAS-4735) Upon Shutdown connectors should be stopped before applications are undeployed
3:24 a.m.
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: Clustering, Web (Tomcat) service
Affects Versions: JBossAS-4.2.1.GA
Reporter: Dominik Pospisil
Assigned To: Brian Stansberry
In clustered environment the process of shutting down single AS instance should be
transparent to clients. This is not the case since applications are udeployed at first
while connectors are still servicing requests. This causes clients not to be redirected to
another cluster nodes and to receive resource not avaiable exceptions.
From the client perspective, shutdown process should should work like
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
4:09 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-4735) Upon Shutdown connectors should be stopped before applications are undeployed
[ http://jira.jboss.com/jira/browse/JBAS-4735?page=all ]
Dominik Pospisil updated JBAS-4735:
-----------------------------------
Description:
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
was:
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 like
follows:
1) stop connectors so they refuse servicing new requests
2) complete running requests
3) undeploy applications
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: Brian Stansberry
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
4:09 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-4735) Upon Shutdown connectors should be stopped before applications are undeployed
[ http://jira.jboss.com/jira/browse/JBAS-4735?page=all ]
Dominik Pospisil updated JBAS-4735:
-----------------------------------
Description:
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 like
follows:
1) stop connectors so they refuse servicing new requests
2) complete running requests
3) undeploy applications
was:
In clustered environment the process of shutting down single AS instance should be
transparent to clients. This is not the case since applications are udeployed at first
while connectors are still servicing requests. This causes clients not to be redirected to
another cluster nodes and to receive resource not avaiable exceptions.
From the client perspective, shutdown process should should work like
follows:
1) stop connectors so they refuse servicing new requests
2) complete running requests
3) undeploy applications
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: Brian Stansberry
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 like 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
10:46 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-4735) Upon Shutdown connectors should be stopped before applications are undeployed
[ http://jira.jboss.com/jira/browse/JBAS-4735?page=all ]
Brian Stansberry updated JBAS-4735:
-----------------------------------
JBoss Forum Reference:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=119807
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: Clustering, Web (Tomcat) service
Affects Versions: JBossAS-4.2.1.GA
Reporter: Dominik Pospisil
Assigned To: Brian Stansberry
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
11:17 a.m.
New subject: [JBoss JIRA] Assigned: (JBAS-4735) Upon Shutdown connectors should be stopped before applications are undeployed
[ http://jira.jboss.com/jira/browse/JBAS-4735?page=all ]
Brian Stansberry reassigned JBAS-4735:
--------------------------------------
Assignee: Remy Maucherat (was: Brian Stansberry)
Remy, I'm passing this one over to you; I think it's beyond what I could get done
efficiently, as it involves the core connector code.
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
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
12:42 p.m.
New subject: [JBoss JIRA] Resolved: (JBAS-4735) Upon Shutdown connectors should be stopped before applications are undeployed
[ 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
6:45 a.m.
New subject: [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
6:58 a.m.
New subject: [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...
]
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
5658
days inactive
6100
days old
7 comments
4 participants
participants (4)
-
Bjørn Ola Smievoll (JIRA) -
Brian Stansberry (JIRA)
-
Dominik Pospisil (JIRA)
-
Remy Maucherat (JIRA)