Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Thu, 24 Jul 2014 13:19:39 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12727081.1405342737623.37364.1406207979301@arcas>
In-Reply-To: <JIRA.12727081.1405342737623@arcas>
References: <JIRA.12727081.1405342737623@arcas>
Subject: [jira] [Updated] (CAMEL-7598) Camel does not clear the jpa session
 after each processed message batch
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Claus Ibsen updated CAMEL-7598:
-------------------------------

    Fix Version/s: 2.12.5

> Camel does not clear the jpa session after each processed message batch
> -----------------------------------------------------------------------
>
>                 Key: CAMEL-7598
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7598
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-jpa
>    Affects Versions: 2.12.3
>            Reporter: Daniel Seidewitz
>            Assignee: Claus Ibsen
>             Fix For: 2.12.5, 2.13.3, 2.14.0
>
>
> We are using apache camel to poll from a database. As we want processed rows only to be updated we have disabled consumeDelete on the JPA endpoint. 
> During testing we found a large memory leak: all polled entities are kept in the session cache (we are using hibernate as persistence provider). 
> The issue seems to be in the JpaConsumer. In method poll() it calls enitityManager.joinTransaction() at the beginning and entitiyManager.flush() at the end of the method but it never calls  entityManager.clear(). As camel is reusing the underlying session during each poll() this causes the first level entity cache to grow indefinitely. 


--
This message was sent by Atlassian JIRA
(v6.2#6252)