[infinispan-issues] [JBoss JIRA] (ISPN-10145) Lock timeout errors do not show which cache they affect

Galder Zamarreño (Jira) issues at jboss.org
Wed Apr 24 13:46:00 EDT 2019


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

Galder Zamarreño updated ISPN-10145:
------------------------------------
              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/infinispan/infinispan/pull/6863, https://github.com/infinispan/infinispan/pull/6862


> Lock timeout errors do not show which cache they affect
> -------------------------------------------------------
>
>                 Key: ISPN-10145
>                 URL: https://issues.jboss.org/browse/ISPN-10145
>             Project: Infinispan
>          Issue Type: Bug
>    Affects Versions: 9.4.12.Final, 10.0.0.Beta3
>            Reporter: Galder Zamarreño
>            Assignee: Galder Zamarreño
>            Priority: Major
>             Fix For: 10.0.0.Final, 9.4.13.Final
>
>
> e.g.
> {code}
> 14:56:40,478 ERROR [org.infinispan.interceptors.impl.InvocationContextInterceptor] (async-thread--p6-t24) ISPN000136: Error executing command PutKeyValueCommand, writing keys [WrappedByteArray{bytes=[B0x6C6561646572626F..[11], hashCode=-1576989476}]: org.infinispan.util.concurrent.TimeoutException: ISPN000299: Unable to acquire lock after 10 seconds for key WrappedByteArray{bytes=[B0x6C6561646572626F..[11], hashCode=-1576989476} and requestor CommandInvocation:datagrid-service-0:4720. Lock is held by CommandInvocation:datagrid-service-0:4712
> 	at org.infinispan.util.concurrent.locks.impl.DefaultLockManager$KeyAwareExtendedLockPromise.get(DefaultLockManager.java:288) [infinispan-core-9.4.11-SNAPSHOT.jar:9.4.11-SNAPSHOT]
> 	at org.infinispan.util.concurrent.locks.impl.DefaultLockManager$KeyAwareExtendedLockPromise.get(DefaultLockManager.java:218) [infinispan-core-9.4.11-SNAPSHOT.jar:9.4.11-SNAPSHOT]
> 	at org.infinispan.util.concurrent.locks.impl.InfinispanLock$LockPlaceHolder.checkState(InfinispanLock.java:436) [infinispan-core-9.4.11-SNAPSHOT.jar:9.4.11-SNAPSHOT]
> 	at org.infinispan.util.concurrent.locks.impl.InfinispanLock$LockPlaceHolder.lambda$toInvocationStage$3(InfinispanLock.java:412) [infinispan-core-9.4.11-SNAPSHOT.jar:9.4.11-SNAPSHOT]
> 	at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:602) [rt.jar:1.8.0_201]
> 	at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577) [rt.jar:1.8.0_201]
> 	at java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:442) [rt.jar:1.8.0_201]
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_201]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_201]
> 	at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_201]
> {code}
> Cache name is only added to NDC when trace is enabled, so the alternative would be for the error message to show it.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)



More information about the infinispan-issues mailing list