The responses queue is created too late, resulting in potentially unanswered requests
thomashilzendegen opened this issue · 2 comments
thomashilzendegen commented
Actual behavior
The server creates the responses queue when the first connector connects. If any other server wants to dispatch a response for a request from a client who has started a request on that particular server without any connector, the queue isn't there, and the response never reaches the client.
Expected behavior
The server needs to create the queue on startup.
Steps to reproduce
Start at least two servers and connect one connector to any server, but start a request on a different server.
Version
3.0.0-rc.3
master, develop, commit-hash, ...
thomashilzendegen commented
I suggest moving the queue declaration/consumption out of the constructor and explicitly calling a Start() method on that implementation (IServerTransport).