As long as the third-party jar is under the lib dir. no log messages appear what-so-ever. As soon as I remove the jar, then using the -Dlog4j.debug=true I get the messages below in the activemq.log. There's nothing that indicates where where log4j takes its conf. file !! However I think it is the conf/log4j.properties, since changes to that affect the logging.
The JVM args are: JVM args: -Xms1G -Xmx1G -Djava.util.logging.config.file=logging.properties -Dlog4j.debug=true -Dactivemq.classpath=/usr/local/activemq/conf; -Dactivemq.home=/usr/local/activemq -Dactivemq.base=/usr/local/activemq -Dactivemq.conf=/usr/local/activemq/conf - Dactivemq.data=/usr/local/activemq/data ======= 2013-09-02 16:09:27,437 | INFO | Refreshing org.apache.activemq.xbean.XBeanBrokerFactory$1@7ee49dcd: startup date [Mon Sep 02 16:09:27 CEST 2013]; root of context hierarchy | org.apache.activemq.xbean.XBeanBrokerFactory$1 | main 2013-09-02 16:09:28,286 | INFO | PListStore:[/usr/local/activemq/data/local/tmp_storage ] started | org.apache.activemq.store.kahadb.plist.PListStore | main 2013-09-02 16:09:28,393 | INFO | Using Persistence Adapter: KahaDBPersistenceAdapter[/usr/local/activemq/data/kahadb] | org.apache.activemq.broker.BrokerService | main 2013-09-02 16:09:28,398 | INFO | JMX consoles can connect to service:jmx:rmi://localhost:11098/jndi/rmi://localhost:11099/jmxrmi | org.apache.activemq.broker.jmx.ManagementContext | JMX connector 2013-09-02 16:09:28,590 | INFO | KahaDB is version 4 | org.apache.activemq.store.kahadb.MessageDatabase | main 2013-09-02 16:09:28,610 | INFO | Recovering from the journal ... | org.apache.activemq.store.kahadb.MessageDatabase | main 2013-09-02 16:09:28,610 | INFO | Recovery replayed 1 operations from the journal in 0.012 seconds. | org.apache.activemq.store.kahadb.MessageDatabase | main 2013-09-02 16:09:28,618 | INFO | ActiveMQ 5.6.0 JMS Message Broker (local) is starting | org.apache.activemq.broker.BrokerService | main 2013-09-02 16:09:28,618 | INFO | For help or more information please see: http://activemq.apache.org/ | org.apache.activemq.broker.BrokerService | main 2013-09-02 16:09:28,741 | INFO | Scheduler using directory: /usr/local/activemq/data/local/scheduler | org.apache.activemq.broker.scheduler.SchedulerBroker | main 2013-09-02 16:09:28,753 | INFO | Installing StaticsBroker | org.apache.activemq.plugin.StatisticsBrokerPlugin | main 2013-09-02 16:09:28,842 | INFO | ignoring zero length, partially initialised journal data file: db-1.log number = 1 , length = 0 | org.apache.kahadb.journal.Journal | main 2013-09-02 16:09:28,848 | INFO | JobSchedulerStore:/usr/local/activemq/data/local/scheduler started | org.apache.activemq.broker.scheduler.JobSchedulerStore | main 2013-09-02 16:09:28,865 | INFO | Starting StatisticsBroker | org.apache.activemq.plugin.StatisticsBroker | main 2013-09-02 16:09:28,879 | INFO | Listening for connections at: tcp://shico.nordija.dk:61616 | org.apache.activemq.transport.TransportServerThreadSupport | main 2013-09-02 16:09:28,879 | INFO | Connector openwire Started | org.apache.activemq.broker.TransportConnector | main 2013-09-02 16:09:28,881 | INFO | ActiveMQ JMS Message Broker (local, ID:shico.nordija.dk-54546-1378130968627-0:1) started | org.apache.activemq.broker.BrokerService | main 2013-09-02 16:09:28,939 | INFO | jetty-7.6.1.v20120215 | org.eclipse.jetty.server.Server | main 2013-09-02 16:09:29,079 | INFO | ActiveMQ WebConsole initialized. | org.apache.activemq.web.WebConsoleStarter | main 2013-09-02 16:09:29,080 | INFO | started o.e.j.w.WebAppContext{/admin,file:/usr/local/apache-activemq-5.6.0/webapps/admin/} | org.eclipse.jetty.server.handler.ContextHandler | main 2013-09-02 16:09:29,096 | INFO | Logging to org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog | org.mortbay.log | main 2013-09-02 16:09:29,129 | INFO | Initializing Spring FrameworkServlet 'dispatcher' | /admin | main 2013-09-02 16:09:29,230 | INFO | ActiveMQ Console at http://0.0.0.0:8161/admin | org.eclipse.jetty.webapp.WebAppContext | main 2013-09-02 16:09:29,243 | INFO | started o.e.j.w.WebAppContext{/demo,file:/usr/local/apache-activemq-5.6.0/webapps/demo} | org.eclipse.jetty.server.handler.ContextHandler | main 2013-09-02 16:09:29,244 | INFO | WebApp@1933139371 at http://0.0.0.0:8161/demo | org.eclipse.jetty.webapp.WebAppContext | main 2013-09-02 16:09:29,259 | INFO | started o.e.j.w.WebAppContext{/fileserver,file:/usr/local/apache-activemq-5.6.0/webapps/fileserver} | org.eclipse.jetty.server.handler.ContextHandler | main 2013-09-02 16:09:29,259 | INFO | WebApp@1933139371 at http://0.0.0.0:8161/fileserver | org.eclipse.jetty.webapp.WebAppContext | main 2013-09-02 16:09:29,325 | INFO | Initializing Spring root WebApplicationContext | /amq-ajax-connector | main 2013-09-02 16:09:29,496 | INFO | started o.e.j.w.WebAppContext{/amq-ajax-connector,file:/usr/local/apache-activemq-5.6.0/webapps/amq-ajax-connector/} | org.eclipse.jetty.server.handler.ContextHandler | main 2013-09-02 16:09:29,501 | INFO | MessageServlet init-param: protocolVer = v2 | com.nordija.activemq.web.MessageServletFilter | main 2013-09-02 16:09:29,501 | INFO | MessageServlet init-param: timeToLive = 86400000 | com.nordija.activemq.web.MessageServletFilter | main 2013-09-02 16:09:29,502 | INFO | MessageServlet init-param: destination = stat.inbound | com.nordija.activemq.web.MessageServletFilter | main 2013-09-02 16:09:29,502 | INFO | MessageServlet init-param: type = queue | com.nordija.activemq.web.MessageServletFilter | main 2013-09-02 16:09:29,511 | INFO | Initializing Spring FrameworkServlet 'pinger' | /amq-ajax-connector | main 2013-09-02 16:09:29,612 | INFO | Nordija's Web Interface to ActiveMQ at http://0.0.0.0:8161/amq-ajax-connector | org.eclipse.jetty.webapp.WebAppContext | main 2013-09-02 16:09:29,637 | INFO | Started [email protected]:8161 | org.eclipse.jetty.server.AbstractConnector | main =========== Regards, -Farhad On Sep 2, 2013, at 3:47 PM, gtully [via ActiveMQ] <[email protected]> wrote: > 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 <[hidden email]> 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 > > > If you reply to this email, your message will be added to the discussion > below: > http://activemq.2283324.n4.nabble.com/Adding-a-third-party-jar-to-the-lib-dir-disables-logging-tp4671024p4671026.html > To unsubscribe from Adding a third-party jar to the lib dir. disables logging > ??!!, click here. > NAML -- View this message in context: http://activemq.2283324.n4.nabble.com/Adding-a-third-party-jar-to-the-lib-dir-disables-logging-tp4671024p4671028.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
