You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It may also be the underlying netty-reactor instrumentation that is the real issue as the heap dump shows a lot of cached entries for reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.
Here is the instrumentation that was loaded in the environment that was experiencing the OOM:
Related to https://new-relic.atlassian.net/browse/NR-299687
Customer reported that they were getting an OOM with their service using SpringBoot and R2DBC Mysql.
It was confirmed that disabling the
r2dbc-mysql
instrumentation resolved the memory issues:This may be related to the the use of the
@NewField
annotation and a known issue with how they interact with the caffeine cache when there are many instances of the annotation.newrelic-java-agent/instrumentation/r2dbc-mssql/src/main/java/io/r2dbc/mssql/client/ReactorNettyClient_Instrumentation.java
Lines 8 to 16 in d35ffd6
newrelic-java-agent/instrumentation/r2dbc-mysql/src/main/java/dev/miku/r2dbc/mysql/client/ReactorNettyClient_Instrumentation.java
Lines 10 to 18 in d35ffd6
It may also be the underlying
netty-reactor
instrumentation that is the real issue as the heap dump shows a lot of cached entries forreactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber
.Here is the instrumentation that was loaded in the environment that was experiencing the OOM:
The text was updated successfully, but these errors were encountered: