[jboss-jira] [JBoss JIRA] Resolved: (AS7-1148) After startup and shutdown of the AS 7 CR 1 release, the async-handler configuration gets overwritten with improper element (subhandlers are changed to handlers), and it won't start again with editing the configuration.
David Lloyd (JIRA)
jira-events at lists.jboss.org
Tue Jul 5 14:10:23 EDT 2011
[ https://issues.jboss.org/browse/AS7-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Lloyd resolved AS7-1148.
------------------------------
Resolution: Done
> After startup and shutdown of the AS 7 CR 1 release, the async-handler configuration gets overwritten with improper element (subhandlers are changed to handlers), and it won't start again with editing the configuration.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-1148
> URL: https://issues.jboss.org/browse/AS7-1148
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management, Logging
> Affects Versions: 7.0.0.CR1
> Reporter: Andrig Miller
> Assignee: David Lloyd
> Priority: Critical
> Fix For: 7.0.0.Final
>
>
> I created a configuration to use asynchronous logging in standalone-ha.xml, and after successfully starting the server, running a test, and shutting it down, I could no longer restart the server without a parse error in standalone-ha.xml.
> What is happening, is the file is being rewritten, and it is replacing the subhandlers element with a handlers element which is incorrect.
> So, my configuration, that looks like this when I start the server:
> <subsystem xmlns="urn:jboss:domain:logging:1.0">
> <async-handler name="ASYNC">
> <level name="INFO"/>
> <queue-length value="1024"/>
> <overflow-action value="BLOCK"/>
> <subhandlers>
> <handler name="FILE"/>
> </subhandlers>
> </async-handler>
> <periodic-rotating-file-handler name="FILE" autoflush="true">
> <level name="INFO"/>
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="server.log"/>
> <suffix value=".yyyy-MM-dd"/>
> </periodic-rotating-file-handler>
> <logger category="com.arjuna">
> <level name="WARN"/>
> </logger>
> <logger category="org.apache.tomcat.util.modeler">
> <level name="WARN"/>
> </logger>
> <logger category="sun.rmi">
> <level name="WARN"/>
> </logger>
> <root-logger>
> <level name="INFO"/>
> <handlers>
> <handler name="ASYNC"/>
> </handlers>
> </root-logger>
> </subsystem>
> ends up looking like this:
> <subsystem xmlns="urn:jboss:domain:logging:1.0">
> <async-handler name="ASYNC">
> <level name="INFO"/>
> <queue-length value="1024"/>
> <overflow-action value="BLOCK"/>
> <handlers>
> <handler name="FILE"/>
> </handlers>
> </async-handler>
> <periodic-rotating-file-handler name="FILE" autoflush="true">
> <level name="INFO"/>
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="server.log"/>
> <suffix value=".yyyy-MM-dd"/>
> </periodic-rotating-file-handler>
> <logger category="com.arjuna">
> <level name="WARN"/>
> </logger>
> <logger category="org.apache.tomcat.util.modeler">
> <level name="WARN"/>
> </logger>
> <logger category="sun.rmi">
> <level name="WARN"/>
> </logger>
> <root-logger>
> <level name="INFO"/>
> <handlers>
> <handler name="ASYNC"/>
> </handlers>
> </root-logger>
> </subsystem>
> Which is wrong and fails parsing, which prevents the server from starting again, unless I hand edit the file again to correct it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list