-
Bug
-
Resolution: Won't Fix
-
P4
-
None
-
6, 6u14, 7
-
x86, sparc
-
solaris_7, windows, windows_xp
J2SE Version (please include all output from java -version flag):
java version "1.6.0"
Java(TM) SE Runtime Environment (build 1.6.0-b105)
Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode, sharing)
Does this problem occur on J2SE 1.4.x or 5.0.x ? Yes / No (pick one)
No
Operating System Configuration Information (be specific):
Microsoft Windows 2000 [Version 5.00.2195]
Regression: Launching java using the jvm.dll no longer works without msvcr71.dll in the system path
This seems to be related to bug 6368613, however it does not work in build 1.6.0-b105.
Many applications deploy java and don't install it rather just use the jvm.dll to launch it.
From memory all the following applications do that Tomcat, WebLogic and JBuilder etc.
In our javapath for our launcher we have to specify the exact location to the jvm.dll (eg /bin/client/jvm.dll).
We can not specify additional paths to search for the msvcr71.dll.
On computers that don't have msvcr71.dll in their system path when java is launched they are receiving the error message that 'The dynamic linked library msvcr71.dll could not be found in the specified path' followed by the error message 'Unable to load the dll '/bin/client/jvm.dll''
This worked fine on all versions of java that we have tested over the last 5 years and only became a problem with JRE 1.6.
The msvcr71.dll is located at /bin/msvcr71.dll.
All the workarounds involve copying msvcr71.dll to somewhere already in the path, or changing the system path to point to this copy of msvcr71.dll. Neither is a possibility for us as that would involve messing with the clients computers.
java version "1.6.0"
Java(TM) SE Runtime Environment (build 1.6.0-b105)
Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode, sharing)
Does this problem occur on J2SE 1.4.x or 5.0.x ? Yes / No (pick one)
No
Operating System Configuration Information (be specific):
Microsoft Windows 2000 [Version 5.00.2195]
Regression: Launching java using the jvm.dll no longer works without msvcr71.dll in the system path
This seems to be related to bug 6368613, however it does not work in build 1.6.0-b105.
Many applications deploy java and don't install it rather just use the jvm.dll to launch it.
From memory all the following applications do that Tomcat, WebLogic and JBuilder etc.
In our javapath for our launcher we have to specify the exact location to the jvm.dll (eg /bin/client/jvm.dll).
We can not specify additional paths to search for the msvcr71.dll.
On computers that don't have msvcr71.dll in their system path when java is launched they are receiving the error message that 'The dynamic linked library msvcr71.dll could not be found in the specified path' followed by the error message 'Unable to load the dll '/bin/client/jvm.dll''
This worked fine on all versions of java that we have tested over the last 5 years and only became a problem with JRE 1.6.
The msvcr71.dll is located at /bin/msvcr71.dll.
All the workarounds involve copying msvcr71.dll to somewhere already in the path, or changing the system path to point to this copy of msvcr71.dll. Neither is a possibility for us as that would involve messing with the clients computers.
- duplicates
-
JDK-7019193 JDeveloper 11g fails to launch with JDK 7 b128
- Closed
- relates to
-
JDK-6509739 JNI/Windows: Document requirement to install msvcr71.dll alongside custom launchers
- Closed