This week's book giveaway is in the Jobs Discussion forum.
We're giving away four copies of Java Interview Guide and have Anthony DePalma on-line!
See this thread for details.
The moose likes Portals and Portlets and the fly likes Enabling tracing for packages in Portal Sever Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Java Interview Guide this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Java » Portals and Portlets
Bookmark "Enabling tracing for packages in Portal Sever" Watch "Enabling tracing for packages in Portal Sever" New topic

Enabling tracing for packages in Portal Sever

vijay sagar MAA

Joined: Jun 22, 2007
Posts: 5
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.*=all;

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

Finally when we enable tracing like*=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 and WAS 6.0.2( i think).

I agree. Here's the link:
subject: Enabling tracing for packages in Portal Sever
It's not a secret anymore!