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 Fri, 22 Dec 2006 10:53:21 GMT
     [ http://issues.apache.org/jira/browse/DERBY-2176?page=all ]

John H. Embretsen updated DERBY-2176:

    Attachment: OU_10.2.1.6_vs_10.2.2.0.png

Attached a graph (OU_10.2.1.6_vs_10.2.2.0.png) showing a rough comparison of and when it comes to memory usage (tenured space) when an ORDER BY query is executed
multiple times. 

I created a smaller (and faster) test case in which a similar ORDER BY query is executed repetitively
(using a PreparedStatement). The attached graph shows results from this test running 1.2 million
ORDER BY queries. The test case is also attached (Derby2176repro.java). memory usage looks very similar to what was seen during the DOTS-based long running
test for, while memory usage is completely stable and much lower. 

Based on these results I now feel quite confident that this issue is the same as the one reported
and fixed in DERBY-912, but I will wait a while longer (and do more testing) before I resolve/close
this issue.

> 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, Derby2176repro.java, jmap-histo_server_17Nov1020CET.txt,
OU_10.2.1.6_vs_10.2.2.0.png, OU_jstat-gc-t.png, 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