On Mon, May 10, 2010 at 1:40 PM, Rajika Kumarasiri <raj...@wso2.com> wrote: > On Mon, Mar 8, 2010 at 9:12 PM, Rajith Attapattu <rajit...@gmail.com> wrote: > >> Hi All, >> >> The current out of the box performance for the java client is somewhat >> impacted by the log4j issues. >> > > What exactly are the issues (sorry if this question is answered before, I > couldn't find any)? I have seen code which uses log4j extensively for > logging, but still serving couple of thousands transactions per second.
This is explained in detail in the first email I sent on this thread. http://apache-qpid-developers.2158895.n2.nabble.com/Java-Client-Logging-yet-again-td4696020.html#a4696020 The problem is, if log4j is not configured properly, it results in defaulting to DEBUG level. In DEBUG level we print a hell of a lot of details which slows down the performance by quite a bit. Also since the whole point of having a logging facade like slf4j is to allow the users to config their own logging, we shouldn't really be ship any bindings. Rajith > Rajika > > > -- > http://rajikak.blogspot.com/ > -- Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/ --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
