Whatterz


Repairing a Corrupt ColdFusion JVM Config

by Simon. Average Reading Time: less than a minute.

Killing ColdFusion is something I love to do!! This time I managed to kill ColdFusion by amending the Class Paths listed in the Java and JVM settings of my local instance of ColdFusion MX 7. When you amend any Java and JVM settings you need to restart the ColdFusion service and hope.

I jokingly commented to a colleague that this was a brilliant way to kill ColdFusion and I wasn’t far wrong.

Doing a clean install is out of the question, partly because of the time factor but also because there are generally a large number of settings, datasources, logs, etc configured on the server.

Fortunately ColdFusion is clever and stores a backup of the jvm.config file in the C:\CFusionMX7\runtime\bin directory. Simply deleting the broken config file and renaming the jvm.config.bak to jvm.config, followed by a ColdFusion application service restart fixes the issue (until the next time).

This article has been tagged

, , , , , ,

Other articles I recommend

Resetting a Lost ColdFusion Password

I’m a ColdFusion freelance developer and as can often happen, I end up using a spare machine sitting in the corner of a room. Being relegated to the “dunce’s corner” is bad enough, but commonly the ColdFusion password has also been forgotten. This happened to me just the other day. So, how do we go about resetting the password?

Coldfusion MX Tuning

For many ColdFusion developers, server setup, tuning, troubleshooting and configuration is one of the least understood areas of ColdFusion. Achieving the highest possible performance and scalability with a ColdFusion MX application is a complex combination of many different factors. Standard performance tuning guidelines in conjunction with the tips provided below should allow you to achieve maximum application performance and scalability. Performance refers to the response time of requests to CFML pages and Components (CFCs), whilst scalability refers to how the performance results change when the load on the server increases.

Configuring ColdFusion 8 with Apache

After installing ColdFusion 8 and Apache successfully you may still see an “HTTP 500 Internal Server Error” when navigating to a ColdFusion page. All is not lost, you simply need to configure, or check the configuration of Apache. Apache requires very little post installation modification, but it is always good practice to check the httpd.conf file to ensure that the ColdFusion “install” scripts did what they were supposed to do.

  • The Java and JVM page in the ColdFusion Administrator (only applicable to CF Standard, and Enterprise installed in Server Config mode) is woefully broken and has been since 7 was released.

    It is recommended that you modify your jvm.config manually – obviously make a backup first.