Re: Jruby/Rails 2/Tomcat 5.5

Lenny, Nick,

Thank you for your assistance.

Lenny, you described my situation almost exactly. The error kept looping in the logs, and I wasn't able to find any more details. I'll apply the patch and see if that helps.

Thank you,

Denny


On 1/23/08 11:03 PM, "Lenny Marks" <lenny@...> wrote:

I also ran into this when I was getting started deploying into
Tomcat. Anytime there was a problem during rails initialization I'd
see that error looping in the logs. Contrary to the 'See the logs for
more details' message I couldn't find any additional logging
information in the server log(catalina.out) or any of the rails log
files. As a quick fix I wound up applying the patch below to rails-
integration to print the stack trace which did show me the underlying
problem which was usually obvious once I could see full stack trace
(In one case it was that I was developing on a Mac which was
shielding some case sensitivity typos in require statements). I could
swear I tried passing the original exception to the (String msg,
Throwable rootCause) constructor of ServletException but that didn't
dump the entire stack trace to the logs.  Anyway, I think there is an
issue with Goldspike swallowing exceptions. I'm guessing the Rails
logging isn't usable before the Rails initialization is complete.


Index: src/main/java/org/jruby/webapp/RailsFactory.java
===================================================================
--- src/main/java/org/jruby/webapp/RailsFactory.java    (revision 877)
+++ src/main/java/org/jruby/webapp/RailsFactory.java    (working copy)
@@ -135,6 +135,7 @@
                  log("Rails init time: " + (System.currentTimeMillis
() - startTime) + "ms");^M
              }^M
          } catch (RaiseException e) {^M
+            e.printStackTrace();^M
              logRubyException("Failed to load Rails", e);^M
              throw new ServletException("Could not load Rails. See
the logs for more details.");^M
          }^M

-lenny

On Jan 23, 2008, at 11:07 PM, Nick Sieger wrote:


---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email




---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email