You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2012/06/28 01:04:43 UTC
[jira] [Commented] (DERBY-5835) OOM failure in 10.3
DerbyNetClient/derbynetmats/multi/stress.multi
[ https://issues.apache.org/jira/browse/DERBY-5835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402648#comment-13402648 ]
Myrna van Lunteren commented on DERBY-5835:
-------------------------------------------
Here's the stack from the diff.txt from the same run I attached the files for:
*** Start: stress jdk1.6.0 DerbyNetClient derbynetmats:multi 2012-06-23 02:39:36 ***
4 del
< ...stopping testers
5 del
< ...waiting for testers to complete
6 del
< TEST CASE SUMMARY: normal termination
7 del
< ...running last checks via final.sql
7 add
> JVMDUMP039I Processing dump event "systhrow", detail "java/lang/OutOfMemoryError" at 2012/06/23 02:48:31 - please wait.
> JVMDUMP032I JVM requested Heap dump using 'E:\cloudtst\jartest\JarResults.2012-06-22\ibm16_derbyall\heapdump.20120623.024831.10020.0001.phd' in response to an event
> JVMDUMP010I Heap dump written to E:\cloudtst\jartest\JarResults.2012-06-22\ibm16_derbyall\heapdump.20120623.024831.10020.0001.phd
> JVMDUMP032I JVM requested Java dump using 'E:\cloudtst\jartest\JarResults.2012-06-22\ibm16_derbyall\javacore.20120623.024831.10020.0002.txt' in response to an event
> UTE430: can't allocate buffer
> UTE437: Unable to load formatStrings for j9mm
> JVMDUMP010I Java dump written to E:\cloudtst\jartest\JarResults.2012-06-22\ibm16_derbyall\javacore.20120623.024831.10020.0002.txt
> JVMDUMP032I JVM requested Snap dump using 'E:\cloudtst\jartest\JarResults.2012-06-22\ibm16_derbyall\Snap.20120623.024831.10020.0003.trc' in response to an event
> UTE001: Error starting trace thread for "Snap Dump Thread": -1
> JVMDUMP010I Snap dump written to E:\cloudtst\jartest\JarResults.2012-06-22\ibm16_derbyall\Snap.20120623.024831.10020.0003.trc
> JVMDUMP013I Processed dump event "systhrow", detail "java/lang/OutOfMemoryError".
> JVMDUMP039I Processing dump event "systhrow", detail "java/lang/OutOfMemoryError" at 2012/06/23 02:48:37 - please wait.
> JVMDUMP032I JVM requested Heap dump using 'E:\cloudtst\jartest\JarResults.2012-06-22\ibm16_derbyall\heapdump.20120623.024837.10020.0004.phd' in response to an event
> JVMDUMP010I Heap dump written to E:\cloudtst\jartest\JarResults.2012-06-22\ibm16_derbyall\heapdump.20120623.024837.10020.0004.phd
> JVMDUMP032I JVM requested Java dump using 'E:\cloudtst\jartest\JarResults.2012-06-22\ibm16_derbyall\javacore.20120623.024837.10020.0005.txt' in response to an event
> OOM failure in 10.3 DerbyNetClient/derbynetmats/multi/stress.multi
> ------------------------------------------------------------------
>
> Key: DERBY-5835
> URL: https://issues.apache.org/jira/browse/DERBY-5835
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.3.3.1
> Environment: Windows XP, ibm 1.5 sr13 and ibm 1.6 sr10
> Reporter: Myrna van Lunteren
> Attachments: heapdump.20120623.024831.10020.0001.phd, heapdump.20120623.024837.10020.0004.phd, javacore.20120623.024831.10020.0002.txt, javacore.20120623.024837.10020.0005.txt
>
>
> Since June 8, the nightly tests for 10.3 are hitting an OOM with both ibm 1.5 and ibm 1.6.
> No changes went in prior to the June 8 test run.
> Here is an example stack trace:
> (with ibm 1.6 against revision 1348302)
> *** Start: stress jdk1.6.0 DerbyNetClient derbynetmats:multi 2012-06-09 02:57:22 ***
> 4 del
> < ...stopping testers
> 5 del
> < ...waiting for testers to complete
> 6 del
> < TEST CASE SUMMARY: normal termination
> 7 del
> < ...running last checks via final.sql
> 7 add
> > JVMDUMP039I Processing dump event "systhrow", detail "java/lang/OutOfMemoryError" at 2012/06/09 03:03:26 - please wait.
> > JVMDUMP032I JVM requested Heap dump using 'E:\cloudtst\jartest\JarResults.2012-06-08\ibm16_derbyall\heapdump.20120609.030326.5592.0001.phd' in response to an event
> > JVMDUMP010I Heap dump written to E:\cloudtst\jartest\JarResults.2012-06-08\ibm16_derbyall\heapdump.20120609.030326.5592.0001.phd
> > JVMDUMP032I JVM requested Java dump using 'E:\cloudtst\jartest\JarResults.2012-06-08\ibm16_derbyall\javacore.20120609.030326.5592.0002.txt' in response to an event
> > UTE430: can't allocate buffer
> > UTE437: Unable to load formatStrings for j9mm
> > JVMDUMP010I Java dump written to E:\cloudtst\jartest\JarResults.2012-06-08\ibm16_derbyall\javacore.20120609.030326.5592.0002.txt
> > JVMDUMP032I JVM requested Snap dump using 'E:\cloudtst\jartest\JarResults.2012-06-08\ibm16_derbyall\Snap.20120609.030326.5592.0003.trc' in response to an event
> > UTE001: Error starting trace thread for "Snap Dump Thread": -1
> > JVMDUMP010I Snap dump written to E:\cloudtst\jartest\JarResults.2012-06-08\ibm16_derbyall\Snap.20120609.030326.5592.0003.trc
> > JVMDUMP013I Processed dump event "systhrow", detail "java/lang/OutOfMemoryError".
> > JVMDUMP039I Processing dump event "systhrow", detail "java/lang/OutOfMemoryError" at 2012/06/09 03:03:30 - please wait.
> > JVMDUMP032I JVM requested Heap dump using 'E:\cloudtst\jartest\JarResults.2012-06-08\ibm16_derbyall\heapdump.20120609.030330.5592.0004.phd' in response to an event
> > JVMDUMP010I Heap dump written to E:\cloudtst\jartest\JarResults.2012-06-08\ibm16_derbyall\heapdump.20120609.030330.5592.0004.phd
> > JVMDUMP032I JVM requested Java dump using 'E:\cloudtst\jartest\JarResults.2012-06-08\ibm16_derbyall\javacore.20120609.030330.5592.0005.txt' in response to an event
> Test Failed.
> See also these links:
> http://people.apache.org/~myrnavl/derby_test_results/v10_3/windows/testSummary-1348302.html
> http://people.apache.org/~myrnavl/derby_test_results/v10_3/windows/testSummary-1350843.html
> http://people.apache.org/~myrnavl/derby_test_results/v10_3/windows/testSummary-1353062.html
> There are older bugs referring to similar OOMs in stress.multi, not sure if it's the same thing. (e.g. DERBY-4744)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira