[infinispan-issues] [JBoss JIRA] (ISPN-3558) PutForExternalRead won't work after a clear(), when both in same tx

Mircea Markus (JIRA) jira-events at lists.jboss.org
Fri Nov 8 09:41:02 EST 2013


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

Mircea Markus commented on ISPN-3558:
-------------------------------------

[~galderz] it's not as easy as that: if there's no transaction associated with the current thread, then the TxInterceptor will throw an exception. Also we'd need to use a nontxinvocation context, which is  a bit more complicated, as the InvocationContextContainer is configured per cache ( and we'd need to change that). I'm not saying that the solution doesn't make sense but that it is not that trivial to implement in the scope of 6.0.
What about this solve the problem with L2 integration? use a distributed executor broadcasted that would invoke DtaContainer.clear and PersistenceManager.clear on all nodes?
                
> PutForExternalRead won't work after a clear(), when both in same tx
> -------------------------------------------------------------------
>
>                 Key: ISPN-3558
>                 URL: https://issues.jboss.org/browse/ISPN-3558
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Transactions
>    Affects Versions: 5.3.0.Final, 6.0.0.Beta1
>            Reporter: Galder Zamarreño
>            Assignee: William Burns
>            Priority: Blocker
>              Labels: dm
>             Fix For: 6.0.0.Final
>
>
> {code}
>    public void testPutForExternalReadAfterClear() throws Exception {
>       cache.put(1, "v1");
>       tm().begin();
>       try {
>          cache.getAdvancedCache().clear();
>          cache.putForExternalRead(1, "v1");
>          assertEquals("v1", cache.get(1));
>       } finally {
>          tm().commit();
>       }
>    }
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the infinispan-issues mailing list