Particularly because it wasn't a 'friendly' reboot. Something may have gotten corrupted, it's not unheard of. Just for the heck of it, you could re-install the JDK and the Tomcat binaries (while keeping your server.xml and webapps directories safely backed up BEFORE you do any of that). > -----Original Message----- > From: Ralph Einfeldt [mailto:[EMAIL PROTECTED] > Sent: Friday, September 19, 2003 9:05 AM > To: Tomcat Users List > Subject: RE: Urgent! Cannot start Tomcat - java.lang.OutOfMemoryError > > > I think it's not the right time to think about optimizing. > > If tomcat isn't even starting, I don't think that the > problem is a 'normal' memory leak especially if the server > has run before. I think that something has changed through > the reboot. > > > -----Original Message----- > > From: Denise Mangano [mailto:[EMAIL PROTECTED] > > Sent: Friday, September 19, 2003 3:59 PM > > To: Tomcat Users List > > Subject: RE: Urgent! Cannot start Tomcat - > java.lang.OutOfMemoryError > > > > I did not change ulimit at all... Actually I did not change > > anything in > > server.xml besides making the configurations for mod_jk. Are > > there any > > settings I should consider changing? Perhaps, you can point me to a > > good resource where I can learn about optimizing? > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
