search for: rb_thread_schedul

...) [sparc-solaris2.10] [2006-04-07 12:22:23] INFO WEBrick::HTTPServer#start: pid=29446 port=3000 127.0.0.1 - - [07/Apr/2006:12:22:49 MDT] "GET /ws/invoke HTTP/1.1" 404 598 - -> /ws/invoke /opt/lib/ruby/gems/1.8/gems/rails-1.1.0/lib/webrick_server.rb:62: [BUG] cross-thread violation on rb_thread_schedule() ruby 1.8.4 (2005-12-24) [sparc-solaris2.10] Abort (core dumped) Last log entries: ActionController::RoutingError (Recognition failed for "/ws/invoke"): /opt/lib/ruby/gems/18/gems/actionpack-1120/lib/action_controller/routingrb:488:in `recognition_failed'' /opt/lib/ruby/...

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

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. http://people.inxsasia.com/~hemant

...re the signal was received. To change this behavior use "set unwindonsignal on" Evaluation of the expression containing the function (rb_p) will be abandoned. (gdb) eval "caller()" [weavere at c13-chd-app1 tools]$ Program received signal SIGINT, Interrupt. 0x00000000004132d9 in rb_thread_schedule () at eval.c:10618 10618 in eval.c The program being debugged was signaled while in a function called from GDB. GDB remains in the frame where the signal was received. To change this behavior use "set unwindonsignal on" Evaluation of the expression containing the function (rb_eval_stri...

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