We are currently running ColdFusion 9 on a RedHat Enterprise Linux server and have found that, in some circumstances, JVM crashes This is why the CF server becomes completely useless and requires full server restart.
The only error that comes back by the CF app is that JVM does not provide much additional information in a Java.lang.inindexautofoundband exception and stacktrace before completing its death spiral. Does anyone else have to face such a problem on this?
On the basis of some very old thread on House of Fusion (about 2003), this was a problem which was sometimes encountered due to the caching problem. But it is believed that it has been decided in later CF versions.
However, I apologize in advance for the ambiguity of this question, but before that we are passing through accidents, they are not particularly useful.
We are not able to replicate this problem on Windows, Mac, or Ubuntu. Whenever the java.lang.IndexOutOfBoundsException error is thrown into any environment, the JVM bus is just fine.
EDIT: A serious mind was devastated this morning, we are not running Enterprise Redhat Enterprise TOKamet.
There are known memory problems when it is overwritten on Cold Fusion Stracts. Are you dumping or copying any large structures? For example, the following of my servers have been tanks:
To debug this stuff, or not, I came to know that the server tried and tanked using true log statements, which caused the server's "last breath" The code line was separated to separate the code.
Comments
Post a Comment