Back to bug 1032627

Who When What Removed Added
Rafael Ruiz 2013-11-20 14:00:08 UTC Doc Text Cause:
:

Fix:

Result:
Summary /subsystem=logging/logger=org.jboss.as.quickstarts.logging:assign-handler can't run under batch mode /subsystem=logging/logger=any.category:assign-handler can't run under batch mode
James Perkins 2014-01-09 00:59:34 UTC Status NEW POST
Target Release --- EAP 6.2.2
Target Milestone --- Pending
Carlo de Wolf 2014-01-10 13:59:54 UTC Status POST MODIFIED
CC cdewolf
Scott Mumford 2014-02-27 06:11:56 UTC CC jperkins, smumford
Flags needinfo?(jperkins)
James Perkins 2014-02-27 19:39:56 UTC Doc Text Cause:
:

Fix:

Result:
Cause: An erroneous name attribute was added to the model. This resulted in the operation trying to add the final handler name to the logger or async-handler multiple times.
:

Fix: The name attribute is not added to the model and the operation correctly gets the handler name from the operation context.

Result: Adding handlers to a logger or async-handler in a composite operation now works correctly.
Flags needinfo?(jperkins)
Scott Mumford 2014-03-03 04:00:40 UTC Doc Text Cause: An erroneous name attribute was added to the model. This resulted in the operation trying to add the final handler name to the logger or async-handler multiple times.
:

Fix: The name attribute is not added to the model and the operation correctly gets the handler name from the operation context.

Result: Adding handlers to a logger or async-handler in a composite operation now works correctly.
An erroneous name attribute was added to the (logging?) model in a previous version of JBoss EAP. This resulted in the operation trying to add the final handler name to the logger or async-handler multiple times. To correct this behavior, the name attribute is no longer added to the model and the operation correctly gets the handler name from the operation context. In this release of the product, adding handlers to a logger or async-handler in a composite operation works correctly.
mark yarborough 2014-03-03 14:41:42 UTC Status MODIFIED ON_QA
Scott Mumford 2014-03-04 00:57:43 UTC Doc Text An erroneous name attribute was added to the (logging?) model in a previous version of JBoss EAP. This resulted in the operation trying to add the final handler name to the logger or async-handler multiple times. To correct this behavior, the name attribute is no longer added to the model and the operation correctly gets the handler name from the operation context. In this release of the product, adding handlers to a logger or async-handler in a composite operation works correctly. An erroneous name attribute was added to the logging model in a previous version of JBoss EAP. This resulted in the operation trying to add the final handler name to the logger or async-handler multiple times. To correct this behavior, the name attribute is no longer added to the model and the operation correctly gets the handler name from the operation context. In this release of the product, adding handlers to a logger or async-handler in a composite operation works correctly.
Nikoleta Hlavickova 2014-03-04 08:22:24 UTC Status ON_QA VERIFIED
John Doyle 2014-03-04 16:06:30 UTC CC jdoyle
mark yarborough 2014-06-02 12:49:10 UTC Status VERIFIED CLOSED
Resolution --- CURRENTRELEASE
Last Closed 2014-06-02 08:49:10 UTC

Back to bug 1032627