This content has been marked as final. Show 2 replies
The issue is that your database connection has been lost somehow. This may be caused by a timeout in your database or firewall, or a database or network error.
You can either try resolve the database/network issue, or workaround the issue.
In TopLink by default when using a recent version of EclipseLink, dead connections should be automatically detected and reconnected. You will still get the error, but the connection will be dropped form the pool and a new connection used for the query. If you just want the error out of your log, then disable logging or disable exception logging.
To avoid the issue entirely, you could disable connection pooling by setting your min pool size to 0, but this can adversely affect performance.
You could also use a third party DataSource such as Oracle UCP, that provides additional dead connection resolution solutions.
Thanks for the response.
It seems to match my analysis.