[jboss-jira] [JBoss JIRA] (WFCORE-4729) System property variable substitution not working for named-formatter

Jason White (Jira) issues at jboss.org
Fri Oct 25 18:21:00 EDT 2019


     [ https://issues.jboss.org/browse/WFCORE-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason White updated WFCORE-4729:
--------------------------------
    Steps to Reproduce: 
In the standalone.xml file, modify the named-formatter name in the logging subsystem to used a variable substitution for either a system or env property:
{noformat}
        <subsystem xmlns="urn:jboss:domain:logging:8.0">
            <console-handler name="CONSOLE">
                <level name="DEBUG"/>
                <formatter>
                    <named-formatter name="${some.property:COLOR-PATTERN}"/>
                </formatter>
            </console-handler>
...
{noformat}

Start up the server:
./standalone.sh

Observe the error in the description.

The problem occurs whether the system or env property exists or not.   This used to work in previous version of Wildly (v13)

  was:
In the standalone.xml file, modify the named-formatter name in the logging subsystem to used a variable substitution for either a system or env property:
{noformat}
        <subsystem xmlns="urn:jboss:domain:logging:8.0">
            <console-handler name="CONSOLE">
                <level name="DEBUG"/>
                <formatter>
                    <named-formatter name="${some.property:COLOR-PATTERN}"/>
                </formatter>
            </console-handler>
...
{noformat}

Start up the server:
./standalone.sh

Observe the error in the description.

The problem occurs whether the system or env property exists or not. 



> System property variable substitution not working for named-formatter
> ---------------------------------------------------------------------
>
>                 Key: WFCORE-4729
>                 URL: https://issues.jboss.org/browse/WFCORE-4729
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Logging
>    Affects Versions: 10.0.0.Final
>            Reporter: Jason White
>            Assignee: James Perkins
>            Priority: Major
>
> The follow FATAL error occurs at start up after attempting to configure a variable substitution for a named-formatter in the logging subsystem in standalone.xml:
> {noformat}
> =========================================================================
>   JBoss Bootstrap Environment
>   JBOSS_HOME: /home/jasonwhite/apps/wildfly-18.0.0.Final
>   JAVA: /home/jasonwhite/apps/jdk/bin/java
>   JAVA_OPTS:  -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true 
> =========================================================================
> 15:47:59,418 INFO  [org.jboss.modules] (main) JBoss Modules version 1.9.1.Final
> 15:47:59,732 INFO  [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
> 15:47:59,745 INFO  [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
> 15:47:59,848 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 18.0.0.Final (WildFly Core 10.0.0.Final) starting
> 15:48:00,460 INFO  [org.wildfly.security] (ServerService Thread Pool -- 24) ELY00001: WildFly Elytron version 1.10.3.Final
> 15:48:00,899 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 15:48:00,926 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 36) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 15:48:00,961 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=logging/console-handler=CONSOLE' are not available:
>     org.wildfly.logging.formatter.${some.property:COLOR-PATTERN}; Possible registration points for this capability: 
> 		/subsystem=logging/pattern-formatter=*
> 		/subsystem=logging/custom-formatter=*
> 		/subsystem=logging/json-formatter=*
> 		/subsystem=logging/xml-formatter=*
> 		/subsystem=logging/logging-profile=*/pattern-formatter=*
> 		/subsystem=logging/logging-profile=*/custom-formatter=*
> 		/subsystem=logging/logging-profile=*/json-formatter=*
> 		/subsystem=logging/logging-profile=*/xml-formatter=*
> 15:48:00,966 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 15:48:00,980 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Full 18.0.0.Final (WildFly Core 10.0.0.Final) stopped in 5ms
> {noformat}



--
This message was sent by Atlassian Jira
(v7.13.8#713008)


More information about the jboss-jira mailing list