Ability to correlate ByteBuf leak records to log messages for a specific request #26230
Labels
in: web
Issues in web modules (web, webmvc, webflux, websocket)
type: enhancement
A general enhancement
Milestone
When Netty's
ResourceLeakDetector
prints a report about leaked buffers, there is currently no way to match those to log messages for the request where the ByteBuf was created. We can useByteBuf#touch
with the log prefix for the request (based on the channel id) when debug logging is enabled, similar to what Reactor Netty does.The text was updated successfully, but these errors were encountered: