[
https://issues.apache.org/jira/browse/DERBY-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Clary updated DERBY-2480:
------------------------------
Attachment: Patch_DERBY-1947_and_DERBY-2480.diff
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().
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: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1,
> 10.2.1.6, 10.2.2.0, 10.3.0.0
> 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, testOpenOfMissingDatabase.java
>
>
> 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.
