|
[
Permalink
| « Hide
]
Charles Oliver Nutter added a comment - 04/Jan/08 09:24 PM
Hmmm, ugly. Can you provide a sample app (great) or WAR file (ok) and instructions on how to reproduce? There are others using JRuby + Rails 2 and having no issues like this.
Charles, well that is encouraging (your comment).
I can work on getting you something this weekend (an app). Well, I built I did a really simple Rails 2.0 app off of trunk & latest Goldspike and I was unable to reproduce. So that is good, but my real app is still doing (a little more complicated). I will try messing with it a bit. Rather than posting it here (the app) can I share it with one person on the Goldspike team to help me?
If you'd like to send it through to me I'll give it a go and see if I can see what's going on.
I can be reached at r.egglestone@auckland.ac.nz We had an issue much earlier where exceptions would be thrown, but the Rails exception handling was failing, so we got empty responses. It's possible that something similar is happening with Rails 2. I've made some changes to Goldspike (r868), and I'm not seeing the empty pages anymore.
Could you please try it out with the latest snapshot? The changes made were: Robert - great news - I'll try it right now & report back my findings.
The fix resolved the issue. The checkin has in issue in that I think the fix depends on 1.0.3, but the build script was pointed at 1.0.1. Maven had 1.0.3, but Ant had 1.0.1. I patched that locally and got it to build. Then I ran it and I no longer saw the Random Empty Response with Rails 2.0 behavior.
I am seeing: 6-Jan-2008 1:05:53 AM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet files threw exception
java.lang.NoSuchMethodError: org.jruby.RubyIO.closed()Lorg/jruby/RubyBoolean;
at org.jruby.webapp.RailsServlet.dispatchRequest(RailsServlet.java:108)
at org.jruby.webapp.RailsServlet.serviceRequest(RailsServlet.java:58)
at org.jruby.webapp.RailsServlet.service(RailsServlet.java:42)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:445)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:343)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:292)
at org.jruby.webapp.FileServlet.service(FileServlet.java:208)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:584)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
in the Tomcat logs now so it looks like there is a (hopefully small) new problem. The attached build.xml will fix the currently broken build.
Thanks, I've updated build.xml in the repository.
By the way, that stack trace is caused by running with JRuby < 1.0.3.
It needs to be both built and run with 1.0.3, to do this add this line to config/warble.rb: And then put the jruby-complete-1.0.3 and goldspike-1.4-snapshot jars in the lib directory. Robert's fix resolved the issue.
Some notes from an email between Robert and I that may be useful. I'll update the wiki with some of the other bits. _To identify the problem, after duplicating the bug using Jetty and Thanks for the wiki updates Mike!
I'm having the same issue (HTTP 200, Content-length:0) with Tomcat and builds from latest JRuby (5816) and Goldspike (886). It appears to not be quite fixed.
Cancel that. My warble reverted back to an old goldspike...
If you drop the desired Goldspike and JRuby jars in webapp/lib, and then add this line to config/warbler.rb, it'll always use them rather than the version bundled with the current Warbler gem:
config.java_libs.reject! {|lib| lib =~ /jruby-complete|goldspike/ } |
|||||||||||||||||||||||||||||||||||||||||||||||||