[jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1363) Rollback fails when triggered by a non-successful operation on a non-existent node

[Manik Surtani (JIRA)]

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

Manik Surtani updated JBCACHE-1363:
-----------------------------------

    Assignee: Mircea Markus  (was: Manik Surtani)

Update all unit tests for all commands to test invalid rollbacks as well.

> Rollback fails when triggered by a non-successful operation on a non-existent node
> ----------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1363
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1363
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Transactions
>    Affects Versions: 2.2.0.CR2, 2.2.0.CR3
>            Reporter: Jason T. Greene
>         Assigned To: Mircea Markus
>            Priority: Critical
>             Fix For: 2.2.0.GA
>
>
> It seems that most of the key commands attempt to rollback even if there is nothing to rollback.  
> In the following case the RemoveKeyCommand.rollback() method throws an exception when the node does not exist, this 
> in turn leads to aborting the entire rollback, so all other changes persist. Further there is no exception thrown to the calling app.
> org.jboss.cache.Cache cache = cache_.getCache();
> cache.start();
> cache.put("/blah", "test", "correct");
> tx_mgr.begin();
> cache.put("/blah", "test", "wrong");
> cache.remove("/blah/blah", "non-exist");
> tx_mgr.rollback();
> assertEquals("correct", cache.get("/blah", "test")); // Ends up being wrong

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