[
https://issues.jboss.org/browse/ISPN-2148?page=com.atlassian.jira.plugin....
]
Manik Surtani updated ISPN-2148:
--------------------------------
Assignee: Vladimir Blagojevic (was: Manik Surtani)
Fix Version/s: 5.2.0.ALPHA2
5.2.0.FINAL
Affects Version/s: 5.1.5.FINAL
Component/s: Core API
Locking and Concurrency
Transactions
(was: Cache Server)
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()
--
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