[Backgroundrb-devel] Problem with blocking workers

Ezra Zygmuntowicz ezmobius at gmail.com
Tue Apr 3 14:46:05 EDT 2007

	It sounds to me like the sybase-ruby driver blocks when being  
called. If something blocks in a ruby thread then it can block all  
other ruby threads. That appears to be what it happening here.


On Apr 3, 2007, at 3:26 AM, Christian Schlaefcke wrote:

> Hi Folks,
> I found this thread
> http://rubyforge.org/pipermail/backgroundrb-devel/2007-March/ 
> 000790.html
> on this mailing list that describes pretty much the same behaviour  
> that I
> experience as well.
> My problem is, that I have no chance for putting a "sleep 0" in an
> iteration because I have no Iteration.
> What I´m doing is executing a stored procedure in a sybase db that  
> could
> take from few seconds up to hours to complete. The stored procedure  
> gets
> executed and spools the result to another table where the user could
> access it later. So in my worker I don´t actually iterate over the  
> results
>  instead it waits until the stored procedure has finished.
> I need to get different jobs with different execution times  
> executed at
> the same time. This is how I understand concurrency.
> How could I solve my problem? Are concurrent tasks possible anyway?
> Thanks & Regards,
> Christian Schlaefcke
> _______________________________________________
> Backgroundrb-devel mailing list
> Backgroundrb-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/backgroundrb-devel

-- Ezra Zygmuntowicz 
-- Lead Rails Evangelist
-- ez at engineyard.com
-- Engine Yard, Serious Rails Hosting
-- (866) 518-YARD (9273)

More information about the Backgroundrb-devel mailing list