Uploaded image for project: 'Application Server 7'
  1. Application Server 7
  2. AS7-6254

Memory leak caused by retained connection ids in RemotingConnectorServer superclass

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: 7.1.1.Final, 7.1.3.Final (EAP)
    • Component/s: JMX
    • Labels:
      None

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              dlofthouse Darran Lofthouse
              Reporter:
              taras.tielkes Taras Tielkes (Inactive)
              Archiver:
              samahaja Sagar Mahajan

                Dates

                Created:
                Updated:
                Resolved:
                Archived: