I had the same problem, increased memory up to 512 and got rid of it.
But it seemd kind of obvious to me that tomcat 4.1.3 was taking way more memory than 
4.0.3, for example an application that normally takes 40 - 60 mb was taking 400mb of 
memory under load, and it did not seem to release the memory unless I killed the 
java.exe process. All my problems came as I was stress-testing the application. I'm 
testing version 4.1.5 right now, I'll let you know if there is any difference. 

-reynir


 

> -----Original Message-----
> From: Victor Popiol [mailto:[EMAIL PROTECTED]]
> Sent: 21. júní 2002 15:44
> To: Tomcat Users List
> Subject: RE: Tomcat 4 performance issues - Trying Tomcat 4.1.3 Beta
> 
> 
> More details:
> 
> Server
> Compaq Single Processor 512 MB RAM
> Windows 2K
> 
> Tomcat
> - Tomcat 4.1.3 Beta, binary distribution running as a service 
> and using Tomcat 4.0's isapi_redirector.dll to interface with IIS
> - Using Ajp3Processor with IIS
> - Runs as an NT Service
> - JVM parametes: "-Xrs" "-Xincgc" "-Xms128m" "-Xmx256m"
> 
> 
> Application
> - Struts
> - Lots of JSP's using I18N and custom tags
> - Database server is Oracle 8.1.7
> - # requests/day: 7,750
> 
> Thanks
> Victor
> 
> 
> -----Original Message-----
> From: Remy Maucherat [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 21, 2002 9:46 AM
> To: Tomcat Users List
> Subject: Re: Tomcat 4 performance issues - Trying Tomcat 4.1.3 Beta
> 
> 
> Victor Popiol wrote:
> > I installed Tomcat 4.1.3 beta. Took a while to configure 
> because the hidden issue with the user vs username parameter 
> in the datasource definition.
> > 
> > After it has been running for a day, it died. Looking at 
> the logs I found the following:
> > 
> > java.lang.OutOfMemoryError
> >     <<no stack trace available>>
> > java.lang.OutOfMemoryError
> >     <<no stack trace available>>
> > java.lang.OutOfMemoryError
> >     <<no stack trace available>>
> > java.lang.OutOfMemoryError
> >     <<no stack trace available>>
> > 
> > Any idea of components leaking memory?
> 
> Without any additional details, I can't really help.
> 
> A bug which could cause this has been fixed after 4.1.3:
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9715
> 
> This bug was also present in TC 4.0.x, though.
> 
> Remy
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: 
> <mailto:[EMAIL PROTECTED]>
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: 
> <mailto:[EMAIL PROTECTED]>
> 
> 

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to