Details
-
Bug
-
Resolution: Fixed
-
Medium
-
5.7
-
None
Description
The heartbeat actions sent from the editor attempt to obtain a lock to do it's work. However it waits forever on that lock - so multiple heartbeats start to build up, eating up HTTP threads.
The action should only wait on the lock as long as the heartbeat interval.
Attachments
Issue Links
- is related to
-
CONFSERVER-36694 Deadlock on Hazelcast
- Closed