Tuesday, September 26, 2017
Environment: Jruby 1.7.25 on Jetty. Rails 3.2.11. We have been facing a random issue where some of the route objects stored in the Journey Gem get corrupted. After that, the corrupted routes/endpoints keep on throwing an empty string or nil for all of the future hits, and blows up our application. The only solution is to restart the server.
The thread unsafety of the Journey gem is a known issue, see these:
https://github.com/rails/rails/issues/23699
https://github.com/rails/rails/pull/27647
I have two questions:
Could the journey objects which are storing routes get garbage collected on the JVM? Thats the only way I see, why routes could get corrupted because in a live highly concurrent site regeneration of the Journey related objects will be prone to race conditions.
Has anyone similar experience in seeing the journey gem getting corrupted?
Thanks,
Samar
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/1f529962-b390-45ed-9d3b-c2743c1e66de%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment