camel-jpa consumer fails to poll after database connection is lost

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.