similar to: webrick, cross-thread violation on rb_thread_schedule()

I tried the current Typo trunk with Edge Rails (1.1.0 RC1) and ran into the following problems: 1) /public/../config/environment.rb:107: undefined method `enable_upload_progress'' for ActionController::Base:Class (NoMethodError). I commented this line out and installed the Upload Progress plugin and this problem _appears_ to have gone away. 2) The second problem I

recently i noticed in my mongrel log files: /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:374: [BUG] cross-thread violation on rb_thread_schedule() ruby 1.8.4 (2005-12-24) [i486-linux] any ideas why? With mongrel 1.0.1 -- gnufied ----------- There was only one Road; that it was like a great river: its springs were at every doorstep, and every path was its tributary.

Hi all, I''m getting a strange, intermittent Thread deadlock in production: deadlock 0x2a988d7008: sleep:F(3) - /opt/ruby/default/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb:723 CPU usage spikes to a full core and Apache 502''s on requests that got handed to that particular listener each time. I tried attaching with gdb, and gdb twisted itself into a knot. Anyone have

Hi, I am using wxRuby 1.9.7 and Ruby 1.8.6. I have built an extension in C++ and used swig to load it into Ruby interpreter, which works great. The extension is an often long executing algorithm, and I''ve noticed that if I fork a new Ruby thread in button clicked event, and in this thread run the algorithm the application freezes for the time of execution. I have looked through the

Hi all we have samba 3.0.21c with OpenLDAP backend as PDC and also 4 BDC's Suddenly on PDC we are getting these error messages in /var/log/messages I am unable to register any system to the domain. niether able to logon to the domain. ########################################################################################## Feb 15 11:14:32 msdpl smbd[18212]: [2007/02/15 11:14:32, 0]

I have a Rails 1.2.3 app (due for an update, I know) running on a Mongrel 1.1.4 behind Apache 2.2.3 mod_proxy on Debian 4.0. It keeps hanging up for no reason I can tell. I have tried everything that anyone has ever hinted at being a solution for this problem: - The application doesn''t use MySQL, so setting the connection timeout won''t help. - Using AR not PStore for sessions. -

Hello Guys, I''m reviewing the code for 1.9, and forgot about this when we first spoke on this subject. The current way we stop threads is using Thread#raise to spread StopServer exception, which will not work as expected in 1.9. 1.9 will treat raised exceptions as #kill, like JRuby does, so the worker threads will not finish serving the client and _then_ exiting, but will be