Mailing-List: contact jena-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jena-dev@incubator.apache.org
Date: Tue, 16 Aug 2011 09:10:27 +0000 (UTC)
From: "Damian Steer (JIRA)" <jira@apache.org>
To: jena-dev@incubator.apache.org
Message-ID: 
 <635827931.40868.1313485827205.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1680671164.39936.1313448927451.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (JENA-101) Memory leak in Fuseki
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Damian Steer updated JENA-101:
------------------------------

    Priority: Major  (was: Minor)

Bumped to 'major', affects all stores.

> Memory leak in Fuseki
> ---------------------
>
>                 Key: JENA-101
>                 URL: https://issues.apache.org/jira/browse/JENA-101
>             Project: Jena
>          Issue Type: Bug
>          Components: Fuseki
>            Reporter: Damian Steer
>              Labels: fuseki, memory_leak
>
> Steps to reproduce:
> 1. Start fuseki in memory mode with updates enabled.
> 2. Repeatedly PUT an N-Triple or turtle file to the same graph.
> 3. Attach VisualVM.
> 4. Memory use slowly grows and is not all collected.
> Explanation:
> The parser uses the sink SinkTriplesToGraph, which registers itself with the global RIOT event manager. The sink is never closed by fuseki, and so is never unregistered, which means the sink remains reachable. The sink also has a reference to the graph, so each added graph remains forever.
> Closing the sink seems to fix the issue. Not clear if this is especially a memory mode issue.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira