You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2017/05/13 09:03:04 UTC
[jira] [Resolved] (CAMEL-11197) camel-jpa consumer fails to poll
after database connection is lost
[ https://issues.apache.org/jira/browse/CAMEL-11197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-11197.
---------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.19.1)
(was: 2.20.0)
2.19.0
We re-cut 2.19.0 so its included.
> camel-jpa consumer fails to poll after database connection is lost
> ------------------------------------------------------------------
>
> Key: CAMEL-11197
> URL: https://issues.apache.org/jira/browse/CAMEL-11197
> Project: Camel
> Issue Type: Bug
> Components: camel-jpa
> Affects Versions: 2.17.1
> Environment: Hibernate JPA with Tomcat Connection Pool data source
> Reporter: James Thomas
> Assignee: Claus Ibsen
> Fix For: 2.17.7, 2.18.4, 2.19.0
>
>
> Under a Hibernate JPA implementation with a Tomcat Connection pool set to test connections "on borrow", the camel-jpa consumer would poll normally until the underlying database connection was lost and then continue to report a PersistenceException at each poll.
> The entityManager instance in camel-jpa needs to be closed and rebuilt in order to force a new connection to be obtained from the connection pool.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)