[
https://issues.apache.org/jira/browse/DERBY-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John H. Embretsen updated DERBY-2176:
-------------------------------------
Attachment: OU_jstat-gc-t_10.2.2.0_server.png
Attaching 'OU_jstat-gc-t_10.2.2.0_server.png', which is a graph showing
utilization of the tenured space in the heap of the server VM during a long
running DOTS run against 10.2.2.0.
The test has now been running for about 58 days (the 10.2.1.5 test ran for 57
days, 13 hours before the OOME), and is showing no signs of ever-increasing
memory usage. Memory usage in this test has never been more stable.
> OutOfMemoryError in Network Server after running DOTS-like test for weeks
> -------------------------------------------------------------------------
>
> Key: DERBY-2176
> URL: https://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, 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, OU_jstat-gc-t_10.2.2.0_server.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.
-
You can reply to this email to add a comment to the issue online.
