Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-8132

Unable to create http-acceptors with same name for 2 different server

    XMLWordPrintable

Details

    • Bug
    • Status: Verified (View Workflow)
    • Minor
    • Resolution: Done
    • 7.0.3.GA
    • 7.1.0.DR11
    • JMS
    • None
    • Hide

      Use different names for the http-acceptors (and make sure to reference the correct ones in the http-connector resources)

      Show
      Use different names for the http-acceptors (and make sure to reference the correct ones in the http-connector resources)

    Description

      To reproduce, create 2 messaging-activemq's server with the same configuration of http-acceptor:

                  <server name="default">
                      ....
                      <http-acceptor name="http-acceptor" http-listener="default"/>
                      ...
                  </server>
                  <server name="other">
                      ...
                      <http-acceptor name="http-acceptor" http-listener="default"/>
                      ...
                  </server>
      

      WildFly starts with the error:

      16:24:47,503 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 51) WFLYCTL0013: Operation ("add") failed - address: ([
          ("subsystem" => "messaging-activemq"),
          ("server" => "other"),
          ("http-acceptor" => "http-acceptor")
      ]): org.jboss.msc.service.DuplicateServiceException: Service jboss.messaging-activemq.http-upgrade-service.http-acceptor is already registered
      

      Attachments

        Issue Links

          Activity

            People

              jmesnil1@redhat.com Jeff Mesnil
              jmesnil1@redhat.com Jeff Mesnil
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: