8:43 a.m.
Galder Zamarreño created ISPN-1782:
--------------------------------------
Summary: 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: Manik Surtani
Priority: Blocker
Fix For: 5.1.0.FINAL
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
8:58 a.m.
[
https://issues.jboss.org/browse/ISPN-1782?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-1782:
-----------------------------------
Attachment: ispn1782.tgz
Attached TRACE logs from 4 nodes. Grep for the WARN messages like the ones posted in the
description.
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: Manik Surtani
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
11:10 a.m.
[
https://issues.jboss.org/browse/ISPN-1782?page=com.atlassian.jira.plugin....
]
Mircea Markus commented on ISPN-1782:
-------------------------------------
Here's the issue:
- N1 does a put for "k" where ch("k")={N2}
- upon receiving the put command, N2 sends the invalidate to all the nodes that require
it, including N1
- but on N1 the invalidation fails, because the lock is already held on "k"
Whilst is required for N1 to also do the invalidation, not sure how we can get rid of the
warning message as the lock on "k" is acquired still
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: Manik Surtani
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
11:14 a.m.
[
https://issues.jboss.org/browse/ISPN-1782?page=com.atlassian.jira.plugin....
]
Mircea Markus reassigned ISPN-1782:
-----------------------------------
Assignee: Mircea Markus (was: Manik Surtani)
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
12:33 p.m.
[
https://issues.jboss.org/browse/ISPN-1782?page=com.atlassian.jira.plugin....
]
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
6:41 p.m.
[
https://issues.jboss.org/browse/ISPN-1782?page=com.atlassian.jira.plugin....
]
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
6:47 p.m.
[
https://issues.jboss.org/browse/ISPN-1782?page=com.atlassian.jira.plugin....
]
Mircea Markus commented on ISPN-1782:
-------------------------------------
@galderz yes, the implementation followed your suggestion.
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
6:47 p.m.
[
https://issues.jboss.org/browse/ISPN-1782?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-1782:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/884
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
6:41 a.m.
[
https://issues.jboss.org/browse/ISPN-1782?page=com.atlassian.jira.plugin....
]
Dan Berindei updated ISPN-1782:
-------------------------------
Fix Version/s: 5.2.0.FINAL
(was: 5.1.0.FINAL)
Git Pull Request: https://github.com/infinispan/infinispan/pull/884 (was:
https://github.com/infinispan/infinispan/pull/884)
Mircea, I integrated your pull request but I still see a lot of WARN messages like
Galder's in the test suite log when running IllegalMonitorTest:
2012-01-24 14:27:11,396 WARN (OOB-1,ISPN,IllegalMonitorTest-NodeC-12895)
[org.infinispan.interceptors.locking.NonTransactionalLockingInterceptor] ISPN000135: Could
not lock key distribution.IllegalMonitorTest in order to invalidate from L1 at node
IllegalMonitorTest-NodeC-12895, skipping....
I'm assuming there must be another case where it's happening, so I'm keeping
the issue open.
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.2.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
6:52 a.m.
[
https://issues.jboss.org/browse/ISPN-1782?page=com.atlassian.jira.plugin....
]
Mircea Markus commented on ISPN-1782:
-------------------------------------
@dberindei IllegalMonitorTest does concurrent writes so invalidation failures are legit
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.2.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
6:57 a.m.
[
https://issues.jboss.org/browse/ISPN-1782?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-1782:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
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.2.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
4:33 a.m.
[
https://issues.jboss.org/browse/ISPN-1782?page=com.atlassian.jira.plugin....
]
Manik Surtani updated ISPN-1782:
--------------------------------
Fix Version/s: 5.1.0.FINAL
(was: 5.2.0.FINAL)
Git Pull Request: https://github.com/infinispan/infinispan/pull/884 (was:
https://github.com/infinispan/infinispan/pull/884)
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
4714
days inactive
4718
days old
infinispan-issues@lists.jboss.org
11 comments
4 participants
participants (4)
-
Dan Berindei (JIRA) -
Galder Zamarreño (JIRA)
-
Manik Surtani (JIRA)
-
Mircea Markus (JIRA)