# Dissecting an SystemExit

**URL:** <https://www.ruby-forum.com/t/dissecting-an-systemexit/90710>\
**Category:** Rails\
**Created:** [March 31, 2007, 9:58am UTC](https://www.ruby-forum.com/t/dissecting-an-systemexit/90710 "2007-03-31T09:58:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![msojka](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/b5a626/32.png) [@msojka](https://www.ruby-forum.com/u/msojka)\
**Post date:** [March 31, 2007, 9:58am UTC](https://www.ruby-forum.com/t/dissecting-an-systemexit/90710/1 "2007-03-31T09:58:49Z")

</div>

Hi,

I´m doing about 300 Net::HTTP.get URI.parse(url) from a for-loop.  
But the loop didn´t get trough more than 150 gets before I got an  
ApplicationError.  
How do I dissect the output from the development.log?  
I see that timeout is listed a few times, did the application die  
because of  
a http-get timeout?

SystemExit (exit):  
/vendor/rails/railties/lib/fcgi\_handler.rb:126:in `exit' /vendor/rails/railties/lib/fcgi_handler.rb:126:in`exit\_now\_handler’  
/usr/local/lib/ruby/site\_ruby/1.8/rubygems/custom\_require.rb:27:in  
`to_proc' /usr/local/lib/ruby/1.8/net/http.rb:560:in`call’  
/usr/local/lib/ruby/1.8/net/http.rb:560:in `initialize' /usr/local/lib/ruby/1.8/net/http.rb:560:in`open’  
/usr/local/lib/ruby/1.8/net/http.rb:560:in `connect' /usr/local/lib/ruby/1.8/timeout.rb:48:in`timeout’  
/usr/local/lib/ruby/1.8/timeout.rb:76:in `timeout' /usr/local/lib/ruby/1.8/net/http.rb:560:in`connect’  
/usr/local/lib/ruby/1.8/net/http.rb:553:in `do_start' /usr/local/lib/ruby/1.8/net/http.rb:542:in`start’  
/usr/local/lib/ruby/1.8/net/http.rb:379:in `get_response' /usr/local/lib/ruby/1.8/net/http.rb:356:in`get’  
/app/controllers/sms\_controller.rb:98:in `sms' /app/controllers/sms_controller.rb:53:in`send\_sms’  
/app/controllers/sms\_controller.rb:52:in `each' /app/controllers/sms_controller.rb:52:in`send\_sms’  
/vendor/rails/actionpack/lib/action\_controller/base.rb:941:in `send' /vendor/rails/actionpack/lib/action_controller/base.rb:941:in`perform\_action\_without\_filters’  
/vendor/rails/actionpack/lib/action\_controller/filters.rb:368:in  
`perform_action_without_benchmark' /vendor/rails/actionpack/lib/action_controller/benchmarking.rb:69:in`perform\_action\_without\_rescue’  
/usr/local/lib/ruby/1.8/benchmark.rb:293:in `measure' /vendor/rails/actionpack/lib/action_controller/benchmarking.rb:69:in`perform\_action\_without\_rescue’  
/vendor/rails/actionpack/lib/action\_controller/rescue.rb:82:in  
`perform_action' /vendor/rails/actionpack/lib/action_controller/base.rb:408:in`send’  
/vendor/rails/actionpack/lib/action\_controller/base.rb:408:in  
`process_without_filters' /vendor/rails/actionpack/lib/action_controller/filters.rb:377:in`process\_without\_session\_management\_support’

/vendor/rails/actionpack/lib/action\_controller/session\_management.rb:117:in  
`process' /vendor/rails/railties/lib/dispatcher.rb:38:in`dispatch’  
/vendor/rails/railties/lib/fcgi\_handler.rb:150:in `process_request' /vendor/rails/railties/lib/fcgi_handler.rb:54:in`process!’  
/usr/local/lib/ruby/gems/1.8/gems/fcgi-0.8.7/lib/fcgi.rb:612:in  
`each_cgi' /usr/local/lib/ruby/gems/1.8/gems/fcgi-0.8.7/lib/fcgi.rb:609:in`each’  
/usr/local/lib/ruby/gems/1.8/gems/fcgi-0.8.7/lib/fcgi.rb:609:in  
`each_cgi' /vendor/rails/railties/lib/fcgi_handler.rb:53:in`process!’  
/vendor/rails/railties/lib/fcgi\_handler.rb:23:in `process!’  
dispatch.fcgi:28

Cheers,  
Martin S.

---

<div class="post-metadata">

**Author:** ![msojka](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/b5a626/32.png) [@msojka](https://www.ruby-forum.com/u/msojka)\
**Post date:** [April 1, 2007, 4:07am UTC](https://www.ruby-forum.com/t/dissecting-an-systemexit/90710/2 "2007-04-01T04:07:30Z")

</div>

Martin S. wrote:

> Hi,
> 
> I´m doing about 300 Net::HTTP.get URI.parse(url) from a for-loop.  
> But the loop didn´t get trough more than 150 gets before I got an  
> ApplicationError.  
> How do I dissect the output from the development.log?  
> I see that timeout is listed a few times, did the application die because of  
> a http-get timeout?

Could be. You could try wrapping your call around a begin rescue block  
and see if the exception bubbles all the way up to the top.

–  
Michael W.