Uploaded image for project: 'Application Server 3 4 5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-5636

Stop HTTP/AJP connectors on Server.STOP_NOTIFICATION_TYPE

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • JBossAS-5.0.0.CR2
    • JBossAS-4.2.2.GA, JBossAS-5.0.0.Beta4
    • Web (Tomcat) service
    • None
    • 0
    • 0% 0%

    Description

      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.

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-380 Upon Shutdown connectors should be stopped before applications are undeployed

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              rmaucher Remy Maucherat
              rhn-support-tkimura Takayoshi Kimura
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: