> This definitely works, as I'm using it and it fixes the error you're seeing.
> What file did you add the passenger block to?
I've added it to an environment file which is pretty much the first
thing I'm requiring in my config.ru
I've also tried switching passenger to use the conservative spawning
method and am still getting the same problem, so this again makes me
think the problem is nothing to do with passenger because nothing
would be reusing the connection any more.
I'm getting this problem on random requests - some of which hardly
return any data, so it doesn't make sense that it would be caused by
read timeouts because there were too many rows to process.
> Perhaps you have multiple connections open to mysql? You could try something
> like:
I've got two connections to two different databases - but I'm
disconnecting both of them in the block. Maybe having two connections
is part of the problem (they're both to the same mysql server)?
> Sequel::DATABASES.each{ |d| d.disconnect }
Maybe I should try this just to make definitely sure I'm disconnecting
everything.
Another thing that puzzles me is that the mysql adapter doesn't
include this "Lost connection during query" message in the set of
"Disconnect" error messages (https://github.com/jeremyevans/sequel/
blob/master/lib/sequel/adapters/mysql.rb line 89) - I don't know if
this is on purpose or an omission.
--
You received this message because you are subscribed to the Google Groups
"sequel-talk" group.
To post to this group, send email to sequel-t...@googlegroups.com.
To unsubscribe from this group, send email to
sequel-talk+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/sequel-talk?hl=en.
