Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
None
Description
Even though the timers are run in a separate thread from the sendMessage operation, the timeouts will block on the intensive synchronization found on the ConversationStates.
This phenomenon was discovered in the status service, which did't detect a frozen messagebus.
Attachments
Issue Links
- related to
-
BITMAG-545 Re-enable conversationTimeout regression test, and fix the bug that causes it not to work!
- Closed