[jboss-jira] [JBoss JIRA] (AS7-6254) Memory leak caused by retained connection ids in RemotingConnectorServer superclass

[Taras Tielkes (JIRA)]

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

Taras Tielkes edited comment on AS7-6254 at 1/2/13 3:32 PM:
------------------------------------------------------------

The compressed hprof heap snapshot is ~80 MB. If there is a Jboss FTP server I can upload it to, let me know how to reach it.
                
      was (Author: taras.tielkes):
    The compressed hprof heap snapshot is ~80 MB. If there is a Jboss FTP server I ca upload it to, let me know where to find it.
                  
> Memory leak caused by retained connection ids in RemotingConnectorServer superclass 
> ------------------------------------------------------------------------------------
>
>                 Key: AS7-6254
>                 URL: https://issues.jboss.org/browse/AS7-6254
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: JMX
>    Affects Versions: 7.1.1.Final, 7.1.3.Final (EAP)
>            Reporter: Taras Tielkes
>            Assignee: Darran Lofthouse
>            Priority: Blocker
>
> We're running 7.1.1, with a patch applied for REMJMX-45 to limit the worst leaks coming from the JMX subsystem.
> However, even with this patch applied we can only survive for a few days in a production-like scenario.
> It seems that {{org.jboss.remotingjmx.RemotingConnectorServer}} never calls the {{connectionClosed()}}/{{connectionFailed()}} methods in its superclass.
> As such, the connection ids that are stored in the field {{javax.management.remote.JMXConnectorServer#connectionIds}} are never released.
> Given sufficient connections made to a running instance of 7.1.1 (for example, various monitoring tools), an out-of-memory end-state is inevitable.

--
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