5 Replies Latest reply on Jun 13, 2019 2:39 AM by Alban Chadenas

    Wildfly 17.0.0 Final Warning about AMQ automatic logging configuration on Windows

    Alban Chadenas Newbie

      Hi, I have just downloaded the latest Wildfly 17 release and noticed the following exception when starting the default configuration:

      C:\ApplicationServers\wildfly\wildfly-17.0.0.Final\bin>.\standalone.bat  --server-config=standalone-full.xml

      Calling "C:\ApplicationServers\wildfly\wildfly-17.0.0.Final\bin\standalone.conf.bat"

      Setting JAVA property to "c:\Java\jdk11\bin\java"

      ===============================================================================

       

        JBoss Bootstrap Environment

       

        JBOSS_HOME: "C:\ApplicationServers\wildfly\wildfly-17.0.0.Final"

       

        JAVA: "c:\Java\jdk11\bin\java"

       

        JAVA_OPTS: "-Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman  --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED"

       

      ===============================================================================

       

      08:34:20,112 INFO  [org.jboss.modules] (main) JBoss Modules version 1.9.1.Final

      ...

      ...

      08:34:22,835 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=C:\ApplicationServers\wildfly\wildfly-17.0.0.Final\standalone\data\activemq\journal,bindingsDirectory=C:\ApplicationServers\wildfly\wildfly-17.0.0.Final\standalone\data\activemq\bindings,largeMessagesDirectory=C:\ApplicationServers\wildfly\wildfly-17.0.0.Final\standalone\data\activemq\largemessages,pagingDirectory=C:\ApplicationServers\wildfly\wildfly-17.0.0.Final\standalone\data\activemq\paging)

      08:34:22,842 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]

      08:34:22,857 INFO  [org.jboss.ws.common.management] (MSC service thread 1-6) JBWS022052: Starting JBossWS 5.3.0.Final (Apache CXF 3.3.2)

      08:34:22,869 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221013: Using NIO Journal

      08:34:22,918 INFO  [org.wildfly.iiop.openjdk] (MSC service thread 1-4) WFLYIIOP0009: CORBA ORB Service started

      08:34:22,927 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE

      08:34:22,928 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP

      08:34:22,932 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ

      08:34:22,932 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP

      08:34:22,997 INFO  [org.apache.activemq.audit.base] (ServerService Thread Pool -- 82) AMQ601138: User anonymous is getting notification info on target resource: null []

      08:34:23,003 WARN  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ222277: Problem initializing automatic logging configuration reload for file:C:\ApplicationServers\wildfly\wildfly-17.0.0.Final\standalone\configuration/logging.properties: java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\ApplicationServers\wildfly\wildfly-17.0.0.Final\standalone\configuration/logging.properties

              at java.base/java.net.URI$Parser.fail(URI.java:2915)

              at java.base/java.net.URI$Parser.checkChars(URI.java:3086)

              at java.base/java.net.URI$Parser.parse(URI.java:3122)

              at java.base/java.net.URI.<init>(URI.java:600)

              at org.apache.activemq.artemis@2.8.1//org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart1(ActiveMQServerImpl.java:2775)

              at org.apache.activemq.artemis@2.8.1//org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:64)

              at org.apache.activemq.artemis@2.8.1//org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:595)

              at org.apache.activemq.artemis@2.8.1//org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:522)

              at org.apache.activemq.artemis@2.8.1//org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:373)

              at org.wildfly.extension.messaging-activemq//org.wildfly.extension.messaging.activemq.jms.JMSService.doStart(JMSService.java:206)

              at org.wildfly.extension.messaging-activemq//org.wildfly.extension.messaging.activemq.jms.JMSService.access$000(JMSService.java:65)

              at org.wildfly.extension.messaging-activemq//org.wildfly.extension.messaging.activemq.jms.JMSService$1.run(JMSService.java:100)

              at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)

              at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)

              at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)

              at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)

              at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)

              at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348)

              at java.base/java.lang.Thread.run(Thread.java:834)

              at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485)

       

       

      This can easily be solved by adding the following JVM argument '-Dlogging.configuration=file:C:/ApplicationServers/wildfly/wildfly-17.0.0.Final/standalone/configuration/logging.properties' replacing windows path backslashes with forward slash:

       

      C:\ApplicationServers\wildfly\wildfly-17.0.0.Final\bin>.\standalone.bat  --server-config=standalone-full.xml -Dlogging.configuration=file:C:/ApplicationServers/wildfly/wildfly-17.0.0.Final/standalone/configuration/logging.properties

      Calling "C:\ApplicationServers\wildfly\wildfly-17.0.0.Final\bin\standalone.conf.bat"

      Setting JAVA property to "c:\Java\jdk11\bin\java"

      ===============================================================================

      ...

      ...

      08:35:44,639 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221013: Using NIO Journal

      08:35:44,697 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE

      08:35:44,698 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP

      08:35:44,699 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ

      08:35:44,700 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP

      08:35:44,724 INFO  [org.wildfly.iiop.openjdk] (MSC service thread 1-1) WFLYIIOP0009: CORBA ORB Service started

      08:35:44,748 INFO  [org.apache.activemq.audit.base] (ServerService Thread Pool -- 82) AMQ601138: User anonymous is getting notification info on target resource: null []

      08:35:44,762 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221034: Waiting indefinitely to obtain live lock

      08:35:44,762 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221035: Live Server Obtained live lock

      08:35:45,298 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-6) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor

      08:35:45,298 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-3) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor

      08:35:45,298 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-8) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor

      08:35:45,298 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor

      08:35:45,412 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221007: Server is now live

      08:35:45,413 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221001: Apache ActiveMQ Artemis Message Broker version 2.8.1 [default, nodeID=fc2aaa90-8ce3-11e9-8c74-00155df15d07]

       

      Other Wildfly services seem to cope with windows paths and only the AMQ seems to complain about it.

      Is 'setting the logging.configuration VM property' what is expected to be done when starting a standard Wildfly on Windows environment?

       

      Thanks.