Thanks for the info Robbie.
In fact that way I solved the problem, once I remove the log4j
implementation of the SLF4J and put the jdk one, the application worked well
--
View this message in context:
http://qpid.2158936.n2.nabble.com/The-AMQConnection-class-fail-to-connect-when-use-in-log4j
Madinaveitia 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-fai
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
.apache.log4j.LogManager.(LogManager.java:127)
> at org.apache.log4j.Logger.getLogger(Logger.java:117)
> at com.wfg.testqpid.TheTest.(TheTest.java:16)
> Caused by: org.apache.qpid.AMQException: Cannot connect to broker: close()
> timed out [error code 200: reply success]
> at
>
> org.apache.qpid.c
nDelegate_0_10.makeBrokerConnection(AMQConnectionDelegate_0_10.java:221)
... 16 more
--
View this message in context:
http://qpid.2158936.n2.nabble.com/The-AMQConnection-class-fail-to-connect-when-use-in-log4j-appender-tp7606582.html
Sent from the Apache Qpid users mailing list archiv
