-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
fixes websockets on netty #6534
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
Conversation
| push(remoteOut, close) | ||
| completeStage() | ||
| // And complete both remote out and remote in | ||
| complete(remoteOut) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if that won't help we can basically just add a netty: Boolean and remove these two completly than netty will close the upstream by himself. Which is basically a little bit smoother since netty knows when he flushes the Message.
|
@schmitch lgtm. Can you backport to 2.5.x? |
|
yes |
|
Backport: 00e016f (commited directly) |
|
Not a helpful pull request title. |
Fixes #6504
Edit: Fix is just 3 Lines https://github.com/playframework/playframework/pull/6534/files#diff-745ef9331ba1901efedd1607f6675eeaR183
Basically we can also omit complet/cancel for netty (not for akka) if necessary.