[ http://issues.apache.org/jira/browse/JDO-394?page=all ]
Michael Bouschen updated JDO-394:
---------------------------------
Attachment: JDO-394.patch
Attached you find a patch (JDO-394.patch) adding pmf.close to the finally block
and does some more code cleanup.
I found a similar issue with the following test classes from the same package:
SetIgnoreCache, SetMultithreaded, SetNonTransactionalRead,
SetNonTransactionalWrite, and SetRetainValues. The patch adds a finally block
closing the pmf.
> org.apache.jdo.tck.api.persistencemanagerfactory.GetPersistenceManager.test()
> and
> org.apache.jdo.tck.api.persistencemanagerfactory.GetPersistenceManagerForUser.test()
> don't close PMF correctly
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JDO-394
> URL: http://issues.apache.org/jira/browse/JDO-394
> Project: JDO
> Issue Type: Bug
> Components: tck20
> Affects Versions: JDO 2 final
> Reporter: Christian Ernst
> Assigned To: Michael Bouschen
> Priority: Minor
> Fix For: JDO 2 maintenance release 1
>
> Attachments: JDO-394.patch
>
>
> org.apache.jdo.tck.api.persistencemanagerfactory.GetPersistenceManager.test()
> and
> org.apache.jdo.tck.api.persistencemanagerfactory.GetPersistenceManagerForUser.test()
>
> don't close PMF correctly and this can cause other Testcases to fail
> Following should be added to the finally block of each test() Method
> if (pmf != null) pmf.close();
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
