-
Bug
-
Resolution: Fixed
-
P2
-
5.0u6, 5.0u11, 5.0u8
Steps to reproduce:
Find a Windows XP machine (AMD64).
Run Bigapps ATG, see test procedure document:
http://jqa.ireland/procedures/test_procedures/all_test_procedures/BigApps.html
Set the -XX:+AggressiveOpts flag:
setenv JAVA_ARGS -XX:+AggressiveOpts
Start atg test. ksh runatg.ksh -server
EXCEPTION_ACCESS_VIOLATION will appear after 2 minutes and the server dies. See attached screenshot)
This is reproducible with 1.5.0_07b03. The -XX:+AggressiveOpts flag works with Tomcat, vtest and vmark tests.
Find a Windows XP machine (AMD64).
Run Bigapps ATG, see test procedure document:
http://jqa.ireland/procedures/test_procedures/all_test_procedures/BigApps.html
Set the -XX:+AggressiveOpts flag:
setenv JAVA_ARGS -XX:+AggressiveOpts
Start atg test. ksh runatg.ksh -server
EXCEPTION_ACCESS_VIOLATION will appear after 2 minutes and the server dies. See attached screenshot)
This is reproducible with 1.5.0_07b03. The -XX:+AggressiveOpts flag works with Tomcat, vtest and vmark tests.
- duplicates
-
JDK-6511174 -XX:+AggressiveOpts option makes JVM to crash
- Closed
-
JDK-6512742 AggressiveOpts parameter cause ATG BigApps test unexpected error in 5.0u11 JVM
- Closed
- relates to
-
JDK-6528475 Appserver bat testing for JDK 1.5.0_12 b01: VM crash with -server option, no crash for 1.5.0_11
- Closed