-
Bug
-
Resolution: Won't Fix
-
P3
-
None
-
6u10
FULL PRODUCT VERSION :
java version "1.6.0_10"
Java(TM) SE Runtime Environment (build 1.6.0_10-b33)
Java HotSpot(TM) Client VM (build 11.0-b15, mixed mode, sharing)
FULL OS VERSION :
Microsoft Windows XP [Versione 5.1.2600]
EXTRA RELEVANT SYSTEM CONFIGURATION :
Application deployed with JavaWS
A DESCRIPTION OF THE PROBLEM :
The code used to access dll's using COM object (such as jacob, jdic or custom dll) doesn't work on 1.6.0_10 jvm. The same code doesn't experience any problem on previous updates. The application sometime doesn't produce errors and never produce jvm dumps: the dll call seems lost and the app keeps working. In the case of jacob library, interacting with MS Word, an exception is raised while trying to use the ActiveX component.
THE PROBLEM WAS REPRODUCIBLE WITH -Xint FLAG: No
THE PROBLEM WAS REPRODUCIBLE WITH -server FLAG: No
REPRODUCIBILITY :
This bug can be reproduced always.
Release Regression From : 6u6
The above release value was the last known release where this
bug was not reproducible. Since then there has been a regression.
java version "1.6.0_10"
Java(TM) SE Runtime Environment (build 1.6.0_10-b33)
Java HotSpot(TM) Client VM (build 11.0-b15, mixed mode, sharing)
FULL OS VERSION :
Microsoft Windows XP [Versione 5.1.2600]
EXTRA RELEVANT SYSTEM CONFIGURATION :
Application deployed with JavaWS
A DESCRIPTION OF THE PROBLEM :
The code used to access dll's using COM object (such as jacob, jdic or custom dll) doesn't work on 1.6.0_10 jvm. The same code doesn't experience any problem on previous updates. The application sometime doesn't produce errors and never produce jvm dumps: the dll call seems lost and the app keeps working. In the case of jacob library, interacting with MS Word, an exception is raised while trying to use the ActiveX component.
THE PROBLEM WAS REPRODUCIBLE WITH -Xint FLAG: No
THE PROBLEM WAS REPRODUCIBLE WITH -server FLAG: No
REPRODUCIBILITY :
This bug can be reproduced always.
Release Regression From : 6u6
The above release value was the last known release where this
bug was not reproducible. Since then there has been a regression.