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

Setting of non-existing factory class to connector service can cause ActiveMQ crash

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.0.1.CR1, 7.0.1.GA
    • 7.0.0.ER5
    • ActiveMQ, JMS
    • None
    • Hide
      1. Run EAP 7
      2. Create new connector service with non existing factory class /profile=full/subsystem=messaging-activemq/server=default/connector-service=foo:add(factory-class=bar)
      3. Reload :reload-servers
      4. Failed to start service jboss.messaging-activemq.default.jms.manager
      Show
      Run EAP 7 Create new connector service with non existing factory class /profile=full/subsystem=messaging-activemq/server=default/connector-service=foo:add(factory-class=bar) Reload :reload-servers Failed to start service jboss.messaging-activemq.default.jms.manager
    • EAP 7.0.1

    Description

      When setting non-existing factory class to connector service, no validation is done and during startup after reload service will fail.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFLY-6241 Setting of non-existing factory class to connector service can cause ActiveMQ crash

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Activity

            People

              rhn-engineering-lgao Lin Gao
              jkasik@redhat.com Jan Kašík
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: