We are using the Ruby beanstalk-client library, however this appears to be doing the right thing, when we set the TTR value in a producer and then read it back off of the job in a consumer we see very different values if an integer >4294 is used. Has anyone seen this before? are we doing something silly? is it a overflow/wrapping issue? Here are some examples of the TTR input > output values we are seeing...
4295 > 0 5000 > 705 21600 > 125 How would we go about fixing this to work with long TTR values such as 6 hours. Thanks, Andy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "beanstalk-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/beanstalk-talk?hl=en -~----------~----~----~----~------~----~------~--~---
