[infinispan-issues] [JBoss JIRA] Commented: (ISPN-841) Flag.CACHE_MODE_LOCAL is not working properly for put operation in TreeCache
Galder Zamarreño (JIRA)
jira-events at lists.jboss.org
Thu Dec 23 09:49:18 EST 2010
[ https://issues.jboss.org/browse/ISPN-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572194#comment-12572194 ]
Galder Zamarreño commented on ISPN-841:
---------------------------------------
The problem is that when the treeCache1.put() call is made and the flag is set, there's no TX going on, so an instance of NonTxInvocationContext() is created and flags are set there. However, once the real put() is really done, this is done within a TX, so the previous context is thrown out and a new LocalTxInvocationContext() is created. However, previous context's flags are not ported over. I get the feeling this should be happening though but I'm not sure. Alternatively, the icc.createInvocationContext().setFlags(flags); call could be moved to be within the startAtomic/stopAtomic to solve the issue.
Another workaround that would most likely work is for client code to start a TX externally.
> Flag.CACHE_MODE_LOCAL is not working properly for put operation in TreeCache
> ----------------------------------------------------------------------------
>
> Key: ISPN-841
> URL: https://issues.jboss.org/browse/ISPN-841
> Project: Infinispan
> Issue Type: Bug
> Components: Tree API
> Affects Versions: 4.1.0.Final
> Environment: Windows XP Professional SP3
> Reporter: Konstantin Kuzmin
> Assignee: Galder Zamarreño
> Fix For: 5.0.0.BETA1
>
> Attachments: TestInfinispan.java
>
>
> Actually, the problem might be wider. I suppose the Flag set is not propagated to underlying (Cache) infrastructure in some cases.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list