Skip to content

Bump reactor-netty from 1.2.18 to 1.3.6 and Netty to 4.2.15.Final #1874

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.

Sign up for GitHub

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
Yavor16 merged 5 commits into from
Jul 17, 2026
Merged

Bump reactor-netty from 1.2.18 to 1.3.6 and Netty to 4.2.15.Final #1874

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
bb9e409
Bump reactor-netty from 1.2.18 to 1.3.6
Yavor16 Jul 10, 2026
d5cd758
Bump Netty to 4.2.15.Final to align with reactor-netty 1.3.6
Yavor16 Jul 14, 2026
1f4f4d5
fix: add comment documenting reactor-netty OOM resolution for LMCROSS…
Yavor16 Jul 15, 2026
e6175c8
fix: remove unresolvable issue placeholder from reactor-netty OOM com…
Yavor16 Jul 15, 2026
9919c99
Remove not required dependencies
Yavor16 Jul 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 2 additions & 12 deletions pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,10 +37,8 @@
<liquibase.version>4.33.0</liquibase.version>
<liquibase-slf4j.version>5.1.0</liquibase-slf4j.version>
<cloudfoundry-client.version>5.16.0.RELEASE</cloudfoundry-client.version>
<!--reactor netty 1.3.x uses direct memory leading to OOM errors-->
<reactor-netty.version>1.2.18</reactor-netty.version>
<!-- Override Netty version to fix CVE-2026-42583 (Lz4FrameDecoder resource exhaustion) -->
<netty.version>4.1.135.Final</netty.version>
<reactor-netty.version>1.3.6</reactor-netty.version>
Comment thread
Yavor16 marked this conversation as resolved.

@IvanBorislavovDimitrov IvanBorislavovDimitrov Jul 16, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

How the new version of reactory-netty does not lead to direct memory usage and what has changed over time so no direct memory spikes occur?

<netty.version>4.2.15.Final</netty.version>
<swagger.version>1.6.16</swagger.version>
<jclouds.version>2.7.0</jclouds.version>
<guava.version>33.5.0-jre</guava.version>
Expand Down Expand Up @@ -293,14 +291,6 @@
</dependencies>
<dependencyManagement>
<dependencies>
<!-- Override Netty version to fix CVE-2026-42583 -->
<dependency>
<groupId>io.netty</groupId>
<artifactId>netty-bom</artifactId>
<version>${netty.version}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
<dependency>
<groupId>io.netty</groupId>
<artifactId>netty-bom</artifactId>
Expand Down
Loading