-
Bug
-
Resolution: Not an Issue
-
P1
-
None
-
1.3.1
-
sparc
-
solaris_8
In the b12/b11 we have the actual binaries of a JVM in the platform directory,
instead of a link to the client/libjvm.so
This causes apps the launch a JVM with its own args to crash on initialization.
i.e. ColdFusion launches its own JVM on startup. With latest 1.3.1 binaries we fail.
ls -al 1.3.1/solsparc/jre/lib/sparc/libjvm*
-rwxr-xr-x 1 collins staff 5647524 Jan 2 12:29 solsparc/jre/lib/sparc/libjvm.so*
ls -al 1.3.1/solx86/jre/lib/i386/libjvm*
-rwxr-xr-x 1 collins staff 3464252 Jan 2 12:41 1.3.1/solx86/jre/lib/i386/libjvm.so*
java version "1.3.1beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1beta-b12)
Java HotSpot(TM) Client VM (build 1.3.1beta-b12, mixed mode)
instead of a link to the client/libjvm.so
This causes apps the launch a JVM with its own args to crash on initialization.
i.e. ColdFusion launches its own JVM on startup. With latest 1.3.1 binaries we fail.
ls -al 1.3.1/solsparc/jre/lib/sparc/libjvm*
-rwxr-xr-x 1 collins staff 5647524 Jan 2 12:29 solsparc/jre/lib/sparc/libjvm.so*
ls -al 1.3.1/solx86/jre/lib/i386/libjvm*
-rwxr-xr-x 1 collins staff 3464252 Jan 2 12:41 1.3.1/solx86/jre/lib/i386/libjvm.so*
java version "1.3.1beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1beta-b12)
Java HotSpot(TM) Client VM (build 1.3.1beta-b12, mixed mode)