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

Log spam in category org.apache.activemq.audit.base

XMLWordPrintable

    • Workaround Exists
    • Hide

      Configure the logging subsystem to limit the offending category to WARN or higher severity:

                  <logger category="org.apache.activemq.audit.base">
                <level name="WARN"/>
            </logger>

      CLI examples for both the org.apache.activemq.audit.base and org.apache.activemq.audit.message categories.

      /subsystem=logging/logger=org.apache.activemq.audit.base:add(level=WARN)
/subsystem=logging/logger=org.apache.activemq.audit.message:add(level=WARN)
      Show
      Configure the logging subsystem to limit the offending category to WARN or higher severity: <logger category= "org.apache.activemq.audit.base" > <level name= "WARN" /> </logger> CLI examples for both the org.apache.activemq.audit.base and org.apache.activemq.audit.message categories. /subsystem=logging/logger=org.apache.activemq.audit.base:add(level=WARN) /subsystem=logging/logger=org.apache.activemq.audit.message:add(level=WARN)

      Artemis is spamming the logs with what look like low-level messages, but recorded at INFO level:

      14:43:29,427 INFO  [org.apache.activemq.audit.base] (Thread-40 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@39c78b17)) AMQ601265: User 4dd3d543-be6a-4a9a-b5d2-5cac9efe8f0f is creating a core consumer on target resource ServerSessionI mpl(jms-session=*N/A*) [with parameters: [175, jms.queue.DCS_DEV.processDcsIntegrationQueue, null, 0, false, true, null]]

              jperkins-rhn James Perkins
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: