In this case I don't completly agree with you. Through the implementation of a servlet container you can incluence the behaviour of the gc. It depends on how many objects are created by the different containers to complete the same task and how the lifecycle of the created objects is. Given that, the same gc parameters can work good with one container, and can perform bad on another.
Note that I'm not suggesting that tomcat performs better or worse than other containers, just that it is possible that there are differences. > -----Original Message----- > From: Shapira, Yoav [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 28, 2003 6:01 PM > To: Tomcat Users List > Subject: RE: Tomcat STILL freezing - time to look at another > app server? > > GC behavior is not tomcat-specific. It's the JVM that's doing the GC, > and if you have a stop-the-world full GC algorithm triggered, then > everything in the JVM will stop. Again, not related to > tomcat. Bad GC tuning will bite you on every server. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
