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
/Users/supun/dev/wso2/trunk/carbon/products/esb/modules/distribution/product/target/wso2esb-4.0.0-SNAPSHOT/repository/conf/qpid/etc/log4j.xml
Using the fallback internal log4j.properties configuration
[Broker] BRK-1001 : Startup : Version: 0.9 Build: 1041962M
[Broker] MNG-1001 : Startup
[Broker] MNG-1004 : Ready : Using the platform JMX Agent
[Broker] BRK-1002 : Starting : Listening on TCP port 5672
[Broker] BRK-1004 : Qpid Broker Ready


Thanks,
Supun..

On Wed, Mar 30, 2011 at 10:09 AM, Isuru Suriarachchi <[email protected]> wrote:
> 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 <[email protected]>
> wrote:
>>
>> Yes. Will change that.
>>
>> Danushka
>>
>> On Tue, Mar 29, 2011 at 7:33 PM, Supun Kamburugamuva <[email protected]>
>> wrote:
>>>
>>> On Tue, Mar 29, 2011 at 7:29 PM, Sumedha Rubasinghe <[email protected]>
>>> 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 messages to WARN in our log4j configuration.
>>>
>>> Yes, that was the exact thing I have in my mind as well.
>>>
>>> Thanks,
>>> Supun..
>>>
>>> > /sumedha
>>> >
>>> > On Tue, Mar 29, 2011 at 6:17 PM, Supun Kamburugamuva <[email protected]>
>>> > wrote:
>>> >>
>>> >> 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; http://www.apache.org
>>> >> WSO2 Inc.;  http://wso2.org
>>> >> E-mail: [email protected];  Mobile: +94 77 431 3585
>>> >> Blog: http://supunk.blogspot.com
>>> >> _______________________________________________
>>> >> Carbon-dev mailing list
>>> >> [email protected]
>>> >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>> >
>>> >
>>>
>>>
>>>
>>> --
>>> Supun Kamburugamuva
>>> Technical Lead &  Product Manager, WSO2 Inc.; http://wso2.com
>>> Member, Apache Software Foundation; http://www.apache.org
>>> WSO2 Inc.;  http://wso2.org
>>> E-mail: [email protected];  Mobile: +94 77 431 3585
>>> Blog: http://supunk.blogspot.com
>>> _______________________________________________
>>> Carbon-dev mailing list
>>> [email protected]
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>> _______________________________________________
>> Carbon-dev mailing list
>> [email protected]
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>
>
>
> --
> Isuru Suriarachchi
> Technical Lead & Product Manager, WSO2 Application Server
> WSO2 Inc. http://wso2.com
> email : [email protected]
> blog : http://isurues.wordpress.com/
>
> lean . enterprise . middleware
>
>
> _______________________________________________
> Carbon-dev mailing list
> [email protected]
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>



-- 
Supun Kamburugamuva
Technical Lead &  Product Manager, WSO2 Inc.; http://wso2.com
Member, Apache Software Foundation; http://www.apache.org
WSO2 Inc.;  http://wso2.org
E-mail: [email protected];  Mobile: +94 77 431 3585
Blog: http://supunk.blogspot.com
_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to