Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-4960

jboss.tomcat.connectors.started JMX Notification Missing

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • EAP_EWP 5.1.1
    • EAP 5.0.1
    • Web
    • None
    • Hide
      sendNotification was present in org.jboss.web.tomcat.service.deployers.TomcatServices.java, but was disabled, so the jboss.tomcat.connectors.started notification was missing. The Barrier Controller depended on that notification and was unavailable to manage subscriptions. This problem has been fixed by reinstating sendNotification.
      Show
      sendNotification was present in org.jboss.web.tomcat.service.deployers.TomcatServices.java, but was disabled, so the jboss.tomcat.connectors.started notification was missing. The Barrier Controller depended on that notification and was unavailable to manage subscriptions. This problem has been fixed by reinstating sendNotification.
    • Documented as Resolved Issue

    Description

      The jboss.tomcat.connectors.started JMX notification is missing. This means that, for example, use of the the Barrier Service to wait for Servlets to be available will not work [1]. The problem has been previously identified and is fixed upstream (JBAS-6499). So, this jira represents the backport of that fix.

      [1] http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/4.3.0.cp06/html/Server_Configuration_Guide/Additional_Services-The_BarrierController_Service.html

      Attachments

        Issue Links

          Activity

            People

              rhn-support-miclark Mike Clark
              rhn-support-miclark Mike Clark
              Rebecca Newton Rebecca Newton (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: