[
https://issues.apache.org/jira/browse/CAMEL-7364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984083#comment-13984083
]
Claus Ibsen commented on CAMEL-7364:
------------------------------------
Yeah we should likely use the factory to create an entity manager instance and
use that, and then close it after use.
> JpaMessageIdRepository uses EntityManager non thread-safe
> ---------------------------------------------------------
>
> Key: CAMEL-7364
> URL: https://issues.apache.org/jira/browse/CAMEL-7364
> Project: Camel
> Issue Type: Bug
> Components: camel-jpa
> Affects Versions: 2.12.3
> Environment: tomcat 7.0.32, hibernate 4.1.4.Final, spring
> 3.1.4.RELEASE
> Reporter: Denis Galkin
> Labels: easyfix
>
> In our product we have found strange behavior of JpaMessageIdRepository when
> change version 2.9.2 to 2.12.3.
> The reason for this was that EntityManager assigned in the constructor
> org.apache.camel.processor.idempotent.jpa.JpaMessageIdRepository, but
> EntityManager not required to be thread safe.
> http://download.oracle.com/otn-pub/jcp/persistence-2.0-fr-oth-JSpec/persistence-2_0-final-spec.pdf
> page 286.
> I think need assign the EntityManager in each method separately.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
