Closed pavelhoral closed 2 years ago
I initially thought that the main issue is only with NIOSimulator
which asynchronously processes messages. And when messages can be in the form of [STREAM ITEM, STREAM ITEM, STREAM END]
then STREAM END
can be processed before previous items get processed.
However it seems that this issue is also present in server implementations thanks to ConnectorFramework#executeMessage which does exactly what NIOSimulator
was doing (introduced in 3d2e0defaff0c41951529dcaddb73d6817fc50d0).
This PR fixes race condition in connector-framework-rpc unit tests.