[
https://issues.jboss.org/browse/WFLY-1712?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on WFLY-1712:
-----------------------------------------------
James Perkins <jperkins(a)redhat.com> made a comment on [bug
1017881|https://bugzilla.redhat.com/show_bug.cgi?id=1017881]
I forgot to add. I think we should delay from EAP 6.2 because the workaround is easy
enough. The error is only going to occur in composite operations when using multiple
add-handler operations to the same logger.
If we need to get this into 6.2 it is possible, but at this stage I'm not sure
it's worth the change for the simple workaround. Also I doubt this use-case, adding
handlers to the same logger in a composite operation, is used all that often. This same
issue is present in EAP 6.1.x and it's the first time I've seen it.
Erroneous name attribute on root-logger after add-handler operation
--------------------------------------------------------------------
Key: WFLY-1712
URL:
https://issues.jboss.org/browse/WFLY-1712
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Logging
Reporter: James Perkins
Assignee: James Perkins
Priority: Minor
Execution of the {{add-handler}} operation adds a name attribute with the handlers name
to the root-logger model.
{code}
"root-logger" => {"ROOT" => {
"filter" => undefined,
"filter-spec" => undefined,
"handlers" => [
"FILE",
"CONSOLE"
],
"level" => "INFO",
"name" => "CONSOLE"
}}
{code}
--
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