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

Broker cannot start on Windows

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • AMQ 7.4.0.CR2
    • AMQ 7.4.0.CR1
    • None
    • None
    • Verified in a release
    • Hide

      1. Download and unzip the installation package.
      2. Create a broker instance: ~\bin\artemis.cmd create broker --user admin --password admin --allow-anonymous y
      3. Try to run the broker instance: cd broker; ~\bin\artemis.cmd run

      Show
      1. Download and unzip the installation package. 2. Create a broker instance: ~\bin\artemis.cmd create broker --user admin --password admin --allow-anonymous y 3. Try to run the broker instance: cd broker; ~\bin\artemis.cmd run

    Description

      Creating a broker instance is possible, but the instance cannot start, the exception is raised, see below, please:

      bin\artemis.cmd run
           __  __  ____    ____            _
     /\   |  \/  |/ __ \  |  _ \          | |
    /  \  | \  / | |  | | | |_) |_ __ ___ | | _____ _ __
   / /\ \ | |\/| | |  | | |  _ <| '__/ _ \| |/ / _ \ '__|
  / ____ \| |  | | |__| | | |_) | | | (_) |   <  __/ |
 /_/    \_\_|  |_|\___\_\ |____/|_|  \___/|_|\_\___|_|

 Red Hat JBoss AMQ 7.4.0.GA


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(ActiveMQBoot
strapLogger_$logger.java:35)
        at org.apache.activemq.artemis.integration.FileBroker.start(FileBroker.java:68)
        at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:85)
        at org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:150)
        at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:98)
        at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:125)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:129)
        at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:49)

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-522 Broker running on windows write problems with remove temp files when shutting down

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-2582 Patching from 7.3.0 to 7.4.0 doesn't work

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

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-3110 Upgrading a Broker instance from 7.4.x to 7.5.0 missing one step.

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-2674 artemis-service.exe start is not working with cygwin

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          mentioned in

          Page Loading...

          Activity

            People

              rh-ee-ataylor Andy Taylor
              psvobodo@redhat.com Petra Svobodova (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: