Commons-logging conflict with failover

2008-11-04 Thread selezovikj
://www.nabble.com/Commons-logging-conflict-with-failover-tp20323028p20323028.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Commons-logging conflict with failover

2008-11-04 Thread James Strachan
2008/11/4 selezovikj [EMAIL PROTECTED]: I am using log4j to send logging events to a topic on an ActiveMQ broker. I use the failover transport to specify a secondary host and automatic reconnection. When the commons-logging.jar is in the classpath the failover transport is blocking. Are you

Re: Commons-logging conflict with failover

2008-11-04 Thread selezovikj
--- 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.

Re: Commons-logging conflict with failover

2008-11-04 Thread James Strachan
2008/11/4 selezovikj [EMAIL PROTECTED]: 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

Re: Commons-logging conflict with failover

2008-11-04 Thread James Strachan
2008/11/4 selezovikj [EMAIL PROTECTED]: So failover tries to log that it is connected, but it cannot log since it is not connected. But, my question is: connected where ? Why doesn't failover log locally that it is connected ? Why can't it log without being connected ? It can just log

Re: Commons-logging conflict with failover

2008-11-04 Thread selezovikj
Dejan's suggestion? -- 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-tp20323028p20324814.html Sent from the ActiveMQ - User mailing list archive

Re: Commons-logging conflict with failover

2008-11-04 Thread selezovikj
://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

Re: Commons-logging conflict with failover

2008-11-04 Thread selezovikj
/log ? -- View this message in context: http://www.nabble.com/Commons-logging-conflict-with-failover-tp20323028p20325590.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Commons-logging conflict with failover

2008-11-04 Thread James Strachan
2008/11/4 selezovikj [EMAIL PROTECTED]: System.out.println(before declaration); final Log log = LogFactory.getLog(MSGSTATS); System.out.println(after declaration); after declaration is never printed out. So commons-logging initializes a Log, which initializes log4j by reading the

Re: Commons-logging conflict with failover

2008-11-04 Thread selezovikj
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

Re: Commons-logging conflict with failover

2008-11-04 Thread James Strachan
://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