db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dag.Wan...@Sun.COM (Dag H. Wanvik)
Subject Re: [jira] Updated: (DERBY-2480) DriverManager.getConnection leaks memory using EmbeddedDriver on non-existent database
Date Sat, 24 Mar 2007 03:40:51 GMT
"Jeff Clary (JIRA)" <jira@apache.org> writes:

> This might be a bit premature, but I am attaching a patch we are
> trying locally to fix this problem and DERBY-1947.  From our
> analysis, it looks like we are missing some calls to
> TransactionResourceImpl.cleanupOnError().

This is what I found as well, I am almost ready with a patch to DERBY-1947,
so we can compare our solutions :)


> I have just now gotten set up to check out, build, and test Derby.
> I am running derbyall against svn revision 521727 now, and will
> re-run it this afternoon with this patch in place.  I'll post my
> results here.
> (By the way, sorry for not granting ASF license for the original test program...that
was just a newbie error.  But I don't see any way to grant it now.)
>> DriverManager.getConnection leaks memory using EmbeddedDriver on non-existent database
>> --------------------------------------------------------------------------------------
>>                 Key: DERBY-2480
>>                 URL: https://issues.apache.org/jira/browse/DERBY-2480
>>             Project: Derby
>>          Issue Type: Bug
>>    Affects Versions:,,,,,,,
>>         Environment: Windows Vista, JDK 1.4.2_13
>> Solaris 10, Sun JDK 1.4.2 & 1.5.0
>>            Reporter: Jeff Clary
>>            Priority: Minor
>>         Attachments: heap-server-Xmx32m.png, Patch_DERBY-1947_and_DERBY-2480.diff,
>> Repeated calls to java.sql.DriverManager.getConnection("jdbc:derby:C:\\DOES_NOT_EXIST")
leak memory and eventually lead to an OutOfMemoryError.
>> This bug is similar to DERBY-1947 in that ContextManager objects are not getting
removed from the HashSet.  The attached test program demonstrates the issue.  When run with
VM options -Xms8m -Xmx8m, it throws an OutOfMemoryError after 19022 calls to DriverManager.getConnection.
> -- 
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.

Dag H. Wanvik
Sun Microsystems, Database Technology Group (DBTG)
Haakon VII gt. 7b, N-7485 Trondheim, Norway
Tel: x43496/+47 73842196, Fax:  +47 73842101

View raw message