Details
-
Type: Bug
-
Status: Closed
-
Priority: Default
-
Resolution: Won't Fix
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Engine
-
Labels:None
Description
Using a synchronized block can result in a thread being starved of access to the responder. This should be changed to use a Lock with fair semantics.
Starvation was observed in a scenario using SocketSynchronousWrites=Y where a slow consumer could not be disconnected because the message writing thread kept re-obtaining the monitor.
Attachments
Issue Links
- is related to
-
QFJ-421 Session responder lock is too restrictive
- Closed