You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2006/06/09 11:34:29 UTC

[jira] Created: (JCR-455) InternalXAResource.rollback() can be called twice and without prepare

InternalXAResource.rollback() can be called twice and without prepare
---------------------------------------------------------------------

         Key: JCR-455
         URL: http://issues.apache.org/jira/browse/JCR-455
     Project: Jackrabbit
        Type: Bug

 Environment: r412989
    Reporter: Tobias Bocanegra
 Assigned to: Tobias Bocanegra 


during the prepare phase in the transaction context, each resource is 'prepared'. if one of them fails to prepare, the rest is rolledback, and later all of them are rolledback again. this can cause that:
- a resource that is never prepared is rolled back (which is ok, since is may need to cleanup stuff)
- a resource's rollback() may be called twice (which i don't know, if it's ok)

however, some of the resources are buggy and can't handle neither case correctly.

-- 
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: (JCR-455) InternalXAResource.rollback() can be called twice and without prepare

Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/JCR-455?page=all ]

Jukka Zitting updated JCR-455:
------------------------------

    Component: transactions
      Version: 0.9
               1.0
               1.0.1

> InternalXAResource.rollback() can be called twice and without prepare
> ---------------------------------------------------------------------
>
>          Key: JCR-455
>          URL: http://issues.apache.org/jira/browse/JCR-455
>      Project: Jackrabbit
>         Type: Bug

>   Components: transactions
>     Versions: 1.0, 1.0.1, 0.9
>  Environment: r412989
>     Reporter: Tobias Bocanegra
>     Assignee: Tobias Bocanegra
>      Fix For: 1.1

>
> during the prepare phase in the transaction context, each resource is 'prepared'. if one of them fails to prepare, the rest is rolledback, and later all of them are rolledback again. this can cause that:
> - a resource that is never prepared is rolled back (which is ok, since is may need to cleanup stuff)
> - a resource's rollback() may be called twice (which i don't know, if it's ok)
> however, some of the resources are buggy and can't handle neither case correctly.

-- 
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] Closed: (JCR-455) InternalXAResource.rollback() can be called twice and without prepare

Posted by "Tobias Bocanegra (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/JCR-455?page=all ]
     
Tobias Bocanegra closed JCR-455:
--------------------------------

    Fix Version: 1.1
     Resolution: Fixed

fixed.

Committed revision 412995.

> InternalXAResource.rollback() can be called twice and without prepare
> ---------------------------------------------------------------------
>
>          Key: JCR-455
>          URL: http://issues.apache.org/jira/browse/JCR-455
>      Project: Jackrabbit
>         Type: Bug

>  Environment: r412989
>     Reporter: Tobias Bocanegra
>     Assignee: Tobias Bocanegra
>      Fix For: 1.1

>
> during the prepare phase in the transaction context, each resource is 'prepared'. if one of them fails to prepare, the rest is rolledback, and later all of them are rolledback again. this can cause that:
> - a resource that is never prepared is rolled back (which is ok, since is may need to cleanup stuff)
> - a resource's rollback() may be called twice (which i don't know, if it's ok)
> however, some of the resources are buggy and can't handle neither case correctly.

-- 
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