There are so many logs from qpid when starting the ESB. Shall we make
these logs to warn level because these are not directly related to ESB
functionality?
Thanks,
--
Supun Kamburugamuva
Technical Lead Product Manager, WSO2 Inc.; http://wso2.com
Member, Apache Software Foundation;
This is common to all products. I tested G-Reg, DSS,GS BAM from trunk and
those log files from QPid are visible on those as well.
These are coming from QPid. The solution is to raise the verbose level for
QPid log messages to WARN in our log4j configuration.
/sumedha
On Tue, Mar 29, 2011 at
On Tue, Mar 29, 2011 at 7:29 PM, Sumedha Rubasinghe sume...@wso2.com wrote:
This is common to all products. I tested G-Reg, DSS,GS BAM from trunk and
those log files from QPid are visible on those as well.
These are coming from QPid. The solution is to raise the verbose level for
QPid log
I've already done that in Carbon core log4j.properties file. But there are
some system outs still coming from Qpid.
Thanks,
~Isuru
On Wed, Mar 30, 2011 at 7:29 AM, Danushka Menikkumbura danus...@wso2.comwrote:
Yes. Will change that.
Danushka
On Tue, Mar 29, 2011 at 7:33 PM, Supun
Yes, we should get rid of the following system outs
[Broker] BRK-1006 : Using configuration :
/Users/supun/dev/wso2/trunk/carbon/products/esb/modules/distribution/product/target/wso2esb-4.0.0-SNAPSHOT/repository/conf/qpid/etc/config.xml
Logging configuration error: unable to read file
Worse case is if you happen to invoke a queue defined on the broker, there
will be another set of logs that get printed per each request. We need to
get rid of them as well, otherwise this will add performance bottlenecks.
Rajika
On Wed, Mar 30, 2011 at 11:13 AM, Supun Kamburugamuva
