[infinispan-issues] [JBoss JIRA] (ISPN-1782) Could not lock to invalidate L1 WARN messages
Galder Zamarreño (JIRA)
jira-events at lists.jboss.org
Mon Jan 23 13:33:18 EST 2012
[ https://issues.jboss.org/browse/ISPN-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661248#comment-12661248 ]
Galder Zamarreño commented on ISPN-1782:
----------------------------------------
Hmmm, the invalidation is the result of a put, so the put's origin must be known for this to work. This could possibly achieved with the invalidate command carrying the put's address?
> Could not lock to invalidate L1 WARN messages
> ---------------------------------------------
>
> Key: ISPN-1782
> URL: https://issues.jboss.org/browse/ISPN-1782
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 5.1.0.CR4
> Reporter: Galder Zamarreño
> Assignee: Mircea Markus
> Priority: Blocker
> Fix For: 5.1.0.FINAL
>
> Attachments: ispn1782.tgz
>
>
> While executing the labs and playing with retrieving keys from other nodes, I see these in the logs:
> {code}
> [Server:server-three] 20:02:46,847 WARN [org.infinispan.interceptors.locking.NonTransactionalLockingInterceptor] (OOB-3,ISPN,z-63185) ISPN000135: Could not lock key sanne-Devoxx presents... in order to invalidate from L1 at node z-63185, skipping....
> [Server:server-three] 20:02:46,857 WARN [org.infinispan.interceptors.locking.NonTransactionalLockingInterceptor] (OOB-2,ISPN,z-63185) ISPN000135: Could not lock key manik-Best of Abba in order to invalidate from L1 at node z-63185, skipping....
> [Server:server-three] 20:02:46,867 WARN [org.infinispan.interceptors.locking.NonTransactionalLockingInterceptor] (OOB-2,ISPN,z-63185) ISPN000135: Could not lock key dan-Cher's greatest hits in order to invalidate from L1 at node z-63185, skipping....
> ...
> [Server:server-four] 20:03:05,500 WARN [org.infinispan.interceptors.locking.NonTransactionalLockingInterceptor] (OOB-4,ISPN,z-25294) ISPN000135: Could not lock key galder-M83 live in order to invalidate from L1 at node z-25294, skipping....{code}
> I'll attach TRACE logs asap if I can replicate it.
--
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
More information about the infinispan-issues
mailing list