activemq uses slf4j over log4j by default and picks up log4j.configuration from ./conf/log4j.properties
use -Dlog4j.debug=true as a jvm system property on the start script and activemq --console to see where log4j is getting its configuration from in your case. log4j.debug causes log4j to system.out its config On 2 September 2013 14:22, farhad <m...@farhad.eu> wrote: > Hi, > Has anybody ever encountered the same problem as I'm having right now? The > problem is that whenever I copy a jar-file (a jar file consisting a single > java class) of my own into the lib directory, then activemq stops logging. > The jar file is needed since I have a couple of route definitions in the > activemq.xml which invokes the class in the jar. > Apart from logging everything runs without any problem. > > I appreciate any help. > Regards, > Farhad Dehghani > > > ActiveMQ: 5.6.0 > java version: "1.6.0_51" > OS: Mac osx > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Adding-a-third-party-jar-to-the-lib-dir-disables-logging-tp4671024.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://redhat.com http://blog.garytully.com
