MySQL broken pipe
Reported by Denis Vergnes | January 28th, 2012 @ 07:27 PM
After a while (8 hours), connection on mysql is closed then a broken pipe error affects rundeck application. It is a common issue with DBCP and MySQL and most often it is fixed by using a validation query such as select 1 to validate connection before using it. The thing is : how to configure this in rundeck configuration file, it seems dataSource.validationQuery = "select 1" is ignored.
Comments and changes to this ticket
-
Greg Schueler February 3rd, 2012 @ 01:39 PM
Hi, the rundeck-config.properties file is a grails config file, and you can specify all your datasource config as described in the grails documentation here http://grails.org/doc/1.3.7/guide/3.%20Configuration.html#3.3%20The...
You might try "dataSource.properties.validateQuery". If it doesn't work it may be because the rundeck-config.properties is in "properties" format, not "groovy" format. You might have to alter the config file syntax to be groovy.
The syntax issue has come up before, I will add a ticket for making groovy the default syntax.
-
Bryan Fransman March 2nd, 2012 @ 07:57 AM
All,
Typo in the property definition:
validationQuery not validateQuery
I'm currently testing (/etc/rundeck/rundeck-config.properties):
dataSource.properties.validationQuery = SELECT 1
I'll try to report back my results after the timeout has occurred.
-
Greg Schueler June 22nd, 2012 @ 11:15 AM
- State changed from new to wontfix
- Assigned user set to Greg Schueler
i think the autoReconnect flag may be the other part of this issue. see http://rundeck.org/docs/administration/relational-database.html#cus...
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
(DEPRECATED) Please use github issues for issue tracking at http://github.com/dtolabs/rundeck/issues