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, followed by a ColdFusion application service restart fixes the issue (until the next time).