You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a Rails 3.2.14 application that's using http streaming that was working fine with the combination of:
JDK 1.6
JRuby 1.7.4
on CentOS 6.4.
We wanted to upgrade to JDK 1.7, which then resulted in a large number of FiberError exceptions in our local development (Mac OSX 10.9). Upgrading to the latest JRuby resolved the problem in our local environment, but not in our CentOS 6.4 environment.
The code in question is essentially this:
class SomeController < ApplicationController
...
def index
...
render stream: true
end
end
Commenting out the "render stream: true" makes the FiberErrors and related ThreadErrors disappear, but we'd ideally like to keep streaming on if possible.
We're seeing the following errors with http streaming turned on:
As of
- jruby/jruby#1243 and
- jruby/jruby#1789,
there might be a regression in JRuby 1.7.x, while JRuby 9000 works
just fine.
(Side note: please don't branch off this commit as long there is
an Work-In-Progress tag. I will force push some minor changes
when fiddleing with Travis...)
dmke
added a commit
to slim-template/slim
that referenced
this issue
Dec 30, 2014
Sorry there has been no interaction from us ever in this bug and I feel guilty in closing this one...If it is still a problem then please re-open. I guess we probably need a more concrete way of reproducing this (bonus if it is minimal) to move further on solving it.
I have a Rails 3.2.14 application that's using http streaming that was working fine with the combination of:
JDK 1.6
JRuby 1.7.4
on CentOS 6.4.
We wanted to upgrade to JDK 1.7, which then resulted in a large number of FiberError exceptions in our local development (Mac OSX 10.9). Upgrading to the latest JRuby resolved the problem in our local environment, but not in our CentOS 6.4 environment.
The code in question is essentially this:
Commenting out the "render stream: true" makes the FiberErrors and related ThreadErrors disappear, but we'd ideally like to keep streaming on if possible.
We're seeing the following errors with http streaming turned on:
I'm curious to see if anyone else has experienced similar issues, and what the fix might be for this. Thanks!
The text was updated successfully, but these errors were encountered: