I’m having an OutOfMemory problem. We’re running a rails 2.0.1 app on
jruby 1.1.1 with MSSQL 2005 via ar-jdbc 0.7.2. The server is a linux
machine running WebSphere 6.1, and goldspike 1.6.1 is the glue between
rails and websphere. We’re using WebSphere’s SQL Server JDBC adapter. I
don’t know what WebSphere’s max heap is set to.
The java stack trace is different every time, and the specific symptoms
vary a bit, but the common component of each server crash is an
OutOfMemoryError and the complete unavailability of our application
the server is restarted. The latest crash (and the first one in our
staging environment) happened after about 4 hours of uptime and heavy
usage by a system test team. And, of course, this happened less than 1/2
hour after I explained to the customer and my manager why this wouldn’t
Obvious things that jump to mind:
- increase -Xmx
- check for heavy session usage (some on the dev team tend to dump too
much into the session) – is there a way to tell Rails or the servlet
context that a session can be emptied?
From watching this list, it has sounded like there aren’t significant
memory leak-type problems in JRuby, and (my inference is) that everyone
else has long-running server processes that aren’t having memory issues,
especially with JRuby 1.1+. Are there any known leaks (and hopefully
workarounds) in JRuby? I found a fairly recent bug report  that
that AR transactions in JRuby leak memory.
In short, has anyone else seen OutOfMemoryErrors with JRuby & Rails? Are
there good tools or techniques for diagnosing the problem?
To unsubscribe from this list, please visit: