]
James Perkins moved JBEAP-10849 to WFLY-8748:
---------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-8748 (was: JBEAP-10849)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Domain Management
Logging
(was: Domain Management)
(was: Logging)
(was: Performance)
Affects Version/s: (was: 7.0.z.GA)
CONSOLE handler in Domain "full-ha" profile
-------------------------------------------
Key: WFLY-8748
URL:
https://issues.jboss.org/browse/WFLY-8748
Project: WildFly
Issue Type: Task
Components: Domain Management, Logging
Reporter: James Perkins
Assignee: James Perkins
Priority: Minor
In EAP 7 console-handler was disabled by default in standalone-full-ha.xml because this
profile is intended for production use. But "full-ha" profile in domain.xml
contain the CONSOLE handler, by the same reasoning, it should not be there.
Logging subsystem configuration in domain.xml "full-ha" profile :
{code}
<profile name="full-ha">
<subsystem xmlns="urn:jboss:domain:logging:3.0">
<console-handler name="CONSOLE">
<level name="INFO"/>
<formatter>
<named-formatter name="COLOR-PATTERN"/>
</formatter>
</console-handler>
<periodic-rotating-file-handler name="FILE"
autoflush="true">
<formatter>
<named-formatter name="PATTERN"/>
</formatter>
<file relative-to="jboss.server.log.dir"
path="server.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="true"/>
</periodic-rotating-file-handler>
<logger category="com.arjuna">
<level name="WARN"/>
</logger>
<logger category="org.jboss.as.config">
<level name="DEBUG"/>
</logger>
<logger category="sun.rmi">
<level name="WARN"/>
</logger>
<root-logger>
<level name="INFO"/>
<handlers>
<handler name="CONSOLE"/>
<handler name="FILE"/>
</handlers>
</root-logger>
<formatter name="PATTERN">
<pattern-formatter pattern="%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p
[%c] (%t) %s%e%n"/>
</formatter>
<formatter name="COLOR-PATTERN">
<pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p
[%c] (%t) %s%e%n"/>
</formatter>
</subsystem>
....
</profile>
{code}