One thing to try would be using an alternative SLF4J binding and logging implementation for the client itself (and anything else using SLF4J), such as the JDK logging binding, while retaining use of Log4J for your JMS appender and actual application.
Robbie On 9 April 2014 14:02, Miguel Madinaveitia <[email protected]>wrote: > For the client we also use log4j. > how do you solved the problem? to prevent the same client generates > problems > when writing to the log? > > > > -- > View this message in context: > http://qpid.2158936.n2.nabble.com/The-AMQConnection-class-fail-to-connect-when-use-in-log4j-appender-tp7606582p7606586.html > Sent from the Apache Qpid users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
