<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Thanks for responding. <br>
<br>
I figured out at lunchtime the problem was my fault.<br>
<br>
I had a backgroundrb server running on a 2nd machine that I<br>
forgot about. This worked ok until I switched to a persistent<br>
queue. Then both processes were accessing the same database<br>
and each worker grabbed a different task. The 2nd machine croaked<br>
but I wasn''t checking it''s log.<br>
<br>
It is working fine now. I really like this plugin.<br>
<br>
Regards,<br>
Don Mc<br>
<br>
<br>
<br>
hemant wrote:
<blockquote
cite="mid:fb283d5e0903131234p68733fecwf0452bf99e1dbdf8@mail.gmail.com"
type="cite">
<pre wrap="">2009/3/13 Don McClean <a
class="moz-txt-link-rfc2396E"
href="mailto:d-mcclean@ti.com"><d-mcclean@ti.com></a>:
</pre>
<blockquote type="cite">
<pre wrap="">I am using backgroundrb with rails and have a
problem if I submit two jobs
to be handled and the 2nd job is submitted before the first job is complete.
The 2nd job is never worked on, although in the database table, it is marked
as
taken.
I have a single worker which is created at rails startup. I am enquing the
task. I had thought the
the 2nd job would be in a queue and would be worked on after
the first job is done. Am I wrong? Do I need to create a pool?
I am using Oracle with rails 2.1.2
I set the allow_concurrency = false
in the 3 places I found it set to true in the backgroundrb code, per
the FAQ, but it did not seem to matter.
</pre>
</blockquote>
<pre wrap=""><!---->
Unforunately, I never had opportunity to test job queues with Oracle
DB. Your best bet is to test your code with sqlite/mysql and see if
you are still having the problem. However if 2nd job never ran it
sounds like a problem with the code of first job that blocked the
worker forever. Can you paste your worker code?
</pre>
</blockquote>
</body>
</html>