Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 61312 invoked from network); 28 Oct 2008 12:41:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Oct 2008 12:41:27 -0000 Received: (qmail 57911 invoked by uid 500); 28 Oct 2008 12:41:31 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 57674 invoked by uid 500); 28 Oct 2008 12:41:30 -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 57663 invoked by uid 99); 28 Oct 2008 12:41:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Oct 2008 05:41:30 -0700 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, 28 Oct 2008 12:40:15 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1KunsQ-0000XG-3N for users@activemq.apache.org; Tue, 28 Oct 2008 05:40:50 -0700 Message-ID: <20206476.post@talk.nabble.com> Date: Tue, 28 Oct 2008 05:40:50 -0700 (PDT) From: selezovikj To: users@activemq.apache.org Subject: Re: Failover transport 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: <20130356.post@talk.nabble.com> <20131087.post@talk.nabble.com> <20148813.post@talk.nabble.com> <20149688.post@talk.nabble.com> <20151177.post@talk.nabble.com> <20205685.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org YES, I am using the log4j JMS appender. That is mentioned in my first message for this thread. In my simple client, I am using the log4j JMS appender, which appends messages to a JMS topic and it WORKS ! It doesn't give any problems. The problem occurs once I include the commons-logging JAR. I don't need the commons-logging jar in my simple client project, but I need it in my bigger project. I just add it to test whether that is causing problems. And yes, it is causing problems. So the main problem is the commons-logging JAR. The JMS appender CAN be used for ActiveMQ. James.Strachan wrote: > > 2008/10/28 James Strachan : > > > Ah - are you using the log4j JMS appender? Thats gonna cause a > cyclical dependency - logging cant' start until you're connected to > JMS etc. Make sure you don't use the JMS appender for ActiveMQ :) > > -- > James > ------- > http://macstrac.blogspot.com/ > > Open Source Integration > http://fusesource.com/ > > -- View this message in context: http://www.nabble.com/Failover-transport-tp20130356p20206476.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.