Details
Description
See pretty nice analysis on SO https://stackoverflow.com/questions/56110408/memory-leak-in-camel-netty-tcp-client-when-consuming-lines-with-windows-line-bre
io.netty.handler.codec.DelimiterBasedFrameDecoder internally delegates decoding to io.netty.handler.codec.LineBasedFrameDecoder. This delegation is not working with Camel, because Netty internally checks for condition
this.getClass() != DelimiterBasedFrameDecoder.class // io.netty.handler.codec.DelimiterBasedFrameDecoder line 174 - !isSubclass()
We can recreate similar optimisation inside org.apache.camel.component.netty4.codec.DelimiterBasedFrameDecoder and get (according to SO post) significant performance improvement.
Attachments
Issue Links
- links to