An infrequent, but recent series of JVM crashes under the configuration of CFMX 6.x on JVM 1.4.x on the Linux platform has been resolved in the short term with the -Xint JVM argument to disable the Sun JVM HotSpot optimizer. 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.
#1 by Hugo Ahlenius on 6/1/04 - 3:47 AM
#2 by Vit on 6/25/04 - 5:01 AM
Looking at Sun`s bug parade, they say that the bug is fixed in jvm 1.4.2_04 (bug 4927116), but i see that you are already using this version :-((
We are using coldfusion 6.1 on redhat 8 and recently we hace upgraded jvm from 1.4.2-b28 to 1.4.2_04-b05.
We will see what happens ...
#3 by Steven Erat on 6/25/04 - 7:47 AM
[P]Yep. That`s what I meant when I said "The result is more stability in exchange a performance hit". You`ll also note that there are many, many bug reports for this hotspot error code, many of them still open.[/P]
#4 by Vit on 7/2/04 - 6:40 AM
#5 by Gavin Cooney on 10/30/04 - 4:26 AM
#6 by Petteri on 12/12/04 - 5:31 PM
Can anyone provide a detailed info on how in the heck can we switch the JVM from the Sun`s engine to IBM`s one for CFMX Pro on Linux? We`re getting almost daily Sig11`s that are getting "pretty" annoying by now..
#7 by Steven Erat on 12/12/04 - 6:09 PM
To use IBM`s JVM just install it and then change the JVM page in the ColdFusion Administrator. Restart CFMX and that`s it. Be aware then that you may be introducing a new suite of issues by just swapping out the JVM from Sun to IBM, so you`d probably want to test that well first.
#8 by Jari on 12/13/04 - 9:24 AM
Using -Xint is not a feasible alternative, since the load on the server is pretty high already.
#9 by Steven Erat on 12/13/04 - 9:46 AM
#10 by Jari on 12/13/04 - 9:57 AM
We`re currently running the Sun JVM with "-XX:+UseParNewGC" which was recommended at
[a href="http://forum.java.sun.com/thread.js..." target="_blank"]http://forum.java.sun.com/thread.js...[/a]
So far the stability and performance increase has been quite nice indeed.
#11 by Steven Erat on 12/13/04 - 10:10 AM
I`ll repost your link which got broken in my comment parser...
http://forum.java.sun.com/thread.jspa?threadID=307...
#12 by Imran Aziz on 12/16/04 - 11:08 AM
#13 by Terry Ford on 12/9/05 - 12:56 PM
We had this problem for over a year and ended up using -Xint. We switched to 1.4_10, removed -Xint, and it`s running crashfree now (well, so far)
#14 by Steven Erat on 1/14/08 - 12:57 PM
[a href="http://www.talkingtree.com/blog/index.cfm/2006/4/2...8/Understanding-HotSpot-in-Plain-English" target="_blank"]http://www.talkingtree.com/blog/index.cfm/2006/4/2......[/a]