Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-6241

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

    XMLWordPrintable

Details

    • 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

    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

          clones

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

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

          Activity

            Public project attachment banner

              context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
              current Project key: WFLY

              People

                rhn-engineering-lgao Lin Gao
                rhn-engineering-lgao Lin Gao
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: