[jboss-jira] [JBoss JIRA] (WFCORE-801) file-handler configured via CLI should require file attribute during add operation

[James Perkins (JIRA)]

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

James Perkins updated WFCORE-801:
---------------------------------
    Fix Version/s: 2.0.0.Alpha8
                       (was: 2.0.0.Alpha7)


> file-handler configured via CLI should require file attribute during add operation
> ----------------------------------------------------------------------------------
>
>                 Key: WFCORE-801
>                 URL: https://issues.jboss.org/browse/WFCORE-801
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Logging
>            Reporter: Jan Stourac
>            Assignee: James Perkins
>             Fix For: 2.0.0.Alpha8
>
>
> When adding file-handler via CLI I can add it without "file" element specified and operation is successfull. However when server reload is performed then configuration fails to parse and server stops with following error:
> {code}
> 15:41:59,452 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
> 	at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131)
> 	at org.jboss.as.server.ServerService.boot(ServerService.java:350)
> 	at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:272)
> 	at java.lang.Thread.run(Thread.java:745)
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[98,13]
> Message: WFLYCTL0133: Missing required attribute(s): FILE
> 	at org.jboss.as.controller.parsing.ParseUtils.missingRequired(ParseUtils.java:161)
> 	at org.jboss.as.logging.LoggingSubsystemParser_3_0.parseFileHandlerElement(LoggingSubsystemParser_3_0.java:522)
> 	at org.jboss.as.logging.LoggingSubsystemParser_3_0.readElement(LoggingSubsystemParser_3_0.java:151)
> 	at org.jboss.as.logging.LoggingSubsystemParser_3_0.readElement(LoggingSubsystemParser_3_0.java:96)
> 	at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
> 	at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69)
> 	at org.jboss.as.server.parsing.StandaloneXml_4.parseServerProfile(StandaloneXml_4.java:540)
> 	at org.jboss.as.server.parsing.StandaloneXml_4.readServerElement(StandaloneXml_4.java:237)
> 	at org.jboss.as.server.parsing.StandaloneXml_4.readElement(StandaloneXml_4.java:140)
> 	at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:69)
> 	at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:47)
> 	at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
> 	at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)
> 	at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123)
> 	... 3 more
> 15:41:59,453 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> {code}
> Expected behaviour is that adding operation on file-handler would require "file" element to be specified or whole operation fails with suitable error message.
> Not sure if it is connected directly or is another problem but I would expect that when "file" element is required then it should not be nillable but when I run:
> {code}
> /subsystem=logging/file-handler=test:read-resource-description
> {code}
> I can see that nillable is enabled for it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)