Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 22452 invoked from network); 4 Nov 2008 15:03:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Nov 2008 15:03:09 -0000 Received: (qmail 17673 invoked by uid 500); 4 Nov 2008 15:03:14 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 17659 invoked by uid 500); 4 Nov 2008 15:03:14 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 17648 invoked by uid 99); 4 Nov 2008 15:03:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Nov 2008 07:03:14 -0800 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Nov 2008 15:01:56 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1KxNQT-0007mE-E5 for users@activemq.apache.org; Tue, 04 Nov 2008 07:02:37 -0800 Message-ID: <20323978.post@talk.nabble.com> Date: Tue, 4 Nov 2008 07:02:37 -0800 (PST) From: selezovikj To: users@activemq.apache.org Subject: Re: Commons-logging conflict with failover In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: semir.elezovic@gmail.com References: <20323028.post@talk.nabble.com> <20323586.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org I am not sending ActiveMQ logging information to the JMS appender. __________________________________ Logger messageLogger = Logger.getLogger("MSGSTATS"); messageLogger.info("Client logs to 61617"); __________________________________ The MSGSTATS (in the log4j.properties) uses the MessageLog and the jms appender: ___________________________________________________ log4j.category.MSGSTATS=DEBUG,MessageLog, jms log4j.additivity.MSGSTATS=false log4j.appender.MessageLog=biz.minaret.log4j.DatedFileAppender log4j.appender.MessageLog.Directory=../logs/ log4j.appender.MessageLog.Prefix=msg${PROCESS}. log4j.appender.MessageLog.Suffix=.log log4j.appender.MessageLog.layout=org.apache.log4j.PatternLayout log4j.appender.MessageLog.layout.ConversionPattern=%d#%c{1}#STATS#%x%m%n log4j.appender.jms=org.apache.log4j.net.JMSAppender log4j.appender.jms.TopicBindingName=LoggingTopic log4j.appender.jms.topicConnectionFactoryBindingName=ConnectionFactory log4j.appender.jms.layout=org.apache.log4j.PatternLayout log4j.appender.jms.layout.ConversionPattern=%d#%c{1}#STATS#%x%m%n -------------------------------------------------------------------------------------------------------------------------------------------- Can you please tell me what do you mean by ActiveMQ logging information ? Do you mean the information that the failover logs when it connects ? And what does this have to do with commons-logging ? James.Strachan wrote: > > You should not be sending ActiveMQ logging information to the JMS > appender right? Otherwise its catch 22; you can't connect until you've > logged and can't log until you've connected. > > > 2008/11/4 selezovikj : >> >> Yes, I am using the JMS appender and in the jndi.properties file I >> specify >> "failover:(tcp://localhost:61617)" as the value for the providerURL. >> I have a simple client logging messages using the JMS appender. >> Commons-logging is logging to a jms appender when I am NOT using the >> failover transport. >> On the other hand, when I use log4j only, it successfully logs when I use >> the failover transport. This is the output I get when I only use log4j: >> >> Nov 4, 2008 3:36:03 PM >> org.apache.activemq.transport.failover.FailoverTransport doReconnect >> INFO: Successfully connected to tcp://localhost:61617 >> >> I really really want to use the failover transport. Is there any way to >> fix >> the problem you mentioned ? >> If failover uses logging to indicate when it is connected and somehow >> commons-logging does not allow this, is there a way to forcefully >> initialize >> logging so that failover can log successfully and not block ? >> >> Thank you very much in advance >> >> >> >> >> James.Strachan wrote: >>> >>> >>> >>> Are you using the JMS appender as well by any chance? Do you get any >>> logging output? >>> >>> FWIW the failover transports uses logging to indicate when its >>> connected; so if logging is not working it might block >>> -- >>> James >>> ------- >>> http://macstrac.blogspot.com/ >>> >>> Open Source Integration >>> http://fusesource.com/ >>> >>> >> >> -- >> View this message in context: >> http://www.nabble.com/Commons-logging-conflict-with-failover-tp20323028p20323586.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> >> > > > > -- > James > ------- > http://macstrac.blogspot.com/ > > Open Source Integration > http://fusesource.com/ > > -- View this message in context: http://www.nabble.com/Commons-logging-conflict-with-failover-tp20323028p20323978.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.