Logging stops while using async-handler in logging subsystem in EAP 6

Solution Unverified - Updated -

Environment

Red Hat JBoss Enterprise Application Platform (EAP) 6.x

Issue

When configuring the logging subsystem, adding an async-handler can cause all logging to stop. The server log file is not written to after a restart. The server log timestamp is updated, but nothing is written to it.

/subsystem=logging/async-handler=rh_async:add

Resolution

This is a bug in JBoss JBoss logging subsystem 1. There are a couple of workarounds:

  1. Remove logging.properties from the JBoss configuration directory. This only needs to be done when JBoss is restarted after an async-handler has been modified.

  2. Initialize the async-handler via the CLI using the subhandler attribute:

/subsystem=logging/async-handler=rh_async:add(queue-length=1000,subhandlers=[rh_file_handler])

  1. WFLY-1713 ↩

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.