| Subject: | Re: CF8 keeps crashing |
|---|---|
| From: | "carehart" <charlie@xxxxxxxxxxxx> |
| Date: | Fri, 25 Jul 2008 16:27:15 +0000 (UTC) |
| Newsgroups: | macromedia.coldfusion.server_administration |
Just wanted to throw in here that for at least on of the errors referenced above, I had a client who saw it go away with an upgrade to 8.01 (http://www.adobe.com/support/coldfusion/downloads_updates.html#cf8) and/or its 8.01 Cumulative Hotfix 1 (http://kb.adobe.com/selfservice/viewContent.do?externalId=kb403622). I can't recall which it was, but both are worth trying if you're still stuck. Besides 8.01 upgrading the JVM a bit (from 1.6.0_01 to 1.6.0_04), the CHF included mention of some related to image handling, and the specific error (like above) that I saw fixed was getting the "out of swap" errors which specifically reference "jbyte in C:\BUILD_AREA\jdk6_01\hotspot\src\share\vm\prims\jni.cpp" in the out log message (as does one of the above). Note that the error clearly shows this was running on the 6.01 hvm. The PID output shared above was also the same as what my client was seeing, in that the first line of the stack trace showed reference to the following on its first line: com.sun.medialib.codec.jpeg. That suggested that things had to do with image manipulation. I can't recall now if the code was using CFIMAGE or cfx_imagecr. Anyway, sorry I can't be more definitive. Some of the details are hazy for me now in retrospective. And I know that some of the "out of swap" space errors others are getting are not related to or resolved by this 8.01 upgrade. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Log file error, GArlington |
|---|---|
| Next by Date: | CF 8 JVM memory maxing out, JNokes |
| Previous by Thread: | How to start logging again?, londonjw |
| Next by Thread: | CF 8 JVM memory maxing out, JNokes |
| Indexes: | [Date] [Thread] [Top] [All Lists] |