Is it possible for begin .. rescue to NOT catch an exception?

Question

I have a process that is within a begin rescue loop, that looks like this:

begin
  # do some stuff
rescue Exception => e
  Rails.logger.info "#{e.response.message}"
end

Is it possible for this to NOT catch an exception? For some reason my process is running, not throwing errors, but randomly not working.

Are you in production environment? Because you shouldn't see info logging as default there. — Ursus, Dec 06 '16 at 16:31
anything can happen if you rescue `Exception`. You should catch `StandardError` — Sascha Kaestle, Dec 06 '16 at 16:52
Ok, I'll update it too `StandardError` see what happens.. And "not working" is vague, that's really my problem. I don't know why, but the process in the `begin` section doesn't send to the remote API. But I don't know why. — ToddT, Dec 06 '16 at 17:10
There isn't really enough info to answer this; the problem would seem to be that your `begin` block is never reached (perhaps due to an unhandled exception further up the call chain). — Chris Heald, Dec 06 '16 at 18:00

score 1 · Answer 1 · edited May 23 '17 at 11:45

Just use :

# do some stuff

without any begin/rescue block, and see which Error comes out. Let's say it is NoMethodError. Maybe you have a typo in some of your code, like "abc".spilt. Correct it. Try again, maybe you get Errno::ECONNRESET.

Try :

begin
  # do some stuff
rescue Errno::ECONNRESET => e
  Rails.logger.info "#{e.message}"
end

Rinse and repeat, but start from scratch. rescue Exception is just too much.

score 0 · Answer 2 · answered Dec 06 '16 at 16:31

Maybe you can temporary comment rescue block:

#begin
  ...
#rescue Exception => e
 #Rails.logger.info "#{e.response.message}"

or you can raise raise this exception in rescue:

begin
  do some stuff
rescue Exception => e
  Rails.logger.info "#{e.response.message}"
  raise e
end

Is it possible for begin .. rescue to NOT catch an exception?

2 Answers2