[infinispan-issues] [JBoss JIRA] (ISPN-1652) Flags ignored in remote nodes on transaction prepare

[Galder Zamarreño (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653379#comment-12653379 ] 

Galder Zamarreño commented on ISPN-1652:
----------------------------------------

Btw, this only happens with transactional operations. The problem is that in this circumstances, the put gets called from a prepare command which is the one that builds the context, but it builds it with no flags. 

A prepare command might come with N commands, so each command should be able to interact with its own flags, so one possibility would be for each command executed remotely needs a different context built for it. I've worked on a fix like this but it's a bit messy and breaks some tx recovery logic.

A simpler approach would be the command's flags as opposed to the context ones. This is possible since ISPN-922 added flags to commands in order to be able to transport them over the wire. This might be a simpler approach. I'll try it with this specific case and if it works I'll see if it can be extended.
                
> Flags ignored in remote nodes on transaction prepare
> ----------------------------------------------------
>
>                 Key: ISPN-1652
>                 URL: https://issues.jboss.org/browse/ISPN-1652
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Loaders and Stores, Transactions
>    Affects Versions: 5.0.1.FINAL, 5.1.0.CR2
>            Reporter: Galder Zamarreño
>            Assignee: Galder Zamarreño
>             Fix For: 5.1.0.CR3, 5.1.0.FINAL
>
>
> Some flags might not be replicating correctly. As shown in the forum entry, transactional put calls on a node with Flag.SKIP_CACHE_LOAD might result in cache load operations when the tx prepares in a different node.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira