search for: timeouterror

Anybody seen this message before? I see it over and over in one of my mongrel processes log files. I''ve never seen it before today. /usr/local/bin/mongrel_rails:16Mon May 14 20:44:30 +0000 2007: Error calling Dispatcher.dispatch #<Mongrel::TimeoutError: Mongrel timed out this thread: shutdown>Thread #<Thread:0x2ae6288dbc40 sleep> is too old, killing. Thanks, Pete

Hey Guys, I''m trying to mock the Rails Logger for the following code: ... rescue TimeoutError => error $logger.error("#{self.name} Timeout for #{path}: #{error}") and return rescue SocketError => error $logger.error("#{self.name} SocketError for #{path}: #{error}") and return rescue StandardError => error $logger.error("#{self.name...

Hey Guys, I''m trying to mock the Rails Logger for the following code: ... rescue TimeoutError => error $logger.error("#{self.name} Timeout for #{path}: #{error}") and return rescue SocketError => error $logger.error("#{self.name} SocketError for #{path}: #{error}") and return rescue StandardError => error $logger.error("#{self.name...

...writing quite a few specs lately that use Ruby''s Timeout::timeout functionality, making sure that timeout errors are properly handled and everything flows right when some command line tools timeout. I like being able to use Mocha''s #returns right now to force a method to raise a TimeoutError, but I know that usage is going away at some point. I''d like to throw out the code and see if anyone has a better way to test this with Mocha (or otherwise). Here is some simplified code showing the example: class FileSpace < ActiveRecord::Base def dsmc # remove command line wra...

...2 6109 ** USR2 signal received. Thu Sep 21 14:55:39 EDT 2006: Reaping 1 threads for slow workers because of ''shutdown'' Thread #<Thread:0x419d7ce0 run> is too old, killing. Waiting for 1 requests to finish, could take 60 seconds.Error calling Dispatcher.dispatch #<Mongrel::TimeoutError: Timed out thread.> /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:600:in `loop'' /usr/lib/ruby/1.8/cgi.rb:984:in `read_multipart'' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/cgi_ext/raw_post_data_fix.rb:20:in `initialize_query'' /usr...

Hello all, For the past couple of weeks I have been spending some time debugging a couple of issues I was having with Mongrel when I put load on it. I have seen two distinct issues: 1. Mongrel stopped responding as if in an endless loop. 2. Mongrel crashed when severely loaded. I believe to have resolved these two issues and have attached patches which shows the resolution (simple as it is).

Hello, I would like to call a function that can take infinite time to be executed in some circumstances (which can not be easily detected). So, I would like that once the function is being executed for more than two seconds it is stopped. I have found documentation for timers but i did not found how to "kill" a function. Moreover, I would like not to change the function code (it should

...sent by my app (on localhost with Postfix - OS X of course...) no proble when postfix is running.. but if Postfix is not running I don''t have any raised error... I tried using the NET lib... rescue Net::SMTPFatalError, Net::SMTPServerBusy, Net::SMTPUnknownError, Net::SMTPSyntaxError, TimeoutError no matter cannot get an error... any info or link will be welcome.. (especially on net lib..) thanks kad -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Ra...

I have this: begin sage = Net::Telnet::new( ''Host'' => sage_unit, ''Prompt'' => /\>/ ) rescue TimeoutError fail "Connection timed out, waiting to reconnect." end It outputs the text but also it gives the links for stack trace and stuff. Is there a way to just get the text back and that is all?? I do not want errors to consume the whole page just a small text field. --~--~---------~--~--...

...in/mongrel_rails:127:in `run'' /usr/lib64/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/command.rb:211:in `run'' /usr/lib64/ruby/gems/1.8/gems/mongrel-1.0.1/bin/mongrel_rails:243 /usr/bin/mongrel_rails:18Wed May 23 08:58:18 CEST 2007: Error calling Dispatcher.dispatch #<Mongrel::TimeoutError: Mongrel timed out this thread: shutdown>Thread #<Thread:0x2a9859a570 sleep> is too old, killing. Any tips on how to determine the cause of this? I''m running CentOS 4, Ruby 1.8.4. Br, Morten

Hi to everybody, This my first post on the list. I''m a newby of mongrel & rails, I''ve deployed my first project and everything seems to work fine, the only problem I have is the following: After about 1 or 2 days of the mongrel_rails daemon running the mongrel.pid in the log directory disappears, the mongrel process is still there running but doesn''t respond

...ite-packages/SQLAlchemy-0.9.6-py2.7.egg/sqlal chemy/pool.py", line 433, in checkout rec = pool._do_get() File "/opt/venv/perf/lib/python2.7/site-packages/SQLAlchemy-0.9.6-py2.7.egg/sqlal chemy/pool.py", line 945, in _do_get (self.size(), self.overflow(), self._timeout)) TimeoutError: QueuePool limit of size 5 overflow 10 reached, connection timed out, timeout 30 After browsing through the sqlalchemy documentation and bits of the LNT implementation, it seems so far that the following pieces may be the key parts that cause the problem shown in the log. The SQLAlchemy doc...

Hello, I am using Mechanize to post a form to a website. When I do this by hand in my browser the response takes about 35s to come back (it''s a long page full of tables and graphics). When I do this with Mechanize, the server starts to respond and then appears to hang. The obvious conclusion is that my code is wrong but I am reasonably sure that I haven''t altered it

Hi all, In GOOS[1] they use an assertion called assertEventually which samples the system for a success state until a certain timeout has elapsed. This allows you to synchronise the tests with asynchronous code. Do we have an equivalent of that in the Ruby / RSpec world already? I know capybara has wait_until { } but that''s fairly rudimentary - the failure message isn''t very

Hello, I''m running mongrel behind apache via proxypass. Every now and then, a spammer tries to proxy traffic through apache, and for some reason, apache forwards the request to mongrel, even though it''s not a site being hosted by me. At times this seems to cause mongrel to become unresponsive, and all requests to the site then fail with a proxy error until mongrel is

Hi list, I''m seeing a couple of issues with Mongrel. I''m running FreeBSD 6.1 and have previously been told that there are known conflicts between this and Mongrel, yet I hope these issues will be resolved with time. I''m overloading Mongrel with httperf on my local workstation. Mongrel is started directly with the mongrel_rails command and there is only one mongrel