ColdFusion MX 7 and 7.01 ship with JVM version 1.4.2.05 as the default JVM. If you are installing the WAR or EAR option of ColdFusion on an existing version of of JRun, then you may not be using this 'default' JVM since JRun permits you to choose a pre-installed JVM when initally instaling JRun4.

If you are using Sun JVM 1.5 in either Server Configuration, Multiserver Config, or J2EE Config then you may encounter a variety of errors that occur regarding the Verity K2 Search Server. Verity K2 ships with ColdFusion MX 7/7.01 and the encyrption libraries don't work with JVM 1.5, and that JVM version is not supported for use with ColdFusion MX 7/7.01.

view plain print about
1# VM configuration
2#
3# Where to find JVM, if {java.home}/jre exists then that JVM is used
4# if not then it must be the path to the JRE itself
5# Default JVM 1.4.2_05 works
6# java.home=C:/CFusionMX7/runtime/jre
7# JVM 1.5 breaks CF and is unsupported
8java.home=C:/jdk1.5.0_01/jre


view plain print about
111/14 08:14:45 user ColdFusionStartUpServlet: init
211/14 08:14:45 user ColdFusionStartUpServlet: ColdFusion MX: Starting application services
311/14 08:14:45 user ColdFusionStartUpServlet: ColdFusion MX: VM version = 1.5.0_01-b08
411/14 08:14:46 Information [main] - Starting logging...


You may encounter the following errors during the ColdFusion Settings Wizard (part 2 of installation) if you are using the JRun J2EE configuration for CFMX with the 1.5 JVM, or you may encounter it if you changed the JVM from 1.4 to 1.5 after the original installation:

view plain print about
1[1]java.lang.ExceptionInInitializerError
2 at com.verity.administration.VAdmin.<init>(Unknown Source)
3 at com.verity.api.administration.VAdministration.<init>(Unknown Source)
4 at coldfusion.tagext.search.Utils$1.run(Utils.java:321)
5 at java.security.AccessController.doPrivileged(Native Method)
6 at coldfusion.tagext.search.Utils.adminConnect(Utils.java:318)
7 at coldfusion.verity.VerityServiceImpl.getCollectiondir(VerityServiceImpl.java:82)
8 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
9 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
10 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
11 at java.lang.reflect.Method.invoke(Method.java:585)
12 at coldfusion.runtime.StructBean.resolveName(StructBean.java:137)
13...


view plain print about
111/14 08:16:10 error Java bean field access exception.
2[2]java.lang.RuntimeException: Encryption algorithm not found
3 at com.verity.security.k2.K2Encrypt.<clinit>(Unknown Source)
4 at com.verity.administration.VAdmin.<init>(Unknown Source)
5 at com.verity.api.administration.VAdministration.<init>(Unknown Source)
6 at coldfusion.tagext.search.Utils$1.run(Utils.java:321)
7 at java.security.AccessController.doPrivileged(Native Method)
8 at coldfusion.tagext.search.Utils.adminConnect(Utils.java:318)
9 at coldfusion.verity.VerityServiceImpl.getCollectiondir(VerityServiceImpl.java:82)
10 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
11...


If you disabled the Settings Wizard after a new installation of CFMX and then entered into the CF Administrator, or if you changed the JVM version and then went back to the CF Admin, then you will see the following error when you click on the Verity page:

view plain print about
1500 Java bean field access exception.
2Java bean field access exception.


To corrrect this error, use the Sun 1.4.2_05 JVM. You can download the Sun JVM 1.4.2_05 from Sun's Archive page.