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 read
connected.
Any way to tell failover to not block/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.
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 ?
>
ne where these log
> messages go (locally versus remotely over JMS etc).
>
> Did you try Dejan's suggestion?
>
> --
> James
> ---
> http://macstrac.blogspot.com/
>
> Open Source Integration
> http://fusesource.com/
>
>
--
View this message in cont
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
ou 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
>
> --
>
>>>>
>>>> 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 b
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 M
t;>
>>>
>>>
>>> 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
>>>
WIW 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/
>>
>>
ging 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.
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.
://www.nabble.com/Commons-logging-conflict-with-failover-tp20323028p20323028.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
13 matches
Mail list logo
