activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ee7arh <>
Subject Re: Failover transport
Date Tue, 04 Nov 2008 12:52:16 GMT


Please could somebody explain exactly what is going wrong to hit this cyclic
redundancy problem?

The log4j JMSAppender is a very useful thing to have. We have created a
little jms logging server where we want clients (using the jmsAppender) to
be able to log to. We want to use the Failover transport so that clients can
automatically reconnect.

We setup a very simple logging client which uses Commons logging (and log4j
underneath), this then specifies a JMSAppender. Everything is fine until we
attempt to use the failover transport then it just stops.


James.Strachan wrote:
> 2008/10/28 James Strachan <>:
>> 2008/10/28 selezovikj <>:
>>> I wrote a simple client connecting to my activemq broker using the
>>> failover
>>> transport and it worked.
>>> Then I started adding the jar files that my bigger project uses, and at
>>> one
>>> point the same problem appeared: it was saying attempting to connect for
>>> hours.
>>> After some adding and removing of jar files, I saw that the problem
>>> causing
>>> this is the commons-logging-1.1.jar file.
>>> When I add that jar file the failover transport is useless.
>>> Any idea why this is so ?
>> Did you get any kind of stack trace?
> 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
> -------
> Open Source Integration

View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message