TCP and TLS Memory Leak for broken connection on NIO

looneyapurv / jain-sip

Automatically exported from code.google.com/p/jain-sip

0 stars 0 forks source link

TCP and TLS Memory Leak for broken connection on NIO #144

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

There is stil slowly increasing size of memory. The memory is hold by instance 
of NioTlsMessageProcessor (NioTcpMessageProcessor) in pendingData hash map. 2 
hours of trafic test show 396 instances of SocketChannelImpl and 22 instances 
of NioTlsMessageChannel. SocketChannelImp instances are still in the 
pendingData.

https://telestax.atlassian.net/browse/JSIP-15

Original issue reported on code.google.com by jean.der...@telestax.com on 22 Aug 2014 at 8:40

GoogleCodeExporter commented 9 years ago

https://java.net/jira/browse/JSIP-475

Original comment by jean.der...@telestax.com on 22 Aug 2014 at 8:41

GoogleCodeExporter commented 9 years ago

This issue was updated by revision e5c24ea3ac47.

JSIP-475 backporting to masyter - fix validated by customer

(cherry picked from commit 533573f5085529a04dd970b8daf744a4203931c1)

Original comment by jean.der...@telestax.com on 22 Aug 2014 at 8:54

GoogleCodeExporter commented 9 years ago

Original comment by jean.der...@telestax.com on 22 Aug 2014 at 8:57

Changed state: Fixed

GoogleCodeExporter commented 9 years ago

This issue was updated by revision 205966879079.

JSIP-475 another leak found where some socket were stored in the iohandler 
instead of NIOHandler for NIO mode

(cherry picked from commit 37175fe259d0815d0c6db43fd176d43c0ddab207)

Original comment by jean.der...@telestax.com on 22 Sep 2014 at 12:53