Skip to content

Fix handling of large chunks #505

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

Merged
merged 3 commits into from
Jun 5, 2018
Merged

Conversation

lutovich
Copy link
Contributor

@lutovich lutovich commented Jun 3, 2018

No description provided.

lutovich added 3 commits June 3, 2018 13:01
Driver used to only accept chunks of size 32767. This was a limitation
on the total chunk size, which includes a 2 byte length header and
body. However, Bolt protocol specification allows chunks with body
of size 65535 (0xFFFF).

This commit fixes the problem by making `ChunkDecoder` accept chunks
of size 65535 + 2.
Driver tries to extract cause of every `CodecException` received in
`#exceptionCaught(Throwable)` netty callbacks. It did not handle
cases when the cause is null, which resulted in an attempt to
exceptionally complete a `CompletableFuture` with null.

This commit fixes the problem by making handlers extract the exception
cause only if it is defined and propagate the original error otherwise.
@lutovich lutovich requested a review from ali-ince June 3, 2018 11:43
@ali-ince ali-ince merged commit 18becc3 into neo4j:1.6 Jun 5, 2018
@lutovich lutovich deleted the 1.6-chunk-size-fix branch June 5, 2018 08:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants