]
James Perkins updated WFLY-12236:
---------------------------------
Workaround Description:
Configure the logging subsystem to limit the offending category to WARN or higher
severity:
{code}
<logger category="org.apache.activemq.audit.base">
<level name="WARN"/>
</logger>
{code}
CLI examples for both the {{org.apache.activemq.audit.base}} and
{{org.apache.activemq.audit.message}} categories.
{code}
/subsystem=logging/logger=org.apache.activemq.audit.base:add(level=WARN)
/subsystem=logging/logger=org.apache.activemq.audit.message:add(level=WARN)
{code}
was:
Configure the logging subsystem to limit the offending category to WARN or higher
severity:
{code}
<logger category="org.apache.activemq.audit.base">
<level name="WARN"/>
</logger>
{code}
Log spam in category org.apache.activemq.audit.base
---------------------------------------------------
Key: WFLY-12236
URL:
https://issues.jboss.org/browse/WFLY-12236
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 17.0.0.Final
Reporter: Brian Stansberry
Assignee: Emmanuel Hugonnet
Priority: Blocker
Fix For: 18.0.0.Beta1
Artemis is spamming the logs with what look like low-level messages, but recorded at INFO
level:
{code}
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]]
{code}