-
Notifications
You must be signed in to change notification settings - Fork 17
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
AbstractXnioSocketChannel.doWrite does not handle FileRegion #14
Comments
fl4via
added a commit
to fl4via/netty-xnio-transport
that referenced
this issue
Sep 10, 2019
… non BytBuf message to handle it properly
fl4via
added a commit
to fl4via/netty-xnio-transport
that referenced
this issue
Sep 10, 2019
… non BytBuf message to handle it properly
fl4via
added a commit
to fl4via/netty-xnio-transport
that referenced
this issue
Sep 10, 2019
… non BytBuf message to handle it properly
fl4via
added a commit
to fl4via/netty-xnio-transport
that referenced
this issue
Sep 10, 2019
… non BytBuf message to handle it properly
fl4via
added a commit
to fl4via/netty-xnio-transport
that referenced
this issue
Sep 10, 2019
… non BytBuf message to handle it properly
jmesnil
added a commit
that referenced
this issue
Sep 10, 2019
#14 At AbstractXnioSocketChannel.doWrite, skip loop if there is a…
jmesnil
added a commit
that referenced
this issue
Sep 10, 2019
#14 At AbstractXnioSocketChannel.doWrite, skip loop if there is a…
@normanmaurer maybe you will have a say in this. Right now we fixed the problem at netty-xnio-transport, but shouldn't nioBuffers return null if it finds a FileRegion message? Right now it doesn't. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The reason for this is that unexpectedly ChannelOutboundBuffer.nioBuffers returns a non null array when there are FileRegion messages in the outbound internal entries.
Since doWrite relies on nioBuffers returning null if there are non ByteBuf messages, it throws a ClassCastException.
The text was updated successfully, but these errors were encountered: