I think I figured this out *facepalm* We have multiple "production" environments, all of which point to the same Redis URI.
The workers on each environment were polling the same storage for work, getting different results via ActiveRecord (because of their different data!), and essentially just doing their job. So, looks like the issue was purely in our implementation. Thanks again for the help! E On Thursday, January 24, 2013 5:42:07 PM UTC-5, John Mettraux wrote: > > > On Thu, Jan 24, 2013 at 02:37:47PM -0800, EJI wrote: > > > > I've produced a similar exception, but it bombed out on a different line > > (prior to the one I originally posted) for another ActiveRecord lookup > -- > > it would have been looking for the same record for all tests, so one > time > > it found it, and one time it didn't. This is what drew me more to > looking > > into how ActiveRecord is utilized. Perhaps I shouldn't be utilizing it > at > > all from within StorageParticipant on_event? > > Hello Eji, > > is the record created in some process/thread and then is the participant > attempting to locate it from another process/thread. Could be a different > connection which has a slightly different view of the records in the db... > > The record is created in connection A, and the participant, with > connection > B, is meant to find it immediately... > > Does that match your setup? > > Cheers, > > -- > John Mettraux - http://lambda.io/jmettraux > > -- -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en
