3:42 p.m.
Stop HTTP/AJP connectors on Server.STOP_NOTIFICATION_TYPE
---------------------------------------------------------
Key: JBAS-5636
URL: http://jira.jboss.com/jira/browse/JBAS-5636
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Web (Tomcat) service
Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA
Reporter: Takayoshi Kimura
Assigned To: Remy Maucherat
In JBoss startup process, JBoss starts HTTP/AJP connectors when
Server.START_NOTIFICATION_TYPE received, so all applications are available when a time the
connectors are started.
This feature has not been implemented for shutdown.
In JBoss shutdown, JBoss undeploys web applications before stopping the connectors. In
this case applications are not available in some timeframe during the undeployment, and
clients may receive 503 or 404 errors. We can ensure applications availablity in a same
manner as startup, by Server.STOP_NOTIFICATION_TYPE.
--
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:49 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-5636) Stop HTTP/AJP connectors on Server.STOP_NOTIFICATION_TYPE
[ http://jira.jboss.com/jira/browse/JBAS-5636?page=comments#action_12417492 ]
Brian Stansberry commented on JBAS-5636:
----------------------------------------
Takayoshi, this sounds like JBAS-4735.
Stop HTTP/AJP connectors on Server.STOP_NOTIFICATION_TYPE
---------------------------------------------------------
Key: JBAS-5636
URL: http://jira.jboss.com/jira/browse/JBAS-5636
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Web (Tomcat) service
Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA
Reporter: Takayoshi Kimura
Assigned To: Remy Maucherat
In JBoss startup process, JBoss starts HTTP/AJP connectors when
Server.START_NOTIFICATION_TYPE received, so all applications are available when a time the
connectors are started.
This feature has not been implemented for shutdown.
In JBoss shutdown, JBoss undeploys web applications before stopping the connectors. In
this case applications are not available in some timeframe during the undeployment, and
clients may receive 503 or 404 errors. We can ensure applications availablity in a same
manner as startup, by Server.STOP_NOTIFICATION_TYPE.
--
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
5:25 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-5636) Stop HTTP/AJP connectors on Server.STOP_NOTIFICATION_TYPE
[ http://jira.jboss.com/jira/browse/JBAS-5636?page=comments#action_12417495 ]
Takayoshi Kimura commented on JBAS-5636:
----------------------------------------
Yes it looks JBAS-4735.
Remy, you said "This cannot be addressed properly in the java.io connectors" in
JBAS-4735, I don't get how this comes. Could you advice on it?
I did quick hack in JBossWeb to call pause() method on connectors when
Server.START_NOTIFICATION_TYPE received. I didn't test it carefully but it works.
Stop HTTP/AJP connectors on Server.STOP_NOTIFICATION_TYPE
---------------------------------------------------------
Key: JBAS-5636
URL: http://jira.jboss.com/jira/browse/JBAS-5636
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Web (Tomcat) service
Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA
Reporter: Takayoshi Kimura
Assigned To: Remy Maucherat
In JBoss startup process, JBoss starts HTTP/AJP connectors when
Server.START_NOTIFICATION_TYPE received, so all applications are available when a time the
connectors are started.
This feature has not been implemented for shutdown.
In JBoss shutdown, JBoss undeploys web applications before stopping the connectors. In
this case applications are not available in some timeframe during the undeployment, and
clients may receive 503 or 404 errors. We can ensure applications availablity in a same
manner as startup, by Server.STOP_NOTIFICATION_TYPE.
--
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
3:12 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-5636) Stop HTTP/AJP connectors on Server.STOP_NOTIFICATION_TYPE
[ http://jira.jboss.com/jira/browse/JBAS-5636?page=comments#action_12420306 ]
Remy Maucherat commented on JBAS-5636:
--------------------------------------
The shutdown has been improved (however, java.io connectors are stuck blocking on their IO
calls, which make them more difficult to manage). I was planning to use the InShutdown
flag to get something clean, but for some reason the value is not as expected.
// Hot undeploy
Boolean inShutdown = (Boolean)server.getAttribute(ServerImplMBean.OBJECT_NAME,
"InShutdown");
if (inShutdown.booleanValue() == false)
{
log.debug("Server '" + ServerImplMBean.OBJECT_NAME +
"' already started, stopping connectors now");
stopConnectors();
}
Stop HTTP/AJP connectors on Server.STOP_NOTIFICATION_TYPE
---------------------------------------------------------
Key: JBAS-5636
URL: http://jira.jboss.com/jira/browse/JBAS-5636
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Web (Tomcat) service
Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA
Reporter: Takayoshi Kimura
Assigned To: Remy Maucherat
In JBoss startup process, JBoss starts HTTP/AJP connectors when
Server.START_NOTIFICATION_TYPE received, so all applications are available when a time the
connectors are started.
This feature has not been implemented for shutdown.
In JBoss shutdown, JBoss undeploys web applications before stopping the connectors. In
this case applications are not available in some timeframe during the undeployment, and
clients may receive 503 or 404 errors. We can ensure applications availablity in a same
manner as startup, by Server.STOP_NOTIFICATION_TYPE.
--
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
1:30 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-5636) Stop HTTP/AJP connectors on Server.STOP_NOTIFICATION_TYPE
[ http://jira.jboss.com/jira/browse/JBAS-5636?page=comments#action_12420532 ]
Takayoshi Kimura commented on JBAS-5636:
----------------------------------------
I think that's a bug, filed in JBAS-5745.
Another point, the stopConnectors() method calls the stop() method on all connectors,
which leads some ERROR logs when the JBossWeb service is actually stopped. This ERROR log
won't be appeared if we use the pause() method instead.
Stop HTTP/AJP connectors on Server.STOP_NOTIFICATION_TYPE
---------------------------------------------------------
Key: JBAS-5636
URL: http://jira.jboss.com/jira/browse/JBAS-5636
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Web (Tomcat) service
Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA
Reporter: Takayoshi Kimura
Assigned To: Remy Maucherat
In JBoss startup process, JBoss starts HTTP/AJP connectors when
Server.START_NOTIFICATION_TYPE received, so all applications are available when a time the
connectors are started.
This feature has not been implemented for shutdown.
In JBoss shutdown, JBoss undeploys web applications before stopping the connectors. In
this case applications are not available in some timeframe during the undeployment, and
clients may receive 503 or 404 errors. We can ensure applications availablity in a same
manner as startup, by Server.STOP_NOTIFICATION_TYPE.
--
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:29 p.m.
New subject: [JBoss JIRA] Resolved: (JBAS-5636) Stop HTTP/AJP connectors on Server.STOP_NOTIFICATION_TYPE
[ http://jira.jboss.com/jira/browse/JBAS-5636?page=all ]
Remy Maucherat resolved JBAS-5636.
----------------------------------
Fix Version/s: JBossAS-5.0.0.CR2
Resolution: Done
Done. At this time, I prefer stopping as soon as pause is complete. The "error"
will not be displayed if there's no attempt to stop a connector multiple times (which
occurs because the flag is not right).
Stop HTTP/AJP connectors on Server.STOP_NOTIFICATION_TYPE
---------------------------------------------------------
Key: JBAS-5636
URL: http://jira.jboss.com/jira/browse/JBAS-5636
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Web (Tomcat) service
Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA
Reporter: Takayoshi Kimura
Assigned To: Remy Maucherat
Fix For: JBossAS-5.0.0.CR2
In JBoss startup process, JBoss starts HTTP/AJP connectors when
Server.START_NOTIFICATION_TYPE received, so all applications are available when a time the
connectors are started.
This feature has not been implemented for shutdown.
In JBoss shutdown, JBoss undeploys web applications before stopping the connectors. In
this case applications are not available in some timeframe during the undeployment, and
clients may receive 503 or 404 errors. We can ensure applications availablity in a same
manner as startup, by Server.STOP_NOTIFICATION_TYPE.
--
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
5915
days inactive
5940
days old
5 comments
3 participants
participants (3)
-
Brian Stansberry (JIRA) -
Remy Maucherat (JIRA)
-
Takayoshi Kimura (JIRA)