Long timeout in receiving can prevent the background handling from other message streams #41
Comments
vivektatipamula
pushed a commit
to vivektatipamula/Rammbock
that referenced
this issue
Dec 4, 2015
…ng template and modifies atest to verify the same. MarketSquare#41
vivektatipamula
pushed a commit
to vivektatipamula/Rammbock
that referenced
this issue
Dec 9, 2015
…tance tests accordingly. Added new atest to test new code. MarketSquare#41
|
Is there a work around for this bug ? I believe I am facing this issue of tests stuck for long time. |
vivektatipamula
added a commit
to vivektatipamula/Rammbock
that referenced
this issue
Jan 15, 2016
…cceptance tests accordingly. MarketSquare#41
|
@niravsh , this fix should help you. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Receiving with timeout goes to a synchronized block. If the timeout is longer than the poll interval for background handlers, this can cause the other message streams to not get the lock during this time and they can not handle their background messages.
The receiving of protocol headers in
MessageStreamshould be done so that other message streams either can operate at the same time, or can get the lock periodically.The text was updated successfully, but these errors were encountered: