Work from home and pocket more money in a month than most people make all year

What I'm offering is a realistic plan that can help you make an extra
$500 to $5,000 a month, right now, and then we'll go from there
depending on what you want to do.If you're happy with that amount you
won't really fit into my "big picture" ... but that's fine.Sign up(use
only your name and email,US,CA,UK Only) to create your account and be
a partner with Paul.
http://alturl.com/nnh7
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "beanstalk-talk" group.
To post to this group, send email to beanstalk-talk@...
To unsubscribe from this group, send email to beanstalk-talk+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Digital Hotcakes Vol1

ruby client bug

Hi,
Found a bug in ruby client lib. It leaks connections when reserve-with- 
timeout.
connection.rb line 329:
     def call_wrap(c, *args)
       self.last_conn = c
       c.send(*args)
     rescue EOFError, Errno::ECONNRESET, Errno::EPIPE,  
UnexpectedResponse => ex
       self.remove(c)
       raise ex
     end

Since TimedOut is defined as a subclass of UnexpectedResponse, good  
connections will be removed from  <at> connections when TimedOut thus leak  
connections.

Fix:
change line 343 to:
self.remove(c) unless ex.is_a?(TimedOut)

best wishes
Linan Wang

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "beanstalk-talk" group.
To post to this group, send email to beanstalk-talk@...
To unsubscribe from this group, send email to beanstalk-talk+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: ruby client bug

A patch is attached.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "beanstalk-talk" group.
To post to this group, send email to beanstalk-talk@...
To unsubscribe from this group, send email to beanstalk-talk+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

On 10 Sep 2009, at 00:57, Linan Wang wrote:

> Hi,
> Found a bug in ruby client lib. It leaks connections when reserve- 
> with-timeout.
> connection.rb line 329:
>    def call_wrap(c, *args)
>      self.last_conn = c
>      c.send(*args)
>    rescue EOFError, Errno::ECONNRESET, Errno::EPIPE,  
> UnexpectedResponse => ex
>      self.remove(c)
>      raise ex
>    end
>
> Since TimedOut is defined as a subclass of UnexpectedResponse, good  
> connections will be removed from  <at> connections when TimedOut thus  
> leak connections.
>
> Fix:
> change line 343 to:
> self.remove(c) unless ex.is_a?(TimedOut)
>
> best wishes
> Linan Wang

ruby client "peek_delayed" not returning delayed jobs

via the .stats method i can see that i have 6 delayed jobs, but
the .peek_delayed method returns nil.  how might i figure out what
these jobs are?  thanks.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "beanstalk-talk" group.
To post to this group, send email to beanstalk-talk@...
To unsubscribe from this group, send email to beanstalk-talk+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

does beanstalkd have any known race conditions?

i'm using beanstalkd to feed about 4.5mm jobs a day to 200 worker
processes and i see roughly 80 results per day that have performed
duplicate/redundant work with nearly identical time stamps, suggesting
to me that beanstalk might be serving the same job to two workers a la
race condition, or these jobs when put into the queue got duped.

has anybody else seen this, or might it be a known issue?

thanks.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "beanstalk-talk" group.
To post to this group, send email to beanstalk-talk@...
To unsubscribe from this group, send email to beanstalk-talk+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: does beanstalkd have any known race conditions?

On Sep 10, 3:56 pm, trak3r <tra...@...> wrote:
> i'm using beanstalkd to feed about 4.5mm jobs a day to 200 worker
> processes and i see roughly 80 results per day that have performed
> duplicate/redundant work with nearly identical time stamps, suggesting
> to me that beanstalk might be serving the same job to two workers a la
> race condition, or these jobs when put into the queue got duped.
>
> has anybody else seen this, or might it be a known issue?

  Your job will be revoked and handed to another worker if you take
longer than the ttr to delete it.  You should see an error in deleting
the job when this happens.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "beanstalk-talk" group.
To post to this group, send email to beanstalk-talk@...
To unsubscribe from this group, send email to beanstalk-talk+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: does beanstalkd have any known race conditions?

On Sep 11, 2:32 am, Dustin <dsalli...@...> wrote:
>   Your job will be revoked and handed to another worker if you take
> longer than the ttr to delete it.  You should see an error in deleting
> the job when this happens.

Yup, but I'm seeing no such errors, and the fact that the timestamps
are fractions of a second apart strongly suggests that two workers are
processing the same job at the same time, not what I would expect if
one worker had timed out while requesting the job.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "beanstalk-talk" group.
To post to this group, send email to beanstalk-talk@...
To unsubscribe from this group, send email to beanstalk-talk+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: ruby client "peek_delayed" not returning delayed jobs

here's a quick console session showing what I mean:

$ script/console production
Loading production environment (Rails 2.3.2)
>> beanstalk = AsyncObserver::Queue.queue
=> #<Beanstalk::Pool:0x2b037a599658  <at> default_tube=nil,  <at> addrs=
["X.X.X.X:X"],  <at> watch_list=["default"],  <at> connections=
{"X.X.X.X:X"=>#<Beanstalk::Connection:0x2b037a599518
 <at> socket=#<TCPSocket:0x2b037a599388>,  <at> addr="X.X.X.X:X",
 <at> waiting=false,  <at> watch_list=["default"],  <at> last_used="default">}>
>> beanstalk.stats['current-jobs-delayed']
=> 13
>> beanstalk.peek_delayed
=> nil

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "beanstalk-talk" group.
To post to this group, send email to beanstalk-talk@...
To unsubscribe from this group, send email to beanstalk-talk+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: does beanstalkd have any known race conditions?

On Sep 11, 7:36 am, trak3r <tra...@...> wrote:
> Yup, but I'm seeing no such errors, and the fact that the timestamps
> are fractions of a second apart strongly suggests that two workers are
> processing the same job at the same time, not what I would expect if
> one worker had timed out while requesting the job.

The first thing that came to mind here was the possibility of the
first worker being blocked by a database lock for longer than the
beanstalk ttr. Then another worker gets the job and the lock happens
to clear and both workers end up committing their transactions.

Not sure this is the case here but it sounds plausible.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "beanstalk-talk" group.
To post to this group, send email to beanstalk-talk@...
To unsubscribe from this group, send email to beanstalk-talk+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en
-~----------~----~----~----~------~----~------~--~---