[
https://issues.jboss.org/browse/WFCORE-2958?page=com.atlassian.jira.plugi...
]
James Perkins commented on WFCORE-2958:
---------------------------------------
The issue here is the undefining the {{formatter}} attribute then defining a
{{named-formatter}}. When the {{named-formatter}} is written it attempts to remove a
formatter with the same name as the handler. The initial {{undefine-attribute}} on the
{{formatter}} attribute tries to edit the previous formatter which has been removed.
One option would be to not have the log managers configuration API remove the handlers
name from it's configuration collection until the action is executed. This may be the
only real option to fix this issue.
Another option may be for the OSH not to remove the formatter. This will however leave the
formatter in the configuration API that's not used. We could add an additional step
that would execute after the commit step which removes handler then does an additional
commit.
Composite operation on periodic-rotating-file-handler fails
-----------------------------------------------------------
Key: WFCORE-2958
URL:
https://issues.jboss.org/browse/WFCORE-2958
Project: WildFly Core
Issue Type: Bug
Components: Logging
Reporter: James Perkins
Assignee: James Perkins
When performing composite operation on periodic-rotating-file-handler, it fails with [1]
although individual steps passes. This affects Web Console form editing.
[1]
{code}
[standalone@localhost:9990 / #] run-batch
The batch failed with the following error (you are remaining in the batch editing mode to
have a chance to correct the error):
WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:
Step: step-1
Operation:
/subsystem=logging/periodic-rotating-file-handler=foo:undefine-attribute(name=formatter)
Failure: WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException:
Formatter "foo" is not found
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)