Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-14559

[GSS](7.0.z) Using periodic-rotating-file-handler should be permitted as a handler for JMX subsystem audit log.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • 7.0.8.GA
    • JMX
    • None

    • This issue is reported in EAP 7.0.8.

    • +
    • Hide

      CLI command sequence to reproduce this issue in standalone mode as follows:

      1. /core-service=management/access=audit/periodic-rotating-file-handler=myhandler:add(formatter="json-formatter", max-failure-count=20, path="audit-jmx.log", relative-to="jboss.server.data.dir", suffix=".yyyy-MM-dd")
      2. /subsystem=jmx/configuration=audit-log:add()
      3. /subsystem=jmx/configuration=audit-log/handler=myhandler:add() ..... (*1)

      (*1) Excerpt from server.log – Error occurred by Step 3.

      2018-04-09 12:07:41,350 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 3) WFLYCTL0013: Operation ("add") failed - address: ([
    ("subsystem" => "jmx"),
    ("configuration" => "audit-log"),
    ("handler" => "myhandler")
]): java.lang.IllegalStateException: WFLYJMX0036: There is no handler called 'myhandler'
        at org.jboss.as.jmx.JmxAuditLogHandlerReferenceResourceDefinition$AuditLogHandlerReferenceAddHandler.populateModel(JmxAuditLogHandlerReferenceResourceDefinition.java:88)
        at org.jboss.as.controller.AbstractAddStepHandler.execute(AbstractAddStepHandler.java:145)
        at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:890)
        at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:659)
        at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)
        at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1349)
        at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:395)
        at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:220)
        at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:208)
        at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:130)
        at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:152)
        at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:148)
        at java.security.AccessController.doPrivileged(Native Method)
        at javax.security.auth.Subject.doAs(Subject.java:422)
        at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:92)
        at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:148)
        at org.jboss.as.protocol.mgmt.AbstractMessageHandler$ManagementRequestContextImpl$1.doExecute(AbstractMessageHandler.java:363)
        at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:472)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:748)
        at org.jboss.threads.JBossThread.run(JBossThread.java:320)
      Show
      CLI command sequence to reproduce this issue in standalone mode as follows: /core-service=management/access=audit/periodic-rotating-file-handler=myhandler:add(formatter="json-formatter", max-failure-count=20, path="audit-jmx.log", relative-to="jboss.server.data.dir", suffix=".yyyy-MM-dd") /subsystem=jmx/configuration=audit-log:add() /subsystem=jmx/configuration=audit-log/handler=myhandler:add() ..... (*1) (*1) Excerpt from server.log – Error occurred by Step 3. 2018-04-09 12:07:41,350 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 3) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "jmx"), ("configuration" => "audit-log"), ("handler" => "myhandler") ]): java.lang.IllegalStateException: WFLYJMX0036: There is no handler called 'myhandler' at org.jboss.as.jmx.JmxAuditLogHandlerReferenceResourceDefinition$AuditLogHandlerReferenceAddHandler.populateModel(JmxAuditLogHandlerReferenceResourceDefinition.java:88) at org.jboss.as.controller.AbstractAddStepHandler.execute(AbstractAddStepHandler.java:145) at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:890) at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:659) at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370) at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1349) at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:395) at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:220) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:208) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:130) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:152) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:148) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:422) at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:92) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:148) at org.jboss.as.protocol.mgmt.AbstractMessageHandler$ManagementRequestContextImpl$1.doExecute(AbstractMessageHandler.java:363) at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:472) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748) at org.jboss.threads.JBossThread.run(JBossThread.java:320)

      Handlers configured as a periodic-rotating-file-handler in /core-service=management/access=audit cannot be added in /subsystem=jmx/configuration=audit-log with "WFLYJMX0036: There is no handler called 'handler name'" message.

              yborgess1@redhat.com Yeray Borges Santana
              rhn-support-myoshida Masato Yoshida
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: