Details
Assignee
UnassignedUnassignedReporter
Simon GoldschmidtSimon GoldschmidtPriority
NewLabels
Fix versions
New Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Details
Details
Assignee
Unassigned
UnassignedReporter
Simon Goldschmidt
Simon GoldschmidtPriority
Labels
Fix versions
New Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Created 15 November 2020 at 21:23
Updated 13 July 2022 at 11:40
We have an application that uses a number of MySQL datasources, including one for session storage. Each has a Connection Timeout of 1 minute and Auto Reconnect set to true. If we use the application, then let it sit idle for a minute, the Open Connections reported on the Web Administration page return to zero, except for the datasource at the END of the list of datasources in [tomcat]\lucee-server\context\lucee-server.xml, which remains open.
This leads to a prevalence of errors like this one: The last packet successfully received from the server was 32,615,195 milliseconds ago. The last packet sent successfully to the server was 32,615,195 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.
If we then add an extra datasource, the issue goes away.