tracker issue : CF-3134418

select a category, or use search below
(searches all categories and all time range)

CF Admin Changes to JVM Config

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Rob Bilson / Rob Bilson (Rob Bilson)

Created: 03/09/2012

Components: Administrator, Administrator Console

Versions: 10.0

Failure Type:

Found In Build/Fixed In Build: Public Beta / 281905

Priority/Frequency: Major / Most users will encounter

Locale/System: English / Win All

Vote Count: 0

Problem Description:

The ColdFusion Administrator seems to be handling changes to JVM config inconsistently, often resulting in bad formatting in the jvm.config file, which causes ColdFusion not to start.  I've noticed different behavior in the default cfusion instance vs. additional instances I've created. 

Steps to Reproduce:

In the default cfusion instance, if you log into the ColdFusion Administrator and make a change to the JVM config (try changing the min/max jvm heap size) and save it.  Now go open the jvm.config file for the default instance.  Here's what I found in mine:


Notice the double back slashes?  That's the problem here.  The slashes should be single, and they should be forward slashes, not back slashes.

For additional ColdFusion instances created through the CF Admin, the problem gets worse.  I created a second instance and attempted to change the JVM config (again, min/max heap size).  When I saved my changes and opened the jvm.config file in a text editor, here's what I found:


# If no java.home is specified a VM is located by looking in these places in this
# order:
#  1) ../runtime/jre
#  2) registry (windows only)
#  3) JAVA_HOME env var plus jre (ie $JAVA_HOME/jre)
#  4) java.exe in path


Two issues here.  The first is that the actual format of the file is different than for the default instance.  Why is that?  Shouldn't the formatting for all instances be the same?  Also, you're correctly using forward slashes for the java.home value here. 

The second and more serious of the issues is the value of application.home.  It seems that ColdFusion has stripped the forward slashes out of the file path.  This will cause ColdFusion not to restart as it's obviously now a bad file path.

Actual Result:

Expected Result:

Any Workarounds:

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3134418

External Customer Info:
External Company:  
External Customer Name: Rob Brooks-Bilson
External Customer Email:  
External Test Config: My Hardware and Environment details:



The path can contain backward slash(double in this case) or forward slash, and they both server the purpose. This will not be an issue and the functionality is not broken. However, the missing slash in application.home needs to be fixed.
Comment by Akhila K.
20154 | March 13, 2012 12:35:43 AM GMT
The missing slash issue in application.home is fixed.
Comment by Akhila K.
20155 | March 16, 2012 05:16:59 AM GMT