[jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1167) Heuristic outcome (STATUS_UNKNOWN) of transaction not handled properly

Manik Surtani (JIRA) jira-events at lists.jboss.org
Wed Oct 10 11:54:08 EDT 2007


     [ http://jira.jboss.com/jira/browse/JBCACHE-1167?page=all ]

Manik Surtani updated JBCACHE-1167:
-----------------------------------

    Fix Version/s: 1.4.1.SP5

> Heuristic outcome (STATUS_UNKNOWN) of transaction not handled properly
> ----------------------------------------------------------------------
>
>                 Key: JBCACHE-1167
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1167
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.1.SP4
>            Reporter: Galder Zamarreno
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 1.4.1.SP5, 2.1.0.BETA1
>
>
> Where an XA transaction has a heuristic outcome, the status reported to 
> the afterCompletion synchronization is STATUS_UNKNOWN (5), since 
> JTA does not handle heuristics. In this case, the cache Synchronization 
> fails to rollback the cache tx. This leaves the app server in a bad (i.e. locked) 
> state even though the XA transaction has been resolved. 
> At first glance it looks like the afterCompletion synchronization should treat a 
> STATUS_UNKNOWN as a cause for rollback as well as logging the error as 
> they currently do. Unfortunately the fix may be more complex than that, since 
> the db may have committed rather than rolled back, meaning the cache would 
> be out of sync with the db if you rolled it back. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list