multithreading - Is it safe to remove Rack::Lock? -

I'm getting this error on a pretty regular basis: Thread error: deadlock; Recursive locking I have read that if the Unicorn (which I am) rack :: lock is not required by adding it to config.middleware.delete "rack :: lock" I can remove it. Application.rb.

Does anyone have the opinion that whether the rack is safe to remove: lock from my production app?

For reference, general trace:

  ... dor / bundle / ruby ​​/ 2.0.0 / gem / rack -1.4.5 / Lib /rack/lock.rb:14:in `lock '... door / bundle / ruby ​​/ 2.0.0 / gem / rack-1.4.5 / leeb / rack / lock RB: 14: In 'call' ... bundle / ruby ​​/ 2.0.0/gems/rack-1.4.5/lib/rack/deflater.rb:13:in 'call' ... / bundle / ruby ​​/ 2.0 .0 / gem / rack-ssl-1.3.3 / lib / rack /ssl.rb:27:in 'call' ... by / 2.0.0 / gem / rack-cache -1.2 / lib / rack / cache / Reference. RB: 136: In 'forwarded' ... by / 2.0.0 / gem /rack-cache-1.2/lib/rack/cache/context.rburday45:in 'fetch' ... by / 2.0.0 / gemstone / Rack-cache-1.2 / lib / rack / cache / context.rb: 185: in 'Lookup' ... / 2.0.0 / gem / rack-cache -1.2 / leeb / rack / cache / reference. RB: 66: In 'call!' ... by / 2.0.0 / gem / rack-cache -1.2 / lib / rack / cache / reference. `Call 'in RB: 51: / 2.0.0 / Gemstone / Unicorn- 4.6.3 / Leib / Unicorn / Http_server.rb: 552: In' process_client '... icorn-worker-killer-0.4.2 In the 'process_client' ... / 2.0 / 2.0 / ... Gems / Unicorn- 4.6.3 / lib / Unicorn / http_server.rb: 632: 'worker_loop' in ... by / 2.0.0 / gemstone / unicorn- 4.6.3 / lib / unicorn / http_server.rb: 500: ` In 'spawn_missing_workers' ... by / 2.0.0 / gemstone / Unicorn- 4.6.3 / lib / Unicorn / http_server.rb: 142: `Initiate'  

< Div class = "post-text" itemprop = "text">

OK, I have config.middlewa Re.delete removed "rack :: lock" Around a week ago and all are working fine. The error has ended and there is no problem removing rack :: lock.