-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: EAP 5.0.0.CR3
-
Fix Version/s: EAP 5.0.1.CR2
-
Component/s: Testsuite
-
Labels:None
-
Environment:
RHEL5 x86_64, RHEL4 x86_64
Sun JDK 1.6
-
Affects:Release Notes
-
Workaround:Workaround Exists
-
Workaround Description:
org.jboss.test.xml.DDValidatorUnitTestCase.testJBossCmpJdbc is failing with:
Error Message
Forked Java VM exited abnormally. Please note the time in the report does not reflect the time until the VM exit.
Stacktrace
junit.framework.AssertionFailedError: Forked Java VM exited abnormally. Please note the time in the report does not reflect the time until the VM exit.
This is in the testsuite output:
[junit] Running org.jboss.test.xml.DDValidatorUnitTestCase
[junit] #
[junit] # A fatal error has been detected by the Java Runtime Environment:
[junit] #
[junit] # SIGSEGV (0xb) at pc=0x0000002a95ba7101, pid=3563, tid=1086544224
[junit] #
[junit] # JRE version: 6.0_15-b03
[junit] # Java VM: Java HotSpot(TM) 64-Bit Server VM (14.1-b02 mixed mode linux-amd64 )
[junit] # Problematic frame:
[junit] # V [libjvm.so+0x524101]
[junit] #
[junit] # An error report file with more information is saved as:
[junit] # /qa/hudson_ws/workspace/eap5-as-rhel4-x86_64-sun6/src/jboss-eap-5.0-src/jboss-as/testsuite/output/hs_err_pid3563.log
[junit] #
[junit] # If you would like to submit a bug report, please visit:
[junit] # http://java.sun.com/webapps/bugreport/crash.jsp
[junit] #
[junit] Running org.jboss.test.xml.DDValidatorUnitTestCase
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
[junit] Test org.jboss.test.xml.DDValidatorUnitTestCase FAILED (crashed)
It works fine with IBM JDK 1.6.
