JDK-4363638 : Program hangs during creation of Java VM, if used with native DB interface.
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version:
    1.0,1.0.1,1.3_01,2.0,1.2.2_005,1.3.0,1.3.0_01 1.0,1.0.1,1.3_01,2.0,1.2.2_005,1.3.0,1.3.0_01
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS:
    generic,linux,solaris_2.6,solaris_7,solaris_8,windows_95,windows_98,windows_nt,windows_2000 generic,linux,solaris_2.6,solaris_7,solaris_8,windows_95,windows_98,windows_nt,windows_2000
  • CPU: generic,x86,sparc
  • Submitted: 2000-08-17
  • Updated: 2001-10-19
  • Resolved: 2001-03-05
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.3.0_03 03Fixed
Related Reports
Duplicate :  
Duplicate :  
Duplicate :  
Duplicate :  
Duplicate :  
Duplicate :  
Duplicate :  
Duplicate :  
Duplicate :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Description
If we try to create Java VM after initializing the DB2 and making calls to
access table, the Hotspot VM results in the following error and program hangs:


Call JNI_CreateJavaVM
#
# HotSpot Virtual Machine Error, Internal Error
#
[error occured during error reporting]

Similar problem is found while using this program with Oracle OCI calls.

*** It results in same error using Java 1.3 (Hotspot).

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: 1.3.0_03 ladybird merlin-beta FIXED IN: 1.3.0_03 ladybird merlin-beta INTEGRATED IN: 1.3.0_03 1.3.0_04 1.3.1 1.3.1_01 ladybird-rc1 merlin-beta VERIFIED IN: 1.3.0_03 1.3.1_01a ladybird
14-06-2004

EVALUATION jon.masamitsu@Eng 2000-08-21 This is the output when the test I got from Kesari was run with a b27 debug VM. See the attachment for the test. The test had to be run on a machine with a db2 installation. $ ./test beginning execution... ** Return code from db connect func = -1 Call JNI_CreateJavaVM # # HotSpot Virtual Machine Error, Internal Error # Please report this error at # http://java.sun.com/cgi-bin/bugreport.cgi # # Fatal: Encountered unexpected pre-existing sigaction handler 0xfe3e14b4 for signal 10. # [error occured during error reporting] Segmentation Fault(coredump) I added this line to the test. 40a41 > vmOptions[ixVMoptions++].optionString = (char *) "-XX:+AllowUserSignalHandlers"; and got this $ ./test beginning execution... ** Return code from db connect func = -1 Call JNI_CreateJavaVM VM option '+AllowUserSignalHandlers' Created the Java VM rcode = 0 $ kesari.mandyam@Eng 2000-08-21 By using this flag the problem appears to be solved. As per the discussion I had with Joe, this flag is internal and can not be suggested for ISV to go ahead with the modification. As this is not a workable solution, we need to keep this bug open till we get a suitable work around for Peoplesoft. I will not be suggesting this workaround to Peoplesoft until the issue of support for this flag is clarified. Here the problem is with the signal handlers and most of the databases like Oracle, DB2 will define their own signal handlers and also the ISV application uses SIGUSR1. This problem occurs if JVM finds that user (in this case the database) has already defined the handlers for SIGSEGV, SIGBUS. --- Please also see RFE 4381843 for more info. mingyao.yang@Eng 2001-07-31
31-07-2001