[jboss-jira] [JBoss JIRA] (JGRP-1616) a memory leak on TCP protocol (leak object is java.net.socket)

[Bela Ban (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766381#comment-12766381 ] 

Bela Ban commented on JGRP-1616:
--------------------------------

The sockets hashmap was removed in 3.x, and since 2.12.x is not supported, I'm closing this JIRA.
Please discuss this on the mailing list next time, before creating a JIRA.
                
> a memory leak on TCP protocol (leak object is java.net.socket)
> --------------------------------------------------------------
>
>                 Key: JGRP-1616
>                 URL: https://issues.jboss.org/browse/JGRP-1616
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 2.12.1
>         Environment: two node using TCP as transport protocol
>            Reporter: freeliuade freeliuade
>            Assignee: Bela Ban
>            Priority: Minor
>              Labels: TCP, leak,
>
> in our product stress test, we will kill/restart one node continouslly, and we using GC Viewer find there is a tiny memory leak, and finally we find the leak object is java.net.Socket.
> next we find the socket object is hold by DefaultSocketFactory's sockets map.
> more investigate/debug, (uncertain, hope it can help identify the issue) 
> in TCPConnectionMap$Mapper.getConnection(Address dest), it will get a TCPConnection from conns hashmap, then it find the conn is not open, and recreated a new connection, but it seems hasn't close the old one.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira