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] Commented: (DERBY-2176) OutOfMemoryError in Network Server after running DOTS-like test for weeks
Date Thu, 14 Dec 2006 16:45:21 GMT
    [ http://issues.apache.org/jira/browse/DERBY-2176?page=comments#action_12458539 ] 
John H. Embretsen commented on DERBY-2176:

Thank you Knut Anders, that is an interesting theory! And if it is correct, it seems like
the problem has already been fixed... I started a new test run using, so we'll see
in a couple of months ;)

I see from derby.log that "Failed Statement is: SELECT BIDERID, BID_PRICE, BID_TIME FROM BID
WHERE ITEMID = ? ORDER BY BID_TIME DESC", and I was not able (from a quick code scan) to find
any other statements utilizing sorting functionality, so this may be the sinner. There is
about 20% chance that the test executes this statement per iteration, so I guess this amounts
to a few million ORDER BYs in the course of these 57+ days.

> 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