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 locally.
Is this something that will be fixed in the coming releases ?
And my biggest question: Is there a way to solve my problem ?
Or do I have to program manually the automatic reconnection feature that
failover provides ?
Thank you very much
James.Strachan wrote:
>
> 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 the log4j.properties) uses the MessageLog and the jms
>> appender:
>> ___________________________________________________
>> log4j.category.MSGSTATS=DEBUG,MessageLog, jms
>> log4j.additivity.MSGSTATS=false
>> log4j.appender.MessageLog=biz.minaret.log4j.DatedFileAppender
>> log4j.appender.MessageLog.Directory=../logs/
>> log4j.appender.MessageLog.Prefix=msg${PROCESS}.
>> log4j.appender.MessageLog.Suffix=.log
>> log4j.appender.MessageLog.layout=org.apache.log4j.PatternLayout
>> log4j.appender.MessageLog.layout.ConversionPattern=%d#%c{1}#STATS#%x%m%n
>>
>> log4j.appender.jms=org.apache.log4j.net.JMSAppender
>> log4j.appender.jms.TopicBindingName=LoggingTopic
>> log4j.appender.jms.topicConnectionFactoryBindingName=ConnectionFactory
>> log4j.appender.jms.layout=org.apache.log4j.PatternLayout
>> log4j.appender.jms.layout.ConversionPattern=%d#%c{1}#STATS#%x%m%n
>> --------------------------------------------------------------------------------------------------------------------------------------------
>>
>> Can you please tell me what do you mean by ActiveMQ logging information ?
>> Do
>> you mean the information that the failover logs when it connects ?
>
> Yes
>
>> And what does this have to do with commons-logging ?
>
> ActiveMQ uses commons-logging to log
>
> --
> 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-tp20323028p20324501.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
