Read the last line in my reply as "Should using :connect_timeout work in my case as well?".
On Tuesday, 21 August 2012 22:10:33 UTC+5:30, azi wrote: > > I am using jruby and hence the adapter in use is jdbc:mysql. Should using > jdbc:mysql work in my case as well? > > On Tuesday, 21 August 2012 21:59:50 UTC+5:30, Jeremy Evans wrote: >> >> On Tuesday, August 21, 2012 8:59:39 AM UTC-7, azi wrote: >>> >>> What is the default time limit for which sequel tries to connect to >>> mysql server in case of a default threaded connection pool. Is there any >>> way to reset this. The connection_timeout at the mysql server level is 300 >>> in my case and sequel is taking considerable time to connect to the server >>> on many occasions. I want to limit this from my end. I am okay if it throws >>> an error as this can be handled. >>> >> >> For the mysql and mysql2 adapters, Sequel doesn't have a connection >> timeout specified by default, so it probably defaults to whatever the mysql >> client library uses. You can specify the :connect_timeout option to set a >> specific connection timeout. I'm assuming if the timeout expires, you'll >> get a Sequel::DatabaseConnectionError raised. >> >> Thanks, >> Jeremy >> > -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To view this discussion on the web visit https://groups.google.com/d/msg/sequel-talk/-/SrCYaZArGLMJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
