Hi, sorry for the delay, that's just to confirm that loading JRuby trunk + Goldspike trunk on Tomcat 5.5 really does fix all my leak problems! I indeed had leaks with Tomcat 6 -could be linked to the common pool lib (not sure). I have no big clues, but I think I also got leaks with Glassfish v2 and possibly Jetty. I had little time to investigate on that and memory leaks are a hassle to debug, so sorry for not having more clues. The one thing that's sure is that Tomcat 5.5 + last JRuby really does it. So you'll be warned!
Raphaël Valyi. On 8/7/07, Raphaël Valyi <[EMAIL PROTECTED]> wrote: > > Guys I think I got a crash even with a recent JRuby and Jetty again. I > didn't report it cause I can't understand the cause yet, no time to > investigate. Upgrading JRuby and Goldspike and using Jetty made me use > less memory. Also I tried a lot of load test and saw a stabilization of the > memory consumption. Still, my Jetty went down recently when I tried the same > on prod again. I mean that could be something else, I had no time to > investigate on this unfortunately (spare time project with little spare > time), but I wouldn't be so self assured there is nothing wrong. > > Also, as for Tomcat 6, somebody reported a know issue with Tomcat 6 and > Jakarta Common Pool which is the pooling system for the JRuby runtimes. > That might explain that specific crash, but obvioulsy we should gather more > info on the stability of our JRuby on Rails app. I mean I never had such a > problem in dev mode over short dev hours, neither with webrick, and that > might explain why nobody is reporting such problems. I would like to hear > more about long running JRuby on Rails apps. > > Good luck, > > Raphaël Valyi. > > On 8/7/07, Charles Oliver Nutter <[EMAIL PROTECTED]> wrote: > > > > waynebaswell wrote: > > > I am experiencing the same problem: we've deployed a Jruby/Rails app > > to > > > Tomcat 6 and it crashes Tomcat within 24 hours...nothing abnormal > > showing up > > > in the logs. Anyone else seen this? > > > > Raphael's problems were solved by updating everything to trunk versions. > > Not ideal, obviously, but is that something you can try? > > > > We're going to push out a 1.0.1 JRuby release followed by a couple > > JRuby-extras project releases soon. > > > > - Charlie > > > > --------------------------------------------------------------------- > > To unsubscribe from this list please visit: > > > > http://xircles.codehaus.org/manage_email > > > > >
