[
https://issues.jboss.org/browse/WFLY-2695?page=com.atlassian.jira.plugin....
]
James Perkins updated WFLY-2695:
--------------------------------
Steps to Reproduce:
* extract wildfly-8.0.0.CR1
* run bin/domain
* execute commands via CLI
** :stop-servers
** -/profile=full/subsystem=logging/console-handler=CONSOLE:remove-
**
/profile=full/subsystem=logging/pattern-formatter=TESTPATTERN:add(pattern="%d%n")
**
/profile=full/subsystem=logging/console-handler=CONSOLE:write-attribute(name=named-formatter,
value=TESTPATTERN)
** /host=master/server-config=server-one:start
was:
* extract wildfly-8.0.0.CR1
* run bin/domain
* execute commands via CLI
** :stop-servers
** /profile=full/subsystem=logging/console-handler=CONSOLE:remove
**
/profile=full/subsystem=logging/pattern-formatter=TESTPATTERN:add(pattern="%d%n")
**
/profile=full/subsystem=logging/console-handler=CONSOLE:write-attribute(name=named-formatter,
value=TESTPATTERN)
** /host=master/server-config=server-one:start
Creating named formater patterns for offline servers fail
---------------------------------------------------------
Key: WFLY-2695
URL:
https://issues.jboss.org/browse/WFLY-2695
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Logging
Affects Versions: 8.0.0.CR1
Environment: any domain configuration
Reporter: Matthias Berndt
Assignee: James Perkins
After adding and attaching a named formatter to an offline server starting the server
fails due to an invalid logging configuration.
server-one fails with:
{{
[Server:server-one] 00:08:00,214 ERROR [org.jboss.as.controller.management-operation]
(Controller Boot Thread) JBAS014612: Operation ("add") failed - address: ([
[Server:server-one] ("subsystem" => "logging"),
[Server:server-one] ("console-handler" => "CONSOLE")
[Server:server-one] ]): java.lang.IllegalArgumentException: Formatter
"TESTPATTERN" is not found
}}
I assume logging.properties is written too late in LoggingOperations.java
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira