Thanks for posting this. It really should be explained in the Workling documentation.
On Apr 10, 3:11 am, Albert Wong <[email protected]> wrote: > Finally figured this out, and posting it incase anyone else runs into > this issue. > > It has to do with logger buffers everything sent to is and does not auto > flush in production environment. > > So a quick fix is to call logger.flush whenever the worker completes, > probably a better way to do this by putting it in some after filter, but > not sure if workling has such a filter... > -- > Posted viahttp://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
