Debug level log entry in a warning level log file
Hi guys, We encountered a strange problem in one of our Websphere Application Server's(8.5) java agent log.
The logging level and logstdout level is set to warning (loglevel=warning,logstdout=warning), though in the agent log i see a lot of debug level log entries:
This occurs every 4-6 ms, and generates a LOT of data (~110MB in 2 hours, so approx. 40GB in a month)... Did anyone else face this issue, or just us?
It's pretty annoying how could a debug level log entry exists in a log file which is restricted for warning (error) level logging... I even tried to override agent log level in the System Profile settings, but that didn't work either.
Thanks,
Tamás
The logging level and logstdout level is set to warning (loglevel=warning,logstdout=warning), though in the agent log i see a lot of debug level log entries:
2014-07-01 15:29:39 [00002080] debug [java ] jms-mayCapture: true
2014-07-01 15:29:39 [00002098] debug [java ] jms-mayCapture: true
2014-07-01 15:29:39 [00002080] debug [java ] jms-mayCapture: true
2014-07-01 15:29:39 [00001364] debug [java ] jms-mayCapture: true
2014-07-01 15:29:39 [00001364] debug [java ] jms-mayCapture: true
This occurs every 4-6 ms, and generates a LOT of data (~110MB in 2 hours, so approx. 40GB in a month)... Did anyone else face this issue, or just us?
It's pretty annoying how could a debug level log entry exists in a log file which is restricted for warning (error) level logging... I even tried to override agent log level in the System Profile settings, but that didn't work either.
Thanks,
Tamás
hi Tamás,
reason for this is that you have the debug flag "debugJMSIntrospectionJava" enabled for this agent. I guess you had a support case some time ago and you've been told to set this and then it was forgotten to be reset.
so you should check this:
- go into client debug mode (ctrl-shift-F9)
- go into the system profile to the agent mapping corresponding to this agent
- click 'debug' and then go to the "debug flags" tab
- see if the debug flag is set there
if it's not there it's also possible that it was set via the agent option string (-agentpath.....) so you should check this.
hope this helps,
Christian
Hi Christian,
Thank you for the fast response and accurate!
It was indeed a forgotten debug flag 
Regards,
Tamás
