[ 
http://issues.apache.org/jira/browse/DERBY-2176?page=comments#action_12459584 ] 
            
John H. Embretsen commented on DERBY-2176:
------------------------------------------

Logs, diagnostics info, graphs and (zipped) heap dump taken at the point where 
the OutOfMemoryError occurred is available at 
http://dbtg.thresher.com/derby/test/debug/DERBY-2176/.

> 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: 10.2.1.6
>         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, 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-10.2.1.5-t2382591.html.
> 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 10.2.1.5 release candidate, but since this 
> version does not exist in Jira, and the delta between 10.2.1.5 and the 
> released 10.2.1.6 is minimal, 10.2.1.6 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

        

Reply via email to