[jira] [Commented] (CAMEL-11197) camel-jpa consumer fails to poll after database connection is lost

2017-04-26 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-11197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15985271#comment-15985271
 ] 

ASF GitHub Bot commented on CAMEL-11197:


Github user jamesET closed the pull request at:

https://github.com/apache/camel/pull/1658


> 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.20.0, 2.19.1
>
>
> 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)


[jira] [Commented] (CAMEL-11197) camel-jpa consumer fails to poll after database connection is lost

2017-04-26 Thread Claus Ibsen (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-11197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15985174#comment-15985174
 ] 

Claus Ibsen commented on CAMEL-11197:
-

Thanks for the PR

> 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.20.0, 2.19.1
>
>
> 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)


[jira] [Commented] (CAMEL-11197) camel-jpa consumer fails to poll after database connection is lost

2017-04-26 Thread Claus Ibsen (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-11197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15985158#comment-15985158
 ] 

Claus Ibsen commented on CAMEL-11197:
-

Need to merge to 2.19.x branch after the release

> 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
> Fix For: 2.18.4, 2.20.0, 2.19.1
>
>
> 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)


[jira] [Commented] (CAMEL-11197) camel-jpa consumer fails to poll after database connection is lost

2017-04-25 Thread James Thomas (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-11197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15982754#comment-15982754
 ] 

James Thomas commented on CAMEL-11197:
--

Discussion and stack trace at 
http://camel.465427.n5.nabble.com/camel-jpa-and-PersistenceException-tp5795205.html

> 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
>
> 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)


[jira] [Commented] (CAMEL-11197) camel-jpa consumer fails to poll after database connection is lost

2017-04-25 Thread James Thomas (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-11197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15982747#comment-15982747
 ] 

James Thomas commented on CAMEL-11197:
--

Patch available:  https://github.com/apache/camel/pull/1658

> 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
>
> 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)