Closed raccoonback closed 3 weeks ago
@raccoonback Your Reactor Netty version is not supported anymore. Please update to a supported version (more info here)
This might be helpful also https://projectreactor.io/docs/netty/release/reference/index.html#faq.memory-leaks
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.
@violetagg
Hello. We are using reactor-netty's HttpClient instead of WebClient for routing. When I checked, it seems that the error log above occurred during the GC process because the bytebuf for the response was not released when the client request was canceled. (In fact, I found a lot of 499 response statuses in NGINX.) In the case of WebClient, it can be solved by using retrieve(), but in the case of HttpClient, there seems to be cases where it is not released, so I modified it to release the bytebuf at the end by adding a filter to the spring gateway. Thank you for the guide. ref. https://speakerdeck.com/violetagg/how-to-avoid-common-mistakes-when-using-reactor-netty?slide=85
Expected Behavior
Actual Behavior
I am running a service with
spring gateway
based onreactor-netty
.I am checking for memory leaks by setting
io.netty.leakDetectionLevel=advanced
, but I frequently get the following error.or
or
I am guessing that the
HTTP request
was unexpectedly disconnected on the side that called it, but I would like to ask if there is an issue with the part that I guessed.The reason I guessed that the http request was disconnected is because the
HTTP response status 499
that occurred in NGINX occurred similarly.Steps to Reproduce
Possible Solution
Your Environment
netty
, ...):java -version
):uname -a
):