activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <>
Subject Re: How to change debug level of CLIENT applications ( inactivity Monitor logging)
Date Thu, 23 Mar 2017 13:01:35 GMT
In a client application, ActiveMQ is just one JAR (or several) that's part
of a much larger whole. The client application establishes how logging will
be done, and ActiveMQ plays by those rules. Since you're seeing ActiveMQ
content in the client logs, this is already working, and your job is to
find the files that control logging and add your content to it, *not*
define your own new file and try to get the logging framework to use it. If
the client is using Log4J, it might be controlled by either a properties
file or an XML file, so you'll need to find out which and apply your
changes to it in the appropriate syntax. If it's a different logging
framework (e.g. Java Util Logging), then it has its own control file and
format and you'll use that.


On Mar 23, 2017 5:04 AM, "Francesco Furfari" <>


I searched in the documentation and archives how to change logging for
client applications but any my attempt doesn't work.

I use activemq 5.14.3 and my IDE is eclipse neon.

The problem is that I would like to remove debug info produced by:
InactivityMonitor Worker, WriteCheckTimer and ReadCheckTimer

It seems has no effect.
I pass  it as argument: -Dlog4j.configuration=file:src
the file is configured like:
log4j.rootCategory=INFO, out

I tried also to use the BrokerURL connector according the reference:
for instance "tcp://localhost:61616?trace=true&startLogging=false" used
with ActiveMQConnectionFactory(URL)
I have even tried to disable InactivityMonitor by adding  the parameter:
"useInactivityMonitor=false" without success.

Please can you give any hints?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message