11:55 a.m.
[
https://issues.jboss.org/browse/ISPN-2737?page=com.atlassian.jira.plugin....
]
Michal Linhard commented on ISPN-2737:
--------------------------------------
So this is an error that happened on node01 in MemcachedServerWorker during replication of
PutKeyValueCommand(key=memcachedCache#key763328) to node03. The PutKeyValueCommand on
remote node03 fails, the exception is returned to node01 with stacktrace from node03.
Shouldn't we do more informative logging in the MemcachedServerWorker i.e. the cache
where the request originates ? Like having local stack trace + remote stacktrace in
causing exception... ?
Thread naming anomaly when reporting lock timeout
-------------------------------------------------
Key: ISPN-2737
URL: https://issues.jboss.org/browse/ISPN-2737
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency
Affects Versions: 5.2.0.CR1
Reporter: Michal Linhard
Assignee: Galder Zamarreño
Priority: Minor
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPOR...
{code}
11:47:30,859 ERROR [org.infinispan.interceptors.InvocationContextInterceptor]
(MemcachedServerWorker-277) ISPN000136: Execution error:
org.infinispan.util.concurrent.TimeoutException: Unable to acquire lock after [3 seconds]
on key [memcachedCache#key763328] for requestor [Thread[OOB-127,null,5,Thread Pools]]!
Lock held by [Thread[OOB-150,null,5,Thread Pools]]
at org.infinispan.util.concurrent.locks.LockManagerImpl.lock(LockManagerImpl.java:217)
[infinispan-core-5.2.0.CR1-redhat-1.jar:5.2.0.CR1-redhat-1]
at
org.infinispan.util.concurrent.locks.LockManagerImpl.acquireLockNoCheck(LockManagerImpl.java:200)
[infinispan-core-5.2.0.CR1-redhat-1.jar:5.2.0.CR1-redhat-1]
at
org.infinispan.interceptors.locking.AbstractLockingInterceptor.lockKey(AbstractLockingInterceptor.java:114)
[infinispan-core-5.2.0.CR1-redhat-1.jar:5.2.0.CR1-redhat-1]
....
at org.jgroups.protocols.MERGE2.up(MERGE2.java:205)
[jgroups-3.2.5.Final-redhat-1.jar:3.2.5.Final-redhat-1]
at org.jgroups.protocols.Discovery.up(Discovery.java:359)
[jgroups-3.2.5.Final-redhat-1.jar:3.2.5.Final-redhat-1]
at org.jgroups.protocols.TP$ProtocolAdapter.up(TP.java:2640)
[jgroups-3.2.5.Final-redhat-1.jar:3.2.5.Final-redhat-1]
at org.jgroups.protocols.TP.passMessageUp(TP.java:1287)
[jgroups-3.2.5.Final-redhat-1.jar:3.2.5.Final-redhat-1]
at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1850)
[jgroups-3.2.5.Final-redhat-1.jar:3.2.5.Final-redhat-1]
at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1823)
[jgroups-3.2.5.Final-redhat-1.jar:3.2.5.Final-redhat-1]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[rt.jar:1.6.0_38]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[rt.jar:1.6.0_38]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_38]
{code}
note the thread name "MemcachedServerWorker" in an operation coming from the
JGroups stack...
--
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
4360
days inactive
4360
days old
infinispan-issues@lists.jboss.org
0 comments
1 participants
participants (1)
-
Michal Linhard (JIRA)