[DERBY-23] just booting jdbc driver and shutting down seem to leak memory

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.0.2.0
• Fix Version/s: 10.2.1.6
• Component/s: Services
• Urgency: Low
• Assignee: Knut Anders Hatlen
• Reporter: Tulika Agrawal
• Created: 29/Sep/04 19:20
• Updated: 19/Jul/11 12:17
• Resolved: 22/Aug/06 13:02

Description

Reporting for Daniel John Debrunner.

Doing simple boot and shutdown of the driver in a loop
seem to grow the heap forever:
new org.apache.derby.jdbc.EmbeddedDriver(); //boot the driver
DriverManager.getConnection("jdbc:derby:;shutdown=true");
//shutdown the cloudscape instance completely

after booting and shutting down 1516 times, memory used is
~~41931056 bytes.
Sample GC Output:
1931.93: [Full GC 43484K->43243K(65088K), 0.1779751 secs]
1933.13: [Full GC 43511K->43270K(65088K), 0.1914383 secs]
1934.47: [Full GC 43538K->43297K(65088K), 0.1808878 secs]
1935.68: [Full GC 43564K->43324K(65088K), 0.4461623 secs]
1937.43: [Full GC 43591K->43350K(65088K), 0.1842980 secs]
1938.63: [Full GC 43617K->43377K(65088K), 0.1873431 secs]
1939.85: [Full GC 43644K->43404K(65088K), 0.1948505 secs]
1941.07: [Full GC 43671K->43430K(65088K), 0.1790895 secs]

Issue Links

• is related to: DERBY-5343 Starting 7/13/2011 weme 6.2 upgrade tests started failing with 213 failures 127 errors with java.lang.IllegalAccessException