Saturday, May 03, 2003
Dumping the JVM when CFMX Bombs
Earlier versions of CF made it pretty difficult to work out what was going on under the hood when the server went into a flap-spin. Java on the other hand provides some useful tricks to deciphering what's happening when the server bombs.
Try this:
- Stop the CFMX service
- start the server from the command line using [install]cfusionmx/bin/cfstart.bat
- kill the server (hang/loop/fry cpu) with your problem code
- press ctrl+break (or cntr+c or kill -3 the process id on UNIX)
- review dump stack interesting tidbits
If your CF code is in an infinite loop, then the thread should be on fire on the CPU. Dumping the JVM, you stand a good chance that your nasty thread will appear in the thread stack, and may indicate where your code is stuck.
Posted by modius at 01:11 AM | Permalink
Trackback: http://blog.daemon.com.au/cgi-bin/dmblog/mt-tb.cgi/117
Comments
