deadlock dehydrating instances of Hashtable
-------------------------------------------
Key: CDV-479
URL: https://jira.terracotta.org/jira//browse/CDV-479
Project: Community Development
Issue Type: Bug
Affects Versions: 2.4.4
Reporter: Tim Eck
Assignee: Issue Review Board
>From the forums: http://forums.terracotta.org/forums/posts/list/549.page
The monitor on the TCObject is held for the duration of dehydrateIfNew(). If
the dehydration makes any callbacks on the target object (eg. logical object's
iterator), and said callbacks acquire locks, it's pretty easy to get a lock
order problem as we see here.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.terracotta.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
tc-dev mailing list
[email protected]
http://lists.terracotta.org/mailman/listinfo/tc-dev
