Starting from FP 5, ITCAM for WAS 6.1 allows to activate L3 method trace for a specific http request.
Suppose you have a production issue and sometimes one or more JSP takes a long time to execute. It’s quite difficult to found the reason of an intermittent behaviour and especially on production.
Creating an application trap and using “Misbehaving transaction” as target type, we’ll help you to find the solution
You’ll select one specific JSP (or a pattern) to trace: something like /<path>/pagename.jsp. In this case you’ll activate the trace only for the requests that are offending the 3,8 seconds threshold
Then you’ll define the actions related to the trap
The most important thing is to activate the “Method Trace”: this will allow you to save every method execution.
How can you choose which methods to trace? Simple, instrumenting the data collector as usual.
I prefere to use CCM to instrument DCs because I don’t have to change manually the DC xml and properties files.
Then just choosing the jsp classes you want to trace
and restarting the DC on production servers, you’re ready to trace only the jsp execution that needs more than 3,8 seconds to terminate.