The common technique to obtain the application stack trace
is to send a "kill -3" signal to the Application Server Java process (the ctrl+break key sequence handles this under Microsoft Windows).
While often not exploitable in and of itself, the leak, such as an error message, default error page, stack trace
or directory listing info leak, is something an attacker can use to formulate and refine their attack strategy.
View a full stack trace
of detailed events to identify and respond to app issues fast.
Collect CPU and wall-clock statistics at the class constructor and method level for the classes selected, with detailed information on the stack trace
signatures and threads involved with each constructor or method;