Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Thu, 8 Aug 2013 10:37:49 +0000 (UTC)
From: "Amichai Rothman (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12662586.1375958063471.23966.1375958269080@arcas>
In-Reply-To: <JIRA.12662586.1375958063471@arcas>
References: <JIRA.12662586.1375958063471@arcas>
Subject: [jira] [Updated] (CXF-5188) Possible memory leak in ServiceImpl
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CXF-5188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amichai Rothman updated CXF-5188:
---------------------------------

    Attachment: ServiceImpl_leak_snapshot.png
    
> Possible memory leak in ServiceImpl
> -----------------------------------
>
>                 Key: CXF-5188
>                 URL: https://issues.apache.org/jira/browse/CXF-5188
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.7.2
>         Environment: Karaf 2.3.2, DOSGi 1.6.0-SNAPSHOT
>            Reporter: Amichai Rothman
>         Attachments: ServiceImpl_leak_snapshot.png
>
>
> I've been looking at VisualVM heap dumps after restarting some custom bundles in Karaf and noticed the stopped services (exported via DOSGi) linger in memory and are never garbage collected (screenshot attached, StoreServiceImpl being the lingering custom service). Browsing through the instance hierarchy from the snapshot I found something suspicious - org.apache.cxf.endpoint.ServiceImpl registers the ManagedEndpoint with the ServerLifeCycleManager, but doesn't seem to unregister it when the instance is destroyed. Could this be the memory leak preventing the old bundles from being collected?

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