Such issues are difficult to resolve because the JVM is simply aborting. FusionReactor has to run inside the same JVM so it too will be aborted when the JVM dies.
It's is likely that a certain type of request causes the issue. FusionReactor should be able to help as it will track the requests that have been started. You would be able to look at the logs to see which requests were running when a crash occurs. If the same request is running you have a start.
Secondly FusionReactor can generate stack traces even on production servers without debug setting on the JVM (which make the JVM slow and stop much of the garbage collection engine from working normally) so you will be able to see what the request is doing, and if you set up Crash Protection, FusionReactor may be able to send you a warning shot before the server goes down. It will depend on what causes the issue. Try giving FusionReactor a go in this case.
One thing to consider is the JVM version. Adobe now support much later versions of the 1.4.2 JVM and so you might consider upgrading this. Also Adobe have many many fixes to CF recently, take a look here:
ColdFusion hot fixes (MX 7 and higher)
Hot fix available for Apache 2.2 support on Linux and Unix
ColdFusion MX/JRun 4.0: Hot fix available for JRun4 Updater 6, IIS 6.0 redirect response truncation
ColdFusion MX 7.0.1 Cumulative Hot Fix 2
ColdFusion MX 7.0.1: Hot fix available for Microsoft IIS truncation for headers larger than 8k
|Last Updated:||28/Aug/08 10:53 AM|