🚀 go-pugleaf

"Victor Ceban" <vceban@eei1.com> wrote in message
news:41ed63d6$1@newsgroups.borland.com...
> Hi,
>
>  we have a complex J2EE application that runs on Tomcat 5/Linux and uses
> struts heavily. We also have a couple extra libraries used in the system.
>
>  The system started to crash on the server and it crashes JVM with no
useful
> information written to the log file.
>
>  I was wondering if there is a mechanism to track all method calls sent to
> Java for us to identify which method crashes the system. We would like to
> avoid adding logging methods to every method: methodIn, methodOut and time
> (may be). Any JVM triggers we can use ? additional libraries ?
>
Two ways, youmight go about this, but it will drag the response time from
the server.

(1) Use debugging with log4j. This will dump to your log4j files the full
stack trace from the running application.

(2)  Start your catalina session with the debug option. You will need to
start the catalina.sh or .bat file in a local terminal and this too will
produce a stack trace of output. Unless you want to monitor all activity, I
would suggest redirecting this info to a file.


Info on log4j:  http://logging.apache.org/log4j/docs/documentation.html

Info on Catalina debugging:
http://www.fawcette.com/javapro/2003%5F06/online/debugging%5Fkjones%5F06%5F23%5F03/
Look toward the bottom for command line info on using the debug mode.

Again, expect your app to slow down dramatically, as the stack trace goes
through class loaders and methods..