Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of chirino@gmail.com designates
 209.85.219.218 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=Vf39C2VtGoejfhCHmSA4YzgM7i3RgTpqs6hbuOosAhQBUzraU+h2eqVkQiWsU0hq5A
         613tgGrhQ7vElc3Nlfuko9AeQGOguzYyuhAGfHV8EKtET0yxilu3d+xmOYpksByw/pmr
         uVyH9G+V2bhn27TOrOnzRBq1y8/x3qmKC3MOc=
MIME-Version: 1.0
In-Reply-To: <3a73c17c0908070200i7e6d5f15h5693fd38818fb71c@mail.gmail.com>
References: <14622389.post@talk.nabble.com> <24860244.post@talk.nabble.com>
	 <3a73c17c0908070200i7e6d5f15h5693fd38818fb71c@mail.gmail.com>
Date: Fri, 7 Aug 2009 10:36:46 -0400
Message-ID: <af2843cd0908070736ybdc8bcct63df61d533e939ee@mail.gmail.com>
Subject: Re: ActiveMQ 5 and Log4j JMSAppender error
From: Hiram Chirino <chirino@gmail.com>
To: users@activemq.apache.org
Content-Type: multipart/alternative; boundary=0016364c7dd77c1aff04708e2afc

--0016364c7dd77c1aff04708e2afc
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Wonder if we should just filter out our own log messages in the JMS
appender, that way users can never get bitten by this problem.

On Fri, Aug 7, 2009 at 5:00 AM, Gary Tully <gary.tully@gmail.com> wrote:

> great. thanks for completing the loop on this by sharing your solution :-)
>
> 2009/8/7 Kinski <matthew.cosgrove@192.com>
>
> >
> > I added the suffix to the brokerURL
> >
> > I.e.
> >
> >
> log4j.appender.JMS.ProviderURL=tcp://localhost:61616?wireFormat.cacheEnabled=false
> >
> > but this made no difference.
> >
> > then finally found my needle in the haystack with this nugget of
> > information..
> >
> http://www.nabble.com/Log4J-ActiveMQ-JMS-Appender-td18840199.html#a19970509
> >
> >
> > Gary Tully wrote:
> > >
> > > can you run with -Dlog4j.debug (set the system property) to see where
> > > the log4j configuration is coming from?
> > >
> > > It may be that the wireFormatNegotiator is trying to log a message
> > > which is trying to start a jms connection which uses
> > > wireFormatNegotiator etc. Chicken and egg.
> > > logging for activemq needs to be disabled if it is used as a default
> > > appender.
> > >
> > >
> >
> > Put the following in my log4j config and Hey Presto....
> >
> > <!-- THIS IS CRITICAL FOR THE JMS APPENDER NOT TO FAIL -->
> > <logger name="org.apache.activemq">
> > <!-- active mq logging must be disabled -->
> > <level value="ERROR" />
> > </logger>
> >
> > --
> > View this message in context:
> >
> http://www.nabble.com/ActiveMQ-5-and-Log4j-JMSAppender-error-tp14622389p24860244.html
> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> >
> >
>
>
> --
> http://blog.garytully.com
>
> Open Source Integration
> http://fusesource.com
>


-- 
Regards,
Hiram

Blog: http://hiramchirino.com

Open Source SOA
http://fusesource.com/

--0016364c7dd77c1aff04708e2afc--