You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 25, 2023. It is now read-only.
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>
The text was updated successfully, but these errors were encountered:
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.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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>
The text was updated successfully, but these errors were encountered: