cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Importance of log files to trouble shoot Windchill Stack traces?

sdoiphode
6-Contributor

Importance of log files to trouble shoot Windchill Stack traces?

Why these files are very important to trouble shoot Windchill Stack traces?

    • Log Files – Method Server logs, PSM Captures ?
1 ACCEPTED SOLUTION

Accepted Solutions

Hi Supriya,

How are logs that provide Windchill stack traces important for troubleshooting Windchill instances?

In windchill there are loggers in most classes and these will return exception and errors directly or via handler to the windchill methodserver log.

These are useful as the trace will provide a path of what classes and methods have been called or invoked so you or Tech Support can track down where the exception may have occured. As Windchill evolves we are able to see that more clear messages of where the exception has occurred, in a plain and easy to understand localized message.

Also each logger within Windchill can be set to various levels to increase the information sent to the Method Server log, such levels are debug and all. In 10.0 + systems you can set loggers with commands from the windchill shell:

windchill wt.util.jmx.SetLogLevel -all [logger_name] DEBUG (to set to debug value)

or wt.util.jmx.SetLogLevel -all [logger_name] ERROR (to set back to default value)

These changes will be dynamic and take effect in a mater of minutes.

The PSM software manages the availability and performance of Windchill and the impact on user experience in the form of deep transaction tracing, synthetic monitoring, real user monitoring, and network monitoring.

These log files will be very important to people that are skilled in reading them and will provide an increase in time to resolution of the issue.

I hope this has clarified your question. Let me know if anything is still unclear.

Thank you,

Jarrett

View solution in original post

3 REPLIES 3

Hi Supriya,

How are logs that provide Windchill stack traces important for troubleshooting Windchill instances?

In windchill there are loggers in most classes and these will return exception and errors directly or via handler to the windchill methodserver log.

These are useful as the trace will provide a path of what classes and methods have been called or invoked so you or Tech Support can track down where the exception may have occured. As Windchill evolves we are able to see that more clear messages of where the exception has occurred, in a plain and easy to understand localized message.

Also each logger within Windchill can be set to various levels to increase the information sent to the Method Server log, such levels are debug and all. In 10.0 + systems you can set loggers with commands from the windchill shell:

windchill wt.util.jmx.SetLogLevel -all [logger_name] DEBUG (to set to debug value)

or wt.util.jmx.SetLogLevel -all [logger_name] ERROR (to set back to default value)

These changes will be dynamic and take effect in a mater of minutes.

The PSM software manages the availability and performance of Windchill and the impact on user experience in the form of deep transaction tracing, synthetic monitoring, real user monitoring, and network monitoring.

These log files will be very important to people that are skilled in reading them and will provide an increase in time to resolution of the issue.

I hope this has clarified your question. Let me know if anything is still unclear.

Thank you,

Jarrett

Hi Jarrett,

Thanks for this reply. Yes, this has clarified my question.

Thank you,

Supriya

jessh
5-Regular Member
(To:JarrettOberg)

Small correction:

SetLogLevel changes take effect immediately -- as do those made via the corresponding HTML UI, Windchill/wtcore/jsp/jmx/logLevel.jsp.

Changes made to the settings by editing the log4j*.properties files will take effect in a matter of minutes (3 or less).

All that said, exception stack traces are mostly associated with ERROR (or FATAL) log events -- and these are logged by default without having to change any log levels.

Announcements
PLM On Demand