You should not be sending ActiveMQ logging information to the JMS appender right? Otherwise its catch 22; you can't connect until you've logged and can't log until you've connected.
2008/11/4 selezovikj <[EMAIL PROTECTED]>: > > Yes, I am using the JMS appender and in the jndi.properties file I specify > "failover:(tcp://localhost:61617)" as the value for the providerURL. > I have a simple client logging messages using the JMS appender. > Commons-logging is logging to a jms appender when I am NOT using the > failover transport. > On the other hand, when I use log4j only, it successfully logs when I use > the failover transport. This is the output I get when I only use log4j: > > Nov 4, 2008 3:36:03 PM > org.apache.activemq.transport.failover.FailoverTransport doReconnect > INFO: Successfully connected to tcp://localhost:61617 > > I really really want to use the failover transport. Is there any way to fix > the problem you mentioned ? > If failover uses logging to indicate when it is connected and somehow > commons-logging does not allow this, is there a way to forcefully initialize > logging so that failover can log successfully and not block ? > > Thank you very much in advance > > > > > James.Strachan wrote: >> >> >> >> Are you using the JMS appender as well by any chance? Do you get any >> logging output? >> >> FWIW the failover transports uses logging to indicate when its >> connected; so if logging is not working it might block >> -- >> 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-tp20323028p20323586.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://fusesource.com/
