| log4J.properties loaded twice when profiling with CBE to log [message #106023] |
Fri, 20 July 2007 18:37  |
Eclipse User |
|
|
|
Originally posted by: wrobinson.gsu.edu
When I profile with the option, CBE to log, then log4J.properties loaded
twice. I suspect it may be a bug. :-)
I'm using the newest TPTP 4.4, downloaded with the eclipse update manager.
Open Profile dialog
Select monitor
Select Common Base Event Analysis (CBE) and edit the options to "output CBE
to Log Facility"
When I run it, the log shows that log4J.properties is loaded twice.
Moreover, it seems that the second load only loads 'log4J.properties'. This
has been a problem, because I am using log4j.xml.
I resolved this problem by making a empty log4J.properties in addition to my
log4j.xml file. Now, my properties are not overriden by the default
log4J.properties.
|
|
|
| Re: log4J.properties loaded twice when profiling with CBE to log [message #106527 is a reply to message #106023] |
Wed, 25 July 2007 15:15  |
 Matt Mings
Messages: 3
Registered: July 2009 |
Junior Member |
|
|
Hi wrobinson,
This is a bug within the CBE monitoring code, by default the
log4j.properties file is load by default and the xml file is never checked.
The work around that you supplied appears to be correct for now. I have
open a defect and have targeted it for 4.4.1.
Thank you for using the CBE monitoring, also what version of log4j are you
using.
Thanks again,
Matt Mings
<wrobinson@gsu.edu> wrote in message news:f7qvdo$et0$1@build.eclipse.org...
> When I profile with the option, CBE to log, then log4J.properties loaded
> twice. I suspect it may be a bug. :-)
>
> I'm using the newest TPTP 4.4, downloaded with the eclipse update manager.
> Open Profile dialog
> Select monitor
> Select Common Base Event Analysis (CBE) and edit the options to "output
> CBE to Log Facility"
>
> When I run it, the log shows that log4J.properties is loaded twice.
> Moreover, it seems that the second load only loads 'log4J.properties'.
> This has been a problem, because I am using log4j.xml.
>
> I resolved this problem by making a empty log4J.properties in addition to
> my log4j.xml file. Now, my properties are not overriden by the default
> log4J.properties.
>
|
|
|
| Re: log4J.properties loaded twice when profiling with CBE to log [message #107559 is a reply to message #106527] |
Sat, 04 August 2007 20:14 |
| Eclipse User |
|
|
|
Originally posted by: wrobinson.gsu.edu
Thanks for the feedback.
I'm using log4j 1.3alpha-8
Also, thanks for the CBE profiling, it works great! :-)
"Matt Mings" <mmings@us.ibm.com> wrote in message
news:f87pdm$9np$1@build.eclipse.org...
> Hi wrobinson,
>
> This is a bug within the CBE monitoring code, by default the
> log4j.properties file is load by default and the xml file is never
> checked. The work around that you supplied appears to be correct for now.
> I have open a defect and have targeted it for 4.4.1.
>
> Thank you for using the CBE monitoring, also what version of log4j are you
> using.
>
> Thanks again,
>
> Matt Mings
>
> <wrobinson@gsu.edu> wrote in message
> news:f7qvdo$et0$1@build.eclipse.org...
>> When I profile with the option, CBE to log, then log4J.properties loaded
>> twice. I suspect it may be a bug. :-)
>>
>> I'm using the newest TPTP 4.4, downloaded with the eclipse update
>> manager.
>> Open Profile dialog
>> Select monitor
>> Select Common Base Event Analysis (CBE) and edit the options to "output
>> CBE to Log Facility"
>>
>> When I run it, the log shows that log4J.properties is loaded twice.
>> Moreover, it seems that the second load only loads 'log4J.properties'.
>> This has been a problem, because I am using log4j.xml.
>>
>> I resolved this problem by making a empty log4J.properties in addition to
>> my log4j.xml file. Now, my properties are not overriden by the default
>> log4J.properties.
>>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.01718 seconds
] 
Search
Help
Register
Login
Home
