500 null, Coldfusion server crash after using CF administrator JVM settings


CF Server 7 Crash with 500 null Error.

Environment:

OS: Centos Linux 4
CF: CF MX 7 patched and hotfixed to accumalative hot fix 2 released in Feb 2006.

Context :

Yesterday we used the CF Administrator to place a Jar file in the JVM class path, after applying the setting through the CF administrator we restarted the CF Server and all hell broke loose, the CF administration page came up with a 500 null error.
On checking the event logs CFserver.log indicated all sorted of errors like

08/03 09:16:32 user failed to load: coldfusion.CfmServlet
08/03 09:16:32 error
[1]java.lang.ClassNotFoundException
at coldfusion.bootstrap.BootstrapClassLoader.loadClass(BootstrapClassLoader.java:229)
08/03 00:33:05 user failed to load: flex.server.j2ee.filemanager.FileManagerServlet
08/03 00:33:05 error Could not pre-load servlet: CFInternalServlet
08/03 00:33:05 user failed to load: flashgateway.controller.GatewayServlet
08/03 00:33:05 error Could not pre-load servlet: CFFormGateway
08/03 00:33:05 user failed to load: coldfusion.xml.rpc.CFCServlet
08/03 00:33:05 error Could not pre-load servlet: CFCServlet
08/03 00:33:05 user failed to load: flex.server.j2ee.SwfServlet
08/03 00:33:05 error Could not pre-load servlet: CFSwfServlet
08/03 00:33:04 user failed to load: coldfusion.CfmServlet
08/03 00:33:04 error Could not pre-load servlet: CfmServlet
08/03 00:33:04 user failed to load: coldfusion.server.j2ee.CFStartUpServlet
08/03 00:33:04 error Could not pre-load servlet: ColdFusionStartUpServlet
08/03 00:33:04 user failed to load: flex.compiler.MxmlServlet
08/03 00:33:04 error Could not pre-load servlet: CFMxmlServlet
08/03 00:33:04 user failed to load: flex.server.j2ee.cache.CacheFilter
08/03 00:33:04 error Error loading class for Filter CFCacheFilter: Filter is disabled.

In panic state we removed the jar file that we installed and removed its reference from the jvm.config file and restarted the server , but no luck, we compared the jvm.config file with the jvm.config file on another server and found it to be fine.

Then on searching from google we found out that 500 null error can happen due to license file corruption so as instructed we changed the license file with a license file from another running install of CF Server, restarted the server but no luck.

The CF server was hagging up on the startup and although it did show up in the running services but on accessing the CF administrator or any of the CF sites we were getting the null error.

Found few posts on CF forums about this

http://www.macromedia.com/cfusion/webforums/forum/messageview.cfm?catid=143&threadid=820782

http://www.macromedia.com/cfusion/webforums/forum/messageview.cfm?catid=143&threadid=1117947&enterthread=y

but no solution other then to reinstall CF

Solution:

Reinstall CF Server, Did the reinstall and went to CF admin to setup JVM parameters like I always do, but on saving the page for the same 500 null error and the server went down again.

Hence did a full reinstall again, applying all hotfixes and updaters todate, and this time knowing the issue with the JVM admin page did not touch it, and the server seems to be running okay now.

Conclusion:

CFMX 7 server on Centos Linux 4 has a bug with the Admin interface of CF for the JVM setting and corrupts the configuration files beyond repair and one has to rebuild the server to get it sorted. So best is to alter the jvm.config manually to get this issue sorted.

Advertisements

2 thoughts on “500 null, Coldfusion server crash after using CF administrator JVM settings

  1. Had this same issue with a Windows machine yesterday. Was hoping for a nice, easy solution rather than a full reinstall.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s