Uncaught ThreadError
-
Kevin Williams- Milestone cleared.
- State changed from new to open
-
Kevin Williams
could we catch the ThreadError and see which thread threw the error? If not the thread Thin cares about, ignore it?
just thinking out loud
-
macournoyerweird thing is the error is not caught by the rescue Object => e in Connection#process
how come?
-
macournoyer
- State changed from open to invalid
I can reproduce the error, but in my case, it's caught by the rescue block and the server keeps running.
-
steve rossHere's the pertinent part of the stack trace:
/usr/local/lib/ruby/gems/1.8/gems/thin-0.5.3/lib/rack/adapter/rails.rb:52:in `serve_rails'
/usr/local/lib/ruby/gems/1.8/gems/thin-0.5.3/lib/rack/adapter/rails.rb:67:in `call'
/usr/local/lib/ruby/gems/1.8/gems/thin-0.5.3/lib/thin/connection.rb:30:in `process'
/usr/local/lib/ruby/gems/1.8/gems/thin-0.5.3/lib/thin/connection.rb:16:in `receive_data'
/usr/local/lib/ruby/gems/1.8/gems/eventmachine-0.10.0/lib/eventmachine.rb:1056:in `event_callback'
/usr/local/lib/ruby/gems/1.8/gems/eventmachine-0.10.0/lib/eventmachine.rb:224:in `run_machine'
/usr/local/lib/ruby/gems/1.8/gems/eventmachine-0.10.0/lib/eventmachine.rb:224:in `run'
/usr/local/lib/ruby/gems/1.8/gems/thin-0.5.3/lib/thin/server.rb:55:in `listen!'
/usr/local/lib/ruby/gems/1.8/gems/thin-0.5.3/lib/thin/server.rb:44:in `start!'
/usr/local/lib/ruby/gems/1.8/gems/thin-0.5.3/bin/thin:85:in `start'
/usr/local/lib/ruby/gems/1.8/gems/thin-0.5.3/bin/thin:116:in `send'
/usr/local/lib/ruby/gems/1.8/gems/thin-0.5.3/bin/thin:116
/usr/local/bin/thin:19:in `load'
-
-
Kevin Williams
- Milestone set to 0.6.2
-
macournoyer
- State changed from open to invalid
I tried reproducing in any way I could, the error is always caught by Thin's rescue block.
Plz reopen if you can reproduce
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.