Hemant, As mentioned in my first email, this happens even when your worker has no code (or only a logger.info line) and no arguments passed. Nothing shows up in the log, it just hangs.
Please refer to my first email and let me know if you have any additional questions. Thank you for helping us with this issue. Csongor On Thu, Jul 17, 2008 at 6:44 AM, hemant <[EMAIL PROTECTED]> wrote: > On Thu, Jul 17, 2008 at 6:01 PM, Martin Honermeyer > <[EMAIL PROTECTED]> wrote: > > Hello guys, > > > > I just installed Backgroundrb (SVN via piston, Packet gem 0.1.7) in my > Rails > > 2.1 project. As far as I can tell, I am experiencing exactly the same > problem. > > On Linux, that is (Ubuntu 8.04, Kernel 2.6.22-14-xen)! > > > > The first asynchronous worker calls (in console) worked. Then, after > restarting > > Backgroundrb and the console, Every synchronous call hangs at the same > > position as told by Jonathan. Asynchronous calls then have no effect > either. > > > > Hemant, I tried your patch, but it doesn't change anything for me. I will > do > > anything to help ;-/ > > > > Okay. Can you pastie your worker code and rails/controller code, using > which you are invoking this methods. Also, please paste the code as > you are using. I will see, if I can reproduce this behaviour. > > Also, Check the logs. both backgroundrb_debug_11006.log and > backgroundrb_11006.log and if there is any exception there. > > Lastly, what exactly you are trying to send from your worker code? You > realize, not everything in ruby can be dumped across wire. > _______________________________________________ > Backgroundrb-devel mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/backgroundrb-devel >
_______________________________________________ Backgroundrb-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/backgroundrb-devel
