Improve lock timeout exception details -------------------------------------- Key: ISPN-2148 URL: https://issues.jboss.org/browse/ISPN-2148 Project: Infinispan Issue Type: Enhancement Components: Cache Server Reporter: Vladimir Blagojevic Assignee: Manik Surtani Priority: Minor I found it much easier to debug locking issues if we log the call originator in TimeoutException raised in LockingManagerImpl.java. Node that sent the call is readily available in InvocationContext#getOrigin()

Improve lock timeout exception details -------------------------------------- Key: ISPN-2148 URL: https://issues.jboss.org/browse/ISPN-2148 Project: Infinispan Issue Type: Enhancement Components: Core API, Locking and Concurrency, Transactions Affects Versions: 5.1.5.FINAL Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Priority: Minor Fix For: 5.2.0.ALPHA2, 5.2.0.FINAL I found it much easier to debug locking issues if we log the call originator in TimeoutException raised in LockingManagerImpl.java. Node that sent the call is readily available in InvocationContext#getOrigin()

Improve lock timeout exception details -------------------------------------- Key: ISPN-2148 URL: https://issues.jboss.org/browse/ISPN-2148 Project: Infinispan Issue Type: Enhancement Components: Core API, Locking and Concurrency, Transactions Affects Versions: 5.1.5.FINAL Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Priority: Minor Fix For: 5.2.0.ALPHA3, 5.2.0.FINAL I found it much easier to debug locking issues if we log the call originator in TimeoutException raised in LockingManagerImpl.java. Node that sent the call is readily available in InvocationContext#getOrigin()

Improve lock timeout exception details -------------------------------------- Key: ISPN-2148 URL: https://issues.jboss.org/browse/ISPN-2148 Project: Infinispan Issue Type: Enhancement Components: Core API, Locking and Concurrency, Transactions Affects Versions: 5.1.5.FINAL Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Priority: Minor Fix For: 5.2.0.Beta1, 5.2.0.Final I found it much easier to debug locking issues if we log the call originator in TimeoutException raised in LockingManagerImpl.java. Node that sent the call is readily available in InvocationContext#getOrigin()

Improve lock timeout exception details -------------------------------------- Key: ISPN-2148 URL: https://issues.jboss.org/browse/ISPN-2148 Project: Infinispan Issue Type: Enhancement Components: Core API, Locking and Concurrency, Transactions Affects Versions: 5.1.5.FINAL Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Priority: Minor Fix For: 5.2.0.CR1, 5.2.0.Final I found it much easier to debug locking issues if we log the call originator in TimeoutException raised in LockingManagerImpl.java. Node that sent the call is readily available in InvocationContext#getOrigin()

Improve lock timeout exception details -------------------------------------- Key: ISPN-2148 URL: https://issues.jboss.org/browse/ISPN-2148 Project: Infinispan Issue Type: Enhancement Components: Core API, Locking and Concurrency, Transactions Affects Versions: 5.1.5.FINAL Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Priority: Minor Fix For: 6.0.0.Final I found it much easier to debug locking issues if we log the call originator in TimeoutException raised in LockingManagerImpl.java. Node that sent the call is readily available in InvocationContext#getOrigin()