[infinispan-issues] [JBoss JIRA] (ISPN-1782) Could not lock to invalidate L1 WARN messages

Mircea Markus (JIRA) jira-events at lists.jboss.org
Mon Jan 23 19:41:18 EST 2012


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

Mircea Markus commented on ISPN-1782:
-------------------------------------

This would reproduce thE WARN:
{code}
public class L1InvalidationWithDistTest extends MultipleCacheManagersTest {

   @Override
   protected void createCacheManagers() throws Throwable {
      ConfigurationBuilder dccc = getDefaultClusteredCacheConfig(CacheMode.DIST_SYNC, false);
      dccc.clustering().hash().numOwners(1).l1().enable();
      createCluster(dccc, 3);
      waitForClusterToForm();
   }
   
   public void testL1InvalidatedCorrectly() {
      Object k1 = getKeyForCache(1);
      cache(1).put(k1, "v");
      assertEquals(cache(0).get(k1), "v");
      assertEquals(cache(2).get(k1), "v");

      DataContainer dc0 = TestingUtil.extractComponent(cache(0), DataContainer.class);
      DataContainer dc1 = TestingUtil.extractComponent(cache(1), DataContainer.class);
      assert dc0.containsKey(k1);
      assert dc1.containsKey(k1);

      log.trace("here it begins");

      cache(0).put(k1, "v2");
      assertEquals("v2", dc0.get(k1).getValue());
      assertEquals("v2", dc0.get(k1).getValue());
   }
}

{code}
                
> 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