Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-1713

Using the add-handler operation on an async-handler doesn't write the handler property to the logging.properties file

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Major Major
    • None
    • None
    • Logging
    • None
    • 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.
    • 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])

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

              jperkins-rhn James Perkins
              jperkins-rhn James Perkins
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: