[
https://issues.apache.org/jira/browse/CAMEL-7598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14067570#comment-14067570
]
Claus Ibsen commented on CAMEL-7598:
------------------------------------
Thanks, so do you mean that we should just call clear after the flush?
A patch is welcome
> 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
> Fix For: 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)
