HotSpot Crash with ColdFusion MX on Linux with JVM 1.4.x http://www.talkingtree.com/blog/index.cfm?data=20040521#A7DC816B-45A6-2844-7185A97FC416A85D
In brief:
"The -Xint JVM option, described in this Sun VM Options page, can be added to the JVM argument list in the ColdFusion Administrator to force the JVM to run in the interpreted mode, avoiding HotSpot optimization all together. The result is more stability in exchange a performance hit. While a better solution is being sought after, the -Xint option will work in a pinch."
Hope that helps,
-- geoff http://www.daemon.com.au/ http://www.fullasagoog.com/
Mark Stanton wrote:
Hey All
I've got a client running CFMX 6.1 on a Redhat 7 box. We've had some issue with this box in the past, but since we have:
- Tweaked the GC & Memory settings - Applied all CF hot fixes - Turned on all the JVM debugging stuff - Replaced verity with Lucene - Switched off CFHTTP related stuff
...the box has been running pretty well. However a few days ago it went down again. It wasn't under any real load at the time, but some requests started timing out in the minute or so leading up to it, then the JVM died.
I'm planning to go back to MM with the logs, but I thought I'd just see if some of you have an clues that might help me. Below is a dump of JVM when the crash happened.
--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
