[jboss-jira] [JBoss JIRA] (WFCORE-2998) levelRange in filter-spec is documented wrong and makes Wildfly startup fail silently

[James Perkins (JIRA)]

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

James Perkins commented on WFCORE-2998:
---------------------------------------

The problem is the error happens while configuring logging so it can't really report it at this point. I've got an issue filed on the log manager (LOGMGR-150) to support a better way of reporting errors. Until that gets fixed there's not a lot we can do at this point.

When I start the current upstream I do at least see the error:
{code}
11:10:27,898 INFO  [org.xnio.nio] (MSC service thread 1-7) XNIO NIO Implementation Version 3.5.0.CR1
11:10:27,915 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
    ("subsystem" => "logging"),
    ("console-handler" => "CONSOLE")
]): java.lang.IllegalArgumentException: Max level cannot be less than min level
	at org.jboss.logmanager.filters.LevelRangeFilter.<init>(LevelRangeFilter.java:49)
	at org.jboss.logmanager.config.LogContextConfigurationImpl.parseFilterExpression(LogContextConfigurationImpl.java:645)
	at org.jboss.logmanager.config.LogContextConfigurationImpl.resolveFilter(LogContextConfigurationImpl.java:731)
	at org.jboss.logmanager.config.LogContextConfigurationImpl.resolveFilter(LogContextConfigurationImpl.java:739)
	at org.jboss.logmanager.config.HandlerConfigurationImpl$3.validate(HandlerConfigurationImpl.java:166)
	at org.jboss.logmanager.config.HandlerConfigurationImpl$3.validate(HandlerConfigurationImpl.java:164)
	at org.jboss.logmanager.config.LogContextConfigurationImpl.doPrepare(LogContextConfigurationImpl.java:335)
	at org.jboss.logmanager.config.LogContextConfigurationImpl.prepare(LogContextConfigurationImpl.java:288)
	at org.jboss.as.logging.logmanager.ConfigurationPersistence.prepare(ConfigurationPersistence.java:303)
	at org.jboss.as.logging.LoggingOperations$CommitOperationStepHandler.execute(LoggingOperations.java:97)
	at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:978)
	at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:724)
	at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:448)
	at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1402)
	at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:516)
	at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:468)
	at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:430)
	at org.jboss.as.server.ServerService.boot(ServerService.java:437)
	at org.jboss.as.server.ServerService.boot(ServerService.java:396)
	at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:370)
	at java.lang.Thread.run(Thread.java:748)
{code}

> levelRange in filter-spec is documented wrong and makes Wildfly startup fail silently
> -------------------------------------------------------------------------------------
>
>                 Key: WFCORE-2998
>                 URL: https://issues.jboss.org/browse/WFCORE-2998
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Logging
>    Affects Versions: 2.2.1.Final
>            Reporter: Gregor Rosenauer
>            Assignee: James Perkins
>              Labels: check, configuration, logging, startup
>
> Linux 4.8.0-54-generic #57-Ubuntu SMP Wed May 24 10:21:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
> Oracle JDK 8 build 1.8.0_131-b11
> running in a docker container using Docker 1.12.6, build 78d1802
> Trying to configure e.g. a console-appender with a logging filter as described in
> [Wildfly 10 Logging Configuration|https://docs.jboss.org/author/display/WFLY10/Logging+Configuration]
> The server will startup and happily parse the configuration, but then exit without any error:
> {{2017-06-22 15:12:28,185 DEBG fd 7 closed, stopped monitoring <POutputDispatcher at 140706226583888 for <Subprocess at 140706228894320 with name wildfly in state RUNNING> (stdout)>
> 2017-06-22 15:12:28,186 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 140706226584392 for <Subprocess at 140706228894320 with name wildfly in state RUNNING> (stderr)>}}
> The culprit is the *order* of the levels in the range expression, which is the wrong way around.
> The correct order (which makes more sense anyway) is e.g. {{[DEBUG,WARN)}} not {{[WARN,DEBUG)}}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)