Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue #5193 - fix lost websocket messages when only one OnWebSocketMessage annotation used #5208

Merged
merged 6 commits into from
Sep 2, 2020

Conversation

lachlan-roberts
Copy link
Contributor

See issue #5193

If no @OnWebSocketMessage annotation is registered, the activeMessage is not reset for a single fin frame message of that message type. This results in discarding the next message after this occurs.

joakime and others added 4 commits August 26, 2020 06:56
Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
…tion

Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
@lachlan-roberts lachlan-roberts changed the title Issue #5193 - fix lost websocket messages when only one onMessage annotation used Issue #5193 - fix lost websocket messages when only one OnWebSocketMessage annotation used Aug 27, 2020
@lachlan-roberts lachlan-roberts added this to In progress in Jetty 9.4.32 via automation Aug 27, 2020
Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
@joakime
Copy link
Contributor

joakime commented Aug 28, 2020

Do you want to merge PR #5202 into this one?

…t-event-logging' into jetty-9.4.x-5193-NullMessage

Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
@joakime joakime moved this from In progress to Review in progress in Jetty 9.4.32 Aug 31, 2020
Copy link
Contributor

@joakime joakime left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Jetty 9.4.32 automation moved this from Review in progress to Reviewer approved Sep 1, 2020
@lachlan-roberts lachlan-roberts merged commit f813b38 into jetty-9.4.x Sep 2, 2020
Jetty 9.4.32 automation moved this from Reviewer approved to Done Sep 2, 2020
@lachlan-roberts lachlan-roberts deleted the jetty-9.4.x-5193-NullMessage branch September 2, 2020 05:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Jetty 9.4.32
  
Done
Development

Successfully merging this pull request may close these issues.

WebSocket unimplemented BINARY message handling can result in TEXT message delivery to fail
2 participants