Copy link to clipboard
Copied
Hi,
I'm using a VPS with CF 8.01 (Enterprise) and recently upgraded Java from 1.6.0_04 to 1.6.0_11 to fix a memory leak issue.
Changed the jvm.config lines below to reflect the upgrade:
#java.home=C:/ColdFusion8/runtime/jre
java.home=C:/Program Files/Java/jdk1.6.0_11/jre
The system info in CF admin still says the java home is C:\ColdFusion8\runtime\jre and the version is 1.6.0_04
What's worse, is that in CF admin under 'Java and JVM' I now get the following error:
Element JDKPATH is undefined in FORM.
The error occurred in jvm.cfm: line 174
Called from jvm.cfm: line 145
Called from jvm.cfm: line 143
Called from jvm.cfm: line 1
-1 : Unable to display error's location in a CFML template.
So I'm now unsure if the server is using the newly installed 1.6.0_11 java version or the old version.
Does anyone know how I can fix this error in CF admin?
Any help appreciated.
Thanks,
Robin.
You have to run a 64-bit version of ColdFusion to use a 64-bit JVM (and vice-versa).
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
http://training.figleaf.com/
Copy link to clipboard
Copied
try using the double quotes when you have a space in the path defined in your jvm.config
java.home="C:/Program Files/Java/jdk1.6.0_11/jre"
Copy link to clipboard
Copied
I managed to resolve it by uninstalling the jdk for the 64bit platform (jdk-6u11-windows-x64.exe) and installing the 32bit jdk (jdk-6u11-windows-i586-p.exe).
I'm running windows server 2003 64bit so don't know why the 64bit version didn't work. Any way fixed now.
Thank you for looking.
Copy link to clipboard
Copied
You have to run a 64-bit version of ColdFusion to use a 64-bit JVM (and vice-versa).
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
http://training.figleaf.com/
Copy link to clipboard
Copied
The x64 mismatch will cause the problem, but it's not the only way it can happen. We saw it in conjunction with this error:
"Security: The requested template has been denied access to C:\ColdFusion8\runtime\bin\jvm.config."
...during the Java update, permissions got change on the directory structure. After a reinstall and repairing the permissions, both problems went away.