db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (DERBY-4744) Out of Memory resulting in heapdump and javacore in test derbynetclientmats (and derbynetmats) stress.multi with 10.1 with IBM 1.5 JVM after upgrade to SR11 FP1 (from SR10)
Date Wed, 22 Jun 2011 00:20:47 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Myrna van Lunteren closed DERBY-4744.
-------------------------------------

    Resolution: Invalid

This is unlikely to be a derby issue, but I do not intend to pursue the OOM for the jvm 1.5.
To prevent the known failure, as there's no way short of hardcoding something in the tests
or an exception in the harness, I've disabled stress.multi from running with ibm 1.5. in 10.1
altogether - embedded and network server - with revision 1138263.

> Out of Memory resulting in heapdump and javacore in test derbynetclientmats (and derbynetmats)
stress.multi with 10.1 with IBM 1.5 JVM after upgrade to SR11 FP1 (from SR10)
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4744
>                 URL: https://issues.apache.org/jira/browse/DERBY-4744
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.1.3.3
>         Environment: windows xp, IBM 1.5 SR11 FP1
>            Reporter: Myrna van Lunteren
>            Priority: Minor
>              Labels: derby_triage10_8
>         Attachments: jvm15sr11dumpfiles.jar
>
>
> After upgrade of the IBM 1.5 jvm from SR10 to SR11 FP1, the 10.1 stress.multi test is
failing (out of 6 runs over the last 4 weeks, it failed 5 times) .
> This is from the .diff file; there are 8 different heapdumps, this is the first (path
has been simplified):
> < ...running last checks via final.sql
> 7 add
> > JVMDUMP006I Processing dump event "systhrow", detail "java/lang/OutOfMemoryError"
- please wait.
> > JVMDUMP032I JVM requested Snap dump using 'C:\ibm15_derbyall\Snap.20100714.092914.6192.0001.trc'
in response to an event
> > UTE001: Error starting trace thread for "Snap Dump Thread": -1
> > JVMDUMP010I Snap dump written to C:\ibm15_derbyall\Snap.20100714.092914.6192.0001.trc
> > JVMDUMP032I JVM requested Heap dump using 'C:\ibm15_derbyall\heapdump.20100714.092914.6192.0002.phd'
in response to an event
> > JVMDUMP010I Heap dump written to C:\ibm15_derbyall\heapdump.20100714.092914.6192.0002.phd
> > JVMDUMP032I JVM requested Java dump using 'C:\ibm15_derbyall\javacore.20100714.092914.6192.0003.txt'
in response to an event
> > JVMDUMP010I Java dump written to C:\ibm15_derbyall\javacore.20100714.092914.6192.0003.txt
> I'll add a set of dump files.
> Logging here for reference, could still be a so-far hidden derby problem or test problem,
although I suspect the jvm.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message