Open glebm opened 11 years ago
exaclty same issue on my side: jruby + puma + Rails 3.2.11, journey 1.0.4
Hate to open this back up - but I just had the same issue on Rails 4.2.7, Puma 3.10.0, jRuby 9.1.10.0.
Simply restarting my app server fixed it.
Attached is a backtrace: https://gist.github.com/TheKidCoder/5f181fea58480fe30eb3689391afc4e1
When running on puma, around 10% (ymmv) of the requests fail with the following exception:
Full backtrace here: https://gist.github.com/4235007