On Mon, Sep 7, 2009 at 4:21 PM, Jonathan Robiejonathan.ro...@redhat.com wrote:
Isn't the Java client's output determined by the log4j file (log4j.xml)?
Not really, no. Except, maybe. Kinda. The client uses SLF4J, which can
use log4j which could use java/broker/etc/log4j.xml (but doesn't
unless
ExchangeDelete(exchange=emisor2)
Thread-2 2009-09-07 10:06:53,319 DEBUG [apache.qpid.transport.Connection]
FLUSH: [conn:18f6235]
.
How can I change the configuration of the broker to disable this feature?
Thank you very much!
--
View this message in context:
http://n2.nabble.com/How-can-I-disable
Hello!
On Mon, Sep 07, 2009 at 03:18:26AM -0500, ricardlf wrote:
When I execute a program using qpid I'm getting message like these:
Thread-2 2009-09-07 10:06:53,318 DEBUG [apache.qpid.transport.Connection]
FLUSH: [conn:18f6235]
Thread-2 2009-09-07 10:06:53,319 DEBUG
- AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscr...@qpid.apache.org
--
View this message in context:
http://n2.nabble.com/How-can-I-disable-the-trace-printing-of-Qpid-tp3596044p3596502.html
Sent from the Apache Qpid users mailing list
Isn't the Java client's output determined by the log4j file (log4j.xml)?
If it's still the way it used to be, you can change the level in the
logger to trace, debug, info, warn, error or fatal:
logger name=org.apache
level value=warn/
/logger
I haven't looked at this for quite a
