• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Enabling tracing for packages in Portal Sever

 
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All,

I have business classes in below package with logger.finest() statements. For troubleshooting purpose we always enable tracing in Websphere Portal to capture logger.finest statments.

com.xyz.abc.*=all;

After enabling above tracing, in log files I don't see logger.finest() statements but I see logger.info() which is by default. So I changed the package tracing level to com.xyz.abc.*=finest. But still no use.

Finally when we enable tracing like com.xyz.*=all , we started seeing logger.finest() statements in the trace for the classes under abc package. Though we able to get the loggers Im still confused why the initial trace setting was not working.

Any ideas why it is not working? Any server settings we are missing?

We use WPS 6.0.1.5 and WAS 6.0.2( i think).

Thanks,
Vijay.
 
If you believe you can tell me what to think, I believe I can tell you where to go. Go read this tiny ad!
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic