activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthias <>
Subject Re: ActiveMQ RAR - Logging
Date Wed, 14 Aug 2013 17:54:49 GMT
Hi all

I figured it out (mostly). The connector module is loaded by a different 
classloader than the EAR/WAR file, see
Therefore the connector module's SLF4J implementation is used as it's 
loaded earlier.

I posted my (lengthy) solution on StackOverflow (

Regards Matthias

On 08/12/2013 08:13 PM, Matthias wrote:
> Hi all
> I have deployed activemq-rar-5.8.0.rar to a GlassFish instance 
> (in order to connect to a remote broker, as described here 
> Unfortunately inside the connector is a SLF4J implementation which 
> causes all other projects on this application server to use Log4J as 
> logging implementation (even though they are packed with logback, i.e. 
> inside the EAR's or WAR's lib folder are the logback-core and the 
> logback-classic files).
> Does somebody know the solution to this? Why does the connector module 
> "binds" stronger than the logging implementation inside the EAR/WAR 
> files deployed to the same application server?
> I am aware that this is possible more a GlassFish specific question - 
> but so far I only experienced this issue with the connector module.
> Cheers and many thanks for your time & help
> Matthias

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message