://www.nabble.com/Commons-logging-conflict-with-failover-tp20323028p20323028.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
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
---
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.
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
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
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
://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
/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.
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
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
://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
11 matches
Mail list logo