[infinispan-issues] [JBoss JIRA] Updated: (ISPN-165) putForExternalRead() resulting in cluster wide invalidation

Galder Zamarreno (JIRA) jira-events at lists.jboss.org
Thu Aug 20 04:40:26 EDT 2009


     [ https://jira.jboss.org/jira/browse/ISPN-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Galder Zamarreno updated ISPN-165:
----------------------------------

    Summary: putForExternalRead() resulting in cluster wide invalidation  (was: putForExternalRead() resulting in cluster wider invalidations)


> putForExternalRead() resulting in cluster wide invalidation
> -----------------------------------------------------------
>
>                 Key: ISPN-165
>                 URL: https://jira.jboss.org/jira/browse/ISPN-165
>             Project: Infinispan
>          Issue Type: Bug
>          Components: RPC
>    Affects Versions: 4.0.0.ALPHA6
>            Reporter: Galder Zamarreno
>            Assignee: Galder Zamarreno
>             Fix For: 4.0.0.BETA1
>
>
> More findings from porting further tests over to the Infinispan cache provider. The following log snippet shows a call to putForExternalRead() resulting on an invalidation and that, according to the Cache API, should not happen:
> 2009-08-20 10:26:23,437 6311  TRACE [org.infinispan.interceptors.InvocationContextInterceptor] (main:) Invoked with command PutKeyValueCommand{key=KEY4, value=VALUE1, putIfAbsent=true, lifespanMillis=-1, maxIdleTimeMillis=100000} and InvocationContext [NonTxInvocationContext{flags=[ZERO_LOCK_ACQUISITION_TIMEOUT, FORCE_ASYNCHRONOUS, FAIL_SILENTLY]}]
> 2009-08-20 10:26:23,437 6311  TRACE [org.infinispan.factories.EntryFactoryImpl] (main:) Creating new entry.
> 2009-08-20 10:26:23,437 6311  TRACE [org.infinispan.util.concurrent.locks.LockManagerImpl] (main:) Attempting to lock KEY4 with acquisition timeout of 0 millis
> 2009-08-20 10:26:23,438 6312  TRACE [org.infinispan.interceptors.CallInterceptor] (main:) Executing command: PutKeyValueCommand{key=KEY4, value=VALUE1, putIfAbsent=true, lifespanMillis=-1, maxIdleTimeMillis=100000}.
> 2009-08-20 10:26:23,438 6312  TRACE [org.infinispan.interceptors.LockingInterceptor] (main:) Number of entries in context: 1
> 2009-08-20 10:26:23,438 6312  TRACE [org.infinispan.container.entries.ReadCommittedEntry] (main:) Updating entry (key=KEY4 removed=false valid=true changed=true created=true value=VALUE1]
> 2009-08-20 10:26:23,439 6313  TRACE [org.infinispan.interceptors.LockingInterceptor] (main:) Releasing lock on [KEY4] for owner Thread[main,5,main]
> 2009-08-20 10:26:23,439 6313  TRACE [org.infinispan.util.concurrent.locks.LockManagerImpl] (main:) Attempting to unlock KEY4
> 2009-08-20 10:26:23,439 6313  DEBUG [org.infinispan.interceptors.InvalidationInterceptor] (main:) Cache [localhost.localdomain-11442] replicating InvalidateCommand{keys=[KEY4]}
> 2009-08-20 10:26:23,439 6313  TRACE [org.infinispan.remoting.rpc.RpcManagerImpl] (main:) localhost.localdomain-11442 broadcasting call InvalidateCommand{keys=[KEY4]} to recipient list null
> 2009-08-20 10:26:23,440 6314  TRACE [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (main:) dests=null, command=SingleRpcCommand{cacheName='test/com.foo.test', command=InvalidateCommand{keys=[KEY4]}}, mode=ASYNCHRONOUS, timeout=20000

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the infinispan-issues mailing list