[infinispan-issues] [JBoss JIRA] (ISPN-2054) Incorrect notification semantics with event.isPre=false

[Mircea Markus (JIRA)]

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

Mircea Markus edited comment on ISPN-2054 at 11/21/12 6:32 AM:
---------------------------------------------------------------

[~manik] on non tx caches yes, perhaps even after the locking interceptor.
For tx caches we might need do that from the Synchronization/XAResource for certain event types (e.g. TransactionCompleted)
                
      was (Author: mircea.markus):
    [~manik] on non tx caches yes, perhaps even after the locking interceptor.
For tx caches we might need do that from the Synchronization/XAResource
                  
> Incorrect notification semantics with event.isPre=false
> -------------------------------------------------------
>
>                 Key: ISPN-2054
>                 URL: https://issues.jboss.org/browse/ISPN-2054
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Listeners
>    Affects Versions: 5.1.4.FINAL, 5.1.5.CR1
>            Reporter: Julio Faerman
>            Assignee: Manik Surtani
>            Priority: Minor
>              Labels: cache, infinispan, listener, size
>             Fix For: 6.0.0.Final
>
>
> I have found that on CacheEntryCreated the cache size is the same both when pre=true and pre=false, what can be wrong. The discussion can be read in the forum reference.
> Here is the reproducible test case:
> https://github.com/jfaerman/sandbox/blob/master/ispn-tests/src/test/java/jfaerman/TestCacheSize.java
>  

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