ThreadError: deadlock; recursive locking.

[Travis Reeder]

We're seeing a bunch of these errors and I see that we're not the first: https://jira.mongodb.org/browse/RUBY-274

The suggestion on there is to set the :op_timeout, but curious how that would fix it and what it should be set to (or set to nil to disable the timeout?). 

Any help would be appreciated, this is a bad one for us.

[Kyle Banker]

Travis,

Which version of the driver?
Which version of Ruby?
Is your app threaded or no?
If a web-app, which app server?

Thanks,
Kyle

[Travis Reeder]

Hi Kyle, 

Driver: 1.4.1

Ruby 1.9.2p180

There are two threads (main + 1).

Not a web app. 

We tried setting the :op_timeout last night, but the problem came back so that did not fix it. 

[David Cuadrado]

hi Travis,

have you tried this patch? http://pastie.org/2762948

--
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To view this discussion on the web visit https://groups.google.com/d/msg/mongodb-user/-/EShU6mLMGQ0J.
To post to this group, send email to mongod...@googlegroups.com.
To unsubscribe from this group, send email to mongodb-user...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/mongodb-user?hl=en.

--
David Cuadrado

[Travis Reeder]

I haven't tried that yet, wanted to see if we could fix it without modifying Ruby core, but if it's the only way.... Trying now. 

[Travis Reeder]

Quick update: that hack/patch seems to work. They really should put this in ruby core or something.

[Kyle Banker]

Travis,

Thanks for testing the patch. I'll add this to the driver's documentation. If I can, I'm going to try to make the driver more lock-less, which may eliminate the issue altogether.

Kyle