I believe you need to supply the '-server' switch at startup to the JVM to be in "server mode". Try dropping that switch, if you're using it.
Personally, I recommend you check out the IBM JDK, too. You can install both and easily switch between them by modifying your JAVA_HOME environment variable. Thanks, --jeff ----- Original Message ----- From: "Hawkins, Keith (Keith)" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Tuesday, December 18, 2001 10:09 AM Subject: RE: Ever increasing heap size with Tomcat 3.2.3 !!! > John, > Thanks for the reply. How do I tell whether I am using the server JVM > or > the client JVM you mentioned? > Thanks, > Keith > > -----Original Message----- > From: John Freeborg [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, December 18, 2001 1:08 PM > To: Tomcat Users List > Subject: RE: Ever increasing heap size with Tomcat 3.2.3 !!! > > > Which JVM are you using? > > On Windows 2K w/ SP2 I found that the Sun JDK 1.3.1 server hotspot JVM > crashed and burned running Tomcat 4.0.1 this way within 24 hours easily. > A few others emailed me about it also. > > Switching to the Sun JDK 1.3.1 client hotspot JVM magically fixed this. > Now my server runs for weeks without crashing. > > Might be the same issue with Tomcat 3.2.3 - try it. I was going to try > an IBM JDK also, but never got around to it once I had it working. > > - John > > -----Original Message----- > From: Randy Layman [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, December 18, 2001 11:07 AM > To: Tomcat Users List > Subject: RE: Ever increasing heap size with Tomcat 3.2.3 !!! > > > > > > -----Original Message----- > > From: Hawkins, Keith (Keith) [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, December 18, 2001 12:34 PM > > To: [EMAIL PROTECTED]; tomcat-user > > Subject: Ever increasing heap size with Tomcat 3.2.3 !!! > > > > > > > > Are there known issues with Tomcat and heap size?? > > No. > > > > Doing a web search revealed numerous posts with people having similar > > problems so I believe there is a problem. The standard > > response these > > people receive is to increase the heap size via -Xmx But that seems > > like a band-aid rather than a real solution. That just delays the > > inevitable. > > The problem is always that they are holding onto memory that they don't > realize they are holding on to, or are expecting to be garbage collected > but > can't for whatever reason. > > Here are some suggestions on where to look: > 1. Don't use class variables in servlets or JSPs > 2. Be careful with sessions. Setting the inactive timeout to > nothing allows the sessions to stay around until the server is reset, > and > sessions last for some time after the last request > 3. Understand that it anything has a reference to an object > (list, > map, array) then it can't be garbage collected > 4. Use a program like OptimizeIT! to find your memory leak > > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
