We run timcat 5.5.x (mod_jk/Apache 2.0) in production on Gentoo/Java 5.0. I can't say that we've experienced any instability in tomcat along the lines your describing.
-Mark On Mar 12, 2007, at 10:48 AM, Richard Jones wrote: > Hi Graham, > >>> Tomcat has always, IMO, been mildly unstable, and we've been >>> having some >>> problems recently that have encouraged me to look at other >>> containers. >> >> Any specific issues that you can / care to share? > > It's nothing too interesting, I don't think, to be honest, which is > why > I didn't elaborate. Basically, our web service layer is occasionally > suffering timeouts when communicating with a tomcat instance that has > been inactive for a time. We suspected that this was to do with > either > > - tomcat unloading useful info from its cache > - tomcat memory being written out to disk, and then being read back > in again > > The tomcat list hasn't been at all helpful, so I hope that this means > that it's the latter, and not really a tomcat problem at all. I'm > still > trying to get an environment set up where I can actually test what's > going on with the paging. > >>> It was alleged on some site or other (i.e. I googled >>> for 5 minutes, and that was what I found - not a scientific >>> approach) >>> that Tomcat and Resin are the fastest of the containers (which is a >>> significant criteria). >> >> Similar research that I've conducted hasn't been quite so >> favourable for >> Tomcat. > > Quite so. A further 10 minutes of googling indicated that Jetty > was the > best, Tomcat was the best and Resin was the best, and that they > were all > also the worst. Conclusive ;) The overall sense I got was that Jetty > might be marginally better. > >> Then again, it may also depend on what criteria you are using - >> vanilla Tomcat doesn't tend to scale to well with multiple >> connections. >> In such cases, you want to look at something that either has NIO >> (Jetty, >> Grizzly - the refitted Tomcat that is part of Glassfish), or use >> the APR >> with Tomcat (but then if you are having issues with Tomcat, I >> can't see >> that they are going to be helped much by including native code!) > > That makes the possibility of using Jetty seem quite attractive, > though. > If this problem persists (we have done some network tweaking which > might have had a knock on effect), I will try that route next. > > Thanks for your feedback on this, Graham. > > Cheers, > > -- > Richard > ---------------------------------------------------------------------- > -- > Richard Jones | t: +44 (0)20 759 [48614 / 41815] > Web & Database | e: [EMAIL PROTECTED] > Technology Specialist | b: http://chronicles-of- > richard.blogspot.com/ > Imperial College London | > ---------------------------------------------------------------------- > -- > > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > DSpace-tech mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/dspace-tech ~~~~~~~~~~~~~ Mark R. Diggory - DSpace Systems Manager MIT Libraries, Systems and Technology Services Massachusetts Institute of Technology ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
