Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-3110

Upgrading a Broker instance from 7.4.x to 7.5.0 missing one step.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • AMQ 7.5.0.GA
    • AMQ 7.5.0.GA, AMQ 7.6.0.GA
    • documentation
    • None

    Description

      Upgrading a Broker instance from 7.4.x to 7.5.0 missing following step :

      Edit the JAVA_ARGS property. Add the bootstrap class path argument, which references a dependent file for the log manager.
      
      -Xbootclasspath/a:$ARTEMIS_HOME/lib/wildfly-common-1.5.2.Final-redhat-00001.jar
      

      Please note wildfly-common-xx.jar's version. If we did not modify it according to AMQ 7.5, broker fails to start with

      java.lang.NoClassDefFoundError: org/wildfly/common/net/HostName
          at org.jboss.logmanager.ExtLogRecord.<init>(ExtLogRecord.java:87)
          at org.jboss.logmanager.Logger.log(Logger.java:796)
          at org.jboss.logging.JBossLogManagerLogger.doLog(JBossLogManagerLogger.java:44)
          at org.jboss.logging.Logger.logv(Logger.java:2226)
          at org.apache.activemq.artemis.integration.bootstrap.ActiveMQBootstrapLogger_$logger.serverStarting(ActiveMQBootstrapLogger_$logger.java:35)
          at org.apache.activemq.artemis.integration.FileBroker.start(FileBroker.java:68)
      

      Attachments

        Issue Links

          Activity

            People

              jbyrne@redhat.com John Byrne
              rhn-support-vkamble Varsha Kamble
              Mikhail Krutov Mikhail Krutov
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: