[WFLY-1713] Using the add-handler operation on an async-handler doesn't write the handler property to the logging.properties file - JBoss Issue Tracker

XML

Word

Printable

Steps to Reproduce:

Hide

Execute: /subsystem=logging/async-handler=rh_async:add(queue-length=1000)

Then: /subsystem=logging/async-handler=rh_async:add-handler(name=CONSOLE)

Check the logging.properties file and the handler.rh_async.handlers=CONSOLE property is not present.

Show
Execute: /subsystem=logging/async-handler=rh_async:add(queue-length=1000) Then: /subsystem=logging/async-handler=rh_async:add-handler(name=CONSOLE) Check the logging.properties file and the handler.rh_async.handlers=CONSOLE property is not present.
Workaround Description:
Hide

When adding an async-handler don't use the add-handler operation, add the subhandlers attribute to the add operation.

/subsystem=logging/async-handler=rh_async:add(queue-length=1000,subhandlers=[CONSOLE])
Show
When adding an async-handler don't use the add-handler operation, add the subhandlers attribute to the add operation. /subsystem=logging/async-handler=rh_async:add(queue-length=1000,subhandlers=[CONSOLE])
Bugzilla References:
https://bugzilla.redhat.com/show_bug.cgi?id=997638

Executing an add-handler operation does not write the handler.$NAME.handlers property to the logging.properties file.