You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by "Ilan Kirsh (JIRA)" <ji...@apache.org> on 2006/04/30 06:59:37 UTC
[jira] Created: (JDO-376)
DeletePersistentFailsIfInstanceManagedByAnotherPersistenceManager - No
cleanup for pm
DeletePersistentFailsIfInstanceManagedByAnotherPersistenceManager - No cleanup for pm
-------------------------------------------------------------------------------------
Key: JDO-376
URL: http://issues.apache.org/jira/browse/JDO-376
Project: JDO
Type: Bug
Components: tck20
Reporter: Ilan Kirsh
Priority: Minor
In org.apache.jdo.tck.api.persistencemanager.DeletePersistentFailsIfInstanceManagedByAnotherPersistenceManager, Line 77: It should be pm2 instead of pm, otherwise cleanup of pm is skipped and a following test may fail. For instance running org.apache.jdo.tck.query.api.Close after DeletePersistentFailsIfInstanceManagedByAnotherPersistenceManager fails, because the old PCPoint instances are still there.
--
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
[jira] Commented: (JDO-376)
DeletePersistentFailsIfInstanceManagedByAnotherPersistenceManager - No
cleanup for pm
Posted by "Ilan Kirsh (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-376?page=comments#action_12377165 ]
Ilan Kirsh commented on JDO-376:
--------------------------------
Thank you for the fix and for the clarification regarding cleanupPM.
> DeletePersistentFailsIfInstanceManagedByAnotherPersistenceManager - No cleanup for pm
> -------------------------------------------------------------------------------------
>
> Key: JDO-376
> URL: http://issues.apache.org/jira/browse/JDO-376
> Project: JDO
> Type: Bug
> Components: tck20
> Versions: JDO 2 rc1
> Reporter: Ilan Kirsh
> Assignee: Michael Bouschen
> Priority: Minor
> Fix For: JDO 2 final
>
> In org.apache.jdo.tck.api.persistencemanager.DeletePersistentFailsIfInstanceManagedByAnotherPersistenceManager, Line 77: It should be pm2 instead of pm, otherwise cleanup of pm is skipped and a following test may fail. For instance running org.apache.jdo.tck.query.api.Close after DeletePersistentFailsIfInstanceManagedByAnotherPersistenceManager fails, because the old PCPoint instances are still there.
--
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
[jira] Resolved: (JDO-376)
DeletePersistentFailsIfInstanceManagedByAnotherPersistenceManager - No
cleanup for pm
Posted by "Michael Bouschen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-376?page=all ]
Michael Bouschen resolved JDO-376:
----------------------------------
Resolution: Fixed
Thanks Ilan for catching this. I fixed this in the trunk and into the 2.0 branch (see revision 398346).
The name cleanupPM might be misleadinng, because the method does not clean up the database. It simply checks whether the transaction bound to the pm is still open and if yes calls rollback. Then it closes the pm. The database cleanup is done as part of method localTearDown implemented in the JDO_Test superclass and it will open a new new pm instance.
> DeletePersistentFailsIfInstanceManagedByAnotherPersistenceManager - No cleanup for pm
> -------------------------------------------------------------------------------------
>
> Key: JDO-376
> URL: http://issues.apache.org/jira/browse/JDO-376
> Project: JDO
> Type: Bug
> Components: tck20
> Versions: JDO 2 rc1
> Reporter: Ilan Kirsh
> Assignee: Michael Bouschen
> Priority: Minor
> Fix For: JDO 2 final
>
> In org.apache.jdo.tck.api.persistencemanager.DeletePersistentFailsIfInstanceManagedByAnotherPersistenceManager, Line 77: It should be pm2 instead of pm, otherwise cleanup of pm is skipped and a following test may fail. For instance running org.apache.jdo.tck.query.api.Close after DeletePersistentFailsIfInstanceManagedByAnotherPersistenceManager fails, because the old PCPoint instances are still there.
--
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
[jira] Updated: (JDO-376)
DeletePersistentFailsIfInstanceManagedByAnotherPersistenceManager - No
cleanup for pm
Posted by "Michael Bouschen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-376?page=all ]
Michael Bouschen updated JDO-376:
---------------------------------
Fix Version: JDO 2 final
Version: JDO 2 rc1
Assign To: Michael Bouschen
> DeletePersistentFailsIfInstanceManagedByAnotherPersistenceManager - No cleanup for pm
> -------------------------------------------------------------------------------------
>
> Key: JDO-376
> URL: http://issues.apache.org/jira/browse/JDO-376
> Project: JDO
> Type: Bug
> Components: tck20
> Versions: JDO 2 rc1
> Reporter: Ilan Kirsh
> Assignee: Michael Bouschen
> Priority: Minor
> Fix For: JDO 2 final
>
> In org.apache.jdo.tck.api.persistencemanager.DeletePersistentFailsIfInstanceManagedByAnotherPersistenceManager, Line 77: It should be pm2 instead of pm, otherwise cleanup of pm is skipped and a following test may fail. For instance running org.apache.jdo.tck.query.api.Close after DeletePersistentFailsIfInstanceManagedByAnotherPersistenceManager fails, because the old PCPoint instances are still there.
--
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