[jboss-jira] [JBoss JIRA] Resolved: (JBAS-5636) Stop HTTP/AJP connectors on Server.STOP_NOTIFICATION_TYPE

Thu Jul 10 12:29:26 EDT 2008

     [ 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