similar to: Finding out what line number exceptions were raised?

If there is an exception raised in my worker I rescue it and throw it into the log. This is decent, but it would really help to find out more information. Like the line number, the stack trace, etc. Is this possible? Thanks for your help. Thank You, Ben Johnson E: bjohnson at contuitive.com -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, I have a worker, which should have thrown an uncaught exception and dumped the stack in the do_work method, however I saw no dump or indication of any error in any of the logs. This makes it very hard to debug, where does stdout and or stderr go? How canb I know if it gets some kind of error? (in this case not being able to find a class). Thanks -- Jim Morris, http://blog.wolfman.com

this: Index: script/backgroundrb/lib/backgroundrb.rb =================================================================== --- script/backgroundrb/lib/backgroundrb.rb (revision 16) +++ script/backgroundrb/lib/backgroundrb.rb (working copy) @@ -29,7 +29,11 @@ # the log via @logger def initialize(args) @logger = BACKGROUNDRB_LOGGER - Thread.new { do_work(args) } +

Hi all, Like most other frameworks, Ruby groups code by Model/View/Controller instead of by task, and therefore I''m having a hard time debugging a problem from the Agile Rails book where looping through @items errors out because one or more items is nil. I managed to empty the cart by placing session[:cart] = nil in find_cart() in the store_controller_rb, and the problem continued

Is there a convention for handling exceptions within BackgrounDRb workers? For example, I have a worker which does some asynchronous data processing (*not* a scheduled worker) based on some things in the database. However, if an exception is raised within that worker, then the process for that worker is killed off. Ideally I would want that worker to just silently fail and be optimistic that it

I''ve been trying unsuccessfully for the better part of today to write a worker that can use by ActiveRecord model classes. The bizarre thing is that worker just stops at the point accessing the database connection. An exception isn''t raising, it just dies. My worker class is below, I''ve interspersed log messages throughout to try to determine where it is dying. =====

Hi, I have a big index and wildcard query raises an exception. That is all right. The problem is I can not rescue this exception and it bombs right to user page. Why? I am on Linux. Ferret 0.9.3 with C extentions. >> class A >> def self.b >> Book.index.search(''isbn:00*'') >> rescue >> puts ''ok'' >> end >> end =>

By default, Mongrel will delete the HTTP request body and short circuit calling any handlers if a request is interrupted or incomplete. Unfortunately, this breaks any attempt to correctly handle a partial PUT. (BTW, PUT is *way* more efficient for uploads compared to POST which requires a MIME parsing step.) So, about a month ago I wrote up some patches to Mongrel 0.3.18 that allowed

Since Merb has the lovely property of rendering the output of an action, using ruby-level exceptions to render error pages in Merb could be a cute way to approach error handling. Suppose one has an action for editing a product which you would like to restrict to administrators: def edit raise AdminAccessReqired unless session[:user] and session[:user].admin? @product =

Hi begin ActiveRecord::Base.transaction do pb_status_history = ProblemStatusHistory.new pb_status_history.problem_id = @problem.id pb_status_history.problem_status_id = @problem.problem_status_id pb_status_history.save! ret_val=@problem.update_attribute("problem_status_id",''ab'') if ret_val==false

Hey. I have a very annoying problem, and was wondering what is wrong. Suppose I have backgroundrb running, and then I have an action in some controller. In the action I define a worker. When leaving the action, suddenly the connection to backgroundrb is lost: DRb URI: druby://localhost:22222 Pid: 3976 Autostart... done druby://localhost:42531 - #<Errno::EBADF: Bad file descriptor -

The error is caused by the save! method updating an object that another thread (most likely in taskomatic) already updated. In the case of this race condition, we retry saving. However, a proper fix would involve fixing the locking. --- src/db-omatic/db_omatic.rb | 23 ++++++++++++++++++++--- 1 files changed, 20 insertions(+), 3 deletions(-) diff --git a/src/db-omatic/db_omatic.rb

My app runs fine on webrick, but I get a ActiveRecord::ConnectionNotEstablished when I try to run it on lighttpd. Here''s the app''s lighttpd config: $HTTP["host"] =~ "(www\.)?mysite\.com" { server.document-root = "/home/pergesuteore/public/" server.error-handler-404 = "/dispatch.fcgi" fastcgi.server = ( ".fcgi" => (

Hello, I was trying to to write a simple ruby program for exceptions. My code is: class ABC begin alpha = ABC.new alpha.foo= [1,2,3] puts foo.inspect.to_s NonExisting raise "all other exceptions" rescue Exception => NoMethodError puts ''Hello'' puts $ERROR_INFO.inspect rescue Exception => NameError puts ''goodbye'' puts $ERROR_INFO.inspect else

He folks- First off thanks to everyone for helping to make this plugin work better for all of us. Its nice to have a bunch of people testing and adding features. I would like to ask for people to post some examples workers. I would really like to get a few more workers to distribute with the plugin. Especially ones that a lot of people seem to need like Email workers. So if you are

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

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

I have a simple question, but can''t seem to figure this out. I added an in place editor field and didn''t like how it didn''t use the save method. It uses the update_attribute method which does not run validation, etc. So I just added the method in my controller myself: def set_event_url begin @event = Event.find params[:id] @event.url =

Does after_save in a model delete if an exception is raised in there? I simply did def after_save raise ''hmmm'' end and it raised the exception but there was nothing in the database. I removed that entire method and its in the database. Is this correct? Thank You, Ben Johnson E: bjohnson@contuitive.com -------------- next part -------------- An HTML attachment was

Hello, maybe someone can help with backgroundrb. I''ve written an application, which makes use of backgroundrb. Everything works fine on my development machine, but it crashes on my production server. Something seems to be wrong with backgroundrb, but I don''t know the cause. All I get is the error message attached below, which is extracted from the production.log. I