Open kuzznya opened 2 years ago
This is still an issue, proactive closure support is inhibited.
Also related to this the mock server does not respect an incoming close message - it likely should echo that back to be well behaved. - that appeared to be the case behaviorally in a test, but upon checking the source it does indeed immediately echo.
Existing WebSocket session is not closed after processing all expected messages with such configuration:
If my understanding is correct, session should close after "input" is received (if not, please correct me and I'll close the issue). This is not happening due to the check in io.fabric8.mockserver.internal.WebSocketSession::closeActiveSocketsIfApplicable:
i.e. requestEvents.isEmpty() - it is never empty when there were some expected messages because even after receiving expected message it still contains entry
"input": <Empty queue>