[JAVA-3126] Test with latest version of Netty Created: 20/Dec/18 Updated: 03/Oct/20 Resolved: 01/Sep/20 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Async |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Case: | (copied to CRM) | ||||
| Description |
|
There was a regression in Netty 4.1.32-Final that a customer encountered, but we hadn't seen it because we don't update our Netty dependency very often. We can catch issues early by testing against latest Netty release. The easiest way to do that is with a version range. It has the disadvantage of making builds non-repeatable, but the alternative of updating every month (which is Netty's patch release cadence) seems worse. |
| Comments |
| Comment by Jeffrey Yemin [ 29/Dec/18 ] |
|
Here's the root cause: https://github.com/netty/netty/issues/8613. The regression was introduced in 4.1.32-Final, and a fix is targeted for 4.1.33-Final. The Java driver's NettyStream class hits the regression in the readAsync method, in which it allocates a CompositeByteBuf that sometimes has only a single component. |
| Comment by Yuri Schimke [ 29/Dec/18 ] |
|
Is there a link to the regression in Netty project, or the original report? I think I got hit by this, took 6+ hours of debugging and finding this report was the only reason I solved it. |