[
https://issues.apache.org/jira/browse/ROL-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564720#comment-17564720
]
Chris Lambertus commented on ROL-2175:
--------------------------------------
Ah, thanks! I was unaware Roller could use Tomcat's Resource descriptors. I'll
give that a shot.
> mysql connection errors due to no validation
> --------------------------------------------
>
> Key: ROL-2175
> URL: https://issues.apache.org/jira/browse/ROL-2175
> Project: Apache Roller
> Issue Type: Bug
> Reporter: Chris Lambertus
> Priority: Major
>
> Pursuant to INFRA-22461, despite having autoReconnect=true in our JDBC URI,
> we still see these failures constantly:
> DatabaseException
> Internal Exception: com.mysql.cj.jdbc.exceptions.CommunicationsException: The
> last packet successfully received from the server was 85,486,668 milliseconds
> ago. The last packet sent successfully to the server was 85,486,674
> milliseconds ago. is longer than the server configured value of
> 'wait_timeout'. You should consider either expiring and/or testing connection
> validity before use in your application, increasing the server configured
> values for client timeouts, or using the Connector/J connection property
> 'autoReconnect=true' to avoid this problem.
> Error Code: 0
>
> Most java applications using the default Tomcat JDBC Resource allow for a
> validationQuery parameter such as "SELECT 1" to keep the database connection
> alive. Can such a parameter be added to roller to avoid database timeouts?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
