db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John H. Embretsen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2176) OutOfMemoryError in Network Server after running DOTS-like test for weeks
Date Thu, 14 Dec 2006 14:00:21 GMT
     [ http://issues.apache.org/jira/browse/DERBY-2176?page=all ]

John H. Embretsen updated DERBY-2176:

    Attachment: derby.log

Attached the following files, to help debugging efforts:

   * derby.log
   * OU_jstat-gc-t.png
       - graph of tenured space memory usage (error occurred at about 1381 hrs (x-axis unit))
   * jmap-histo_server_17Nov1020CET.txt
       - textual histogram of objects in the heap approx. 6 days before the error

I plan to make more logs and diagnostics info (including a heap dump) available soon.

Timing of events:
   * Network Server started: 2006-09-26 14:20 CEST
   * Test client started: 2006-09-26 14:23 CEST (+3 min)
   * First OutOfMemoryError occured: 2006-11-23 01:41 CET (+1381 hrs (57 days, 13 hrs), 21
   * Test + server stopped: ca. 2006-12-12 15:05 CET (+1849 hrs, 28 min)

> OutOfMemoryError in Network Server after running DOTS-like test for weeks
> -------------------------------------------------------------------------
>                 Key: DERBY-2176
>                 URL: http://issues.apache.org/jira/browse/DERBY-2176
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server
>    Affects Versions:
>         Environment: Solaris 10 x86_64 MU2, remote client-server, 2 x 2.4 GHz AMD Opteron,
2048 MB RAM, Sun HotSpot 1.5.0_07 server JVM
>            Reporter: John H. Embretsen
>         Attachments: derby.log, jmap-histo_server_17Nov1020CET.txt, OU_jstat-gc-t.png
> Running a modified version of the Database Opensource Test Suite (DOTS) (v1.1.1) test
case ATCJ2 (auction "simulation"), available from http://sourceforge.net/project/showfiles.php?group_id=3382,
resulted in an "OutOfMemoryError: Java heap space" after 57 days, 13 hours and 21 minutes.
> The test run has previously been described on derby-dev: http://www.nabble.com/Long-running-testing-of-
> The modifications to the original test case were mainly to avoid the type of errors described
in http://www.nabble.com/OutOfMemoryErrors-when-testing-Derby-with-DOTS-t1010027.html. Indeed,
this is a different, yet similar error.
> Heap size (both client and server JVMs) was:
>   -Xms128m
>   -Xmx128m
> The test was run against the release candidate, but since this version does
not exist in Jira, and the delta between and the released is minimal,
is marked as the "affects version".

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message