[DERBY-2176] OutOfMemoryError in Network Server after running DOTS-like test for weeks

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.2.1.6
• Fix Version/s: 10.2.2.0
• Component/s: Network Server
• 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
• Urgency: Normal
• Assignee: John Embretsen
• Reporter: John Embretsen
• Created: 14/Dec/06 09:13
• Updated: 09/Feb/07 11:36
• Resolved: 09/Feb/07 11:36

Description

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".

Issue Links

• relates to: DERBY-912 OutOfMemory error on continuous execution of SQL statement