This forum is no longer active. Please post your questions to our new community site

Recent Posts by Leigh

Subscribe to Recent Posts by Leigh 4 post(s) found

24 Feb, 2009 11:22 AM
Avatar Leigh 4 post(s)

Topic: RubyStack & JRubyStack / Mongel Cluster crashes after period of inactivity - Production

And finally have configured the MySQL wait_timeout parameter to something more than the default (which is about 8 hours and ties up closely with what I have observed the timeout to be)

 
24 Feb, 2009 11:05 AM
Avatar Leigh 4 post(s)

Topic: RubyStack & JRubyStack / Mongel Cluster crashes after period of inactivity - Production

Thanks Beltran.

Have also seen suggestion of adding

SetEnv force-proxy-request-1.0 1
SetEnv proxy-nokeepalive 1

to Apache Virtual Host setting, so also trying that…

 
24 Feb, 2009 09:56 AM
Avatar Leigh 4 post(s)

Topic: RubyStack & JRubyStack / Mongel Cluster crashes after period of inactivity - Production

Anyone have a feeling as to whether adding this into the bottom of environment.rb will work?

ActiveRecord::Base.connection.instance_eval {@connection.reconnect = true}

(I am testing it, but need to wait for a long period of inactivity)

 
22 Feb, 2009 03:15 PM
Avatar Leigh 4 post(s)

Topic: RubyStack & JRubyStack / Mongel Cluster crashes after period of inactivity - Production

Hi, I have my production RubyStack up and running (Windows). Have 4 Mongrel Cluster. All works flawlessly until I pop off to bedforshire, wake up in the morning, and all 4 mongrels have crashed.
Segmentation fault, which appears to be related to MySql. I am guessing it is a connection timeout issue?
Has anyone else come across this? Is there a trick / gem I need which will ensure the connections to MySql keep alive or are re-made correctly?

The error reported is at line 548 of the mysql_adapter.rb file which is

@connection.real_connect(*@connection_options)
configure_connection

Any help would be much appreciated. Following months of testing and bug fixing it is soul destroying to find the production stack is our problem! (and I apprecaite this is probably not a BitNami issue, more likely just Ruby / MySQL / Mongrel) Thanks in advance.