[jboss-jira] [JBoss JIRA] (WFLY-12085) java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties

[James Perkins (Jira)]

    [ https://issues.jboss.org/browse/WFLY-12085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734584#comment-13734584 ] 

James Perkins commented on WFLY-12085:
--------------------------------------

This unfortunately won't fix this warning from being logged. The {{ReloadManager}} will not be scheduled, but the {{new URL(System.getProperty("logging.proeprties")).toURL()}} will still be invoked. This is because it's registered as a callback to the reload manager.

{code:java}
if (System.getProperty("logging.configuration") != null) {
   try {
      reloadManager.addCallback(new URI(System.getProperty("logging.configuration")).toURL(), new LoggingConfigurationFileReloader());
   } catch (Exception e) {
      // a syntax error with the logging system property shouldn't prevent the server from starting
      ActiveMQServerLogger.LOGGER.problemAddingConfigReloadCallback(System.getProperty("logging.configuration"), e);
   }
}
{code}

I don't know enough about the reload manager, but we may want to set it to {{-1}} anyway if the configuration should be coming from WildFly itself anyway.

> java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-12085
>                 URL: https://issues.jboss.org/browse/WFLY-12085
>             Project: WildFly
>          Issue Type: Bug
>          Components: JMS
>    Affects Versions: 17.0.0.Alpha1
>         Environment: Red Hat JBoss Enterprise Application Platform
>   7.2.1
> Microsoft Windows 10
>            Reporter: Emmanuel Hugonnet
>            Assignee: Emmanuel Hugonnet
>            Priority: Major
>
> There seems to be a regression in JBoss EAP 7.2.1 patch. After applying it the following exception can be seen in the server log file during the startup:
> {noformat} 
> 2019-05-13 11:45:11,419 WARN  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 78) AMQ222277: Problem initializing automatic logging configuration reload for file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties: java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties
> 	at java.net.URI$Parser.fail(URI.java:2848)
> 	at java.net.URI$Parser.checkChars(URI.java:3021)
> 	at java.net.URI$Parser.parse(URI.java:3058)
> 	at java.net.URI.<init>(URI.java:588)
> 	at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart1(ActiveMQServerImpl.java:2369)
> 	at org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:64)
> 	at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:544)
> 	at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:481)
> 	at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:376)
> 	at org.wildfly.extension.messaging.activemq.jms.JMSService.doStart(JMSService.java:206)
> 	at org.wildfly.extension.messaging.activemq.jms.JMSService.access$000(JMSService.java:65)
> 	at org.wildfly.extension.messaging.activemq.jms.JMSService$1.run(JMSService.java:100)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> 	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> 	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> 	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349)
> 	at java.lang.Thread.run(Thread.java:748)
> 	at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> {noformat}
> This issue only affects Microsoft Windows platform.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)