manager outofmemory exception
I know this is a very common issue but i want to be sure about it. I have 5 tomcats on a 8Gb RAM machine. The number of applications installed on tomcats are 5 to 15. All the tomcat run with -Xms128M -Xmx512M but the manager aplication never show JVM memory higger than 128 This is the JVM memory state for the tomcat with 15 application: Free memory: 73.94 MB Total memory: 128.62 MB Max memory: 510.37 MB What i don't understand is that I sometimes get OutOfMemoryException when i upload new aplitications to the tomcat using the manager. I Profiled my aplication and i don't have any memory issue. Is this a manager bug? Why the Total Memory is never higger than 128 MB but I get OutOfMemoryExceptions? Regards, Enrique. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: manager outofmemory exception
From: Enrique Rodriguez [mailto:[EMAIL PROTECTED] What i don't understand is that I sometimes get OutOfMemoryException when i upload new aplitications to the tomcat using the manager. I Profiled my aplication and i don't have any memory issue. Just to check: Did your profiling include looking at PermGen? Is this a manager bug? Why the Total Memory is never higger than 128 MB but I get OutOfMemoryExceptions? Java always loads classes into the permanent generation (PermGen) and never (to my knowledge) reclaims that space, even when you unload classes. So you may be running out of PermGen space. You may wish to increase that. A search on a Tomcat archive for 'Permgen' should give you plenty more information! - Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: manager outofmemory exception
http://jakarta.apache.org/tomcat/faq/memory.html#why -Tim Enrique Rodriguez wrote: I know this is a very common issue but i want to be sure about it. I have 5 tomcats on a 8Gb RAM machine. The number of applications installed on tomcats are 5 to 15. All the tomcat run with -Xms128M -Xmx512M but the manager aplication never show JVM memory higger than 128 This is the JVM memory state for the tomcat with 15 application: Free memory: 73.94 MB Total memory: 128.62 MB Max memory: 510.37 MB What i don't understand is that I sometimes get OutOfMemoryException when i upload new aplitications to the tomcat using the manager. I Profiled my aplication and i don't have any memory issue. Is this a manager bug? Why the Total Memory is never higger than 128 MB but I get OutOfMemoryExceptions? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: manager outofmemory exception
From: Enrique Rodriguez [mailto:[EMAIL PROTECTED] Subject: manager outofmemory exception What i don't understand is that I sometimes get OutOfMemoryException when i upload new aplitications to the tomcat using the manager. Search the archives - this comes up frequently. Assuming you're using a HotSpot JVM (Sun 1.4 or later), you're probably running out of PermGen space, where all the instances of java.lang.Class (among other things) are stored. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: manager outofmemory exception
Thanks, i will try to set maxpermsize to 256m Regards, Enrique. El mar, 11-10-2005 a las 17:11 +0100, Peter Crowther escribió: From: Enrique Rodriguez [mailto:[EMAIL PROTECTED] What i don't understand is that I sometimes get OutOfMemoryException when i upload new aplitications to the tomcat using the manager. I Profiled my aplication and i don't have any memory issue. Just to check: Did your profiling include looking at PermGen? Is this a manager bug? Why the Total Memory is never higger than 128 MB but I get OutOfMemoryExceptions? Java always loads classes into the permanent generation (PermGen) and never (to my knowledge) reclaims that space, even when you unload classes. So you may be running out of PermGen space. You may wish to increase that. A search on a Tomcat archive for 'Permgen' should give you plenty more information! - Peter - 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]
Please help with PermGen OutOfMemory error
After many webapp installs, I get this in my tomcat logs... Exception in thread ContainerBackgroundProcessor[StandardEngine[Catalina]] java.lang.OutOfMemory Error: PermGen space MaxPermSize=128m, but the errors still happen. I understand that this comes from apps not releasing all their resources. How do I track down what part of my app is leaving these resources behind? I'm hoping for pointers to tools/articles/blog entries - anything that'll let me isolate this problem (hopefully to a part of my code that I can actually fix as opposed to third party code I have no control over). thx andy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Please help with PermGen OutOfMemory error
What is the version of your tomcat? 5.5 supposed to have resolved this issue by flush reflection cache when undeploy your web app. -Original Message- From: Andy Kriger [mailto:[EMAIL PROTECTED] Sent: June 27, 2005 12:12 PM To: tomcat-user@jakarta.apache.org Subject: Please help with PermGen OutOfMemory error After many webapp installs, I get this in my tomcat logs... Exception in thread ContainerBackgroundProcessor[StandardEngine[Catalina]] java.lang.OutOfMemory Error: PermGen space MaxPermSize=128m, but the errors still happen. I understand that this comes from apps not releasing all their resources. How do I track down what part of my app is leaving these resources behind? I'm hoping for pointers to tools/articles/blog entries - anything that'll let me isolate this problem (hopefully to a part of my code that I can actually fix as opposed to third party code I have no control over). thx andy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] !DSPAM:42c02542251611437718752!
Re: Please help with PermGen OutOfMemory error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Phillip Qin wrote: What is the version of your tomcat? 5.5 supposed to have resolved this issue by flush reflection cache when undeploy your web app. I get this with 5.5.9, using jdk 1.5, under Solaris 8, when I copy my new beehive-based webapp into my webapps directory. After about 5-8 new versions within a few hours then I get this error and have to restart tomcat. - -- Love is mutual self-giving that ends in self-recovery. Fulton Sheen James Black[EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCwDZhikQgpVn8xrARAmGqAJ90O/O0HFgB6cCL/PvpcqOldhoFPQCeJ60A kPBnA55zhnUmNtiNp6z1iqU= =s7n+ -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Please help with PermGen OutOfMemory error
I did see this issue happened with my tomcat 4.1/5.0. After I upgraded to 5.5, I have encountered any outofmemory even after 100 hundreds deployments. Does your web app use struts? You can always clean up resource by adding Introspector.flushCaches(); in your context listener's contextDestroyed method. Otherwise, you will have to go through your web app carefully to find out if there is any memory leak. -Original Message- From: James Black [mailto:[EMAIL PROTECTED] Sent: June 27, 2005 1:25 PM To: Tomcat Users List Subject: Re: Please help with PermGen OutOfMemory error -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Phillip Qin wrote: What is the version of your tomcat? 5.5 supposed to have resolved this issue by flush reflection cache when undeploy your web app. I get this with 5.5.9, using jdk 1.5, under Solaris 8, when I copy my new beehive-based webapp into my webapps directory. After about 5-8 new versions within a few hours then I get this error and have to restart tomcat. - -- Love is mutual self-giving that ends in self-recovery. Fulton Sheen James Black[EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCwDZhikQgpVn8xrARAmGqAJ90O/O0HFgB6cCL/PvpcqOldhoFPQCeJ60A kPBnA55zhnUmNtiNp6z1iqU= =s7n+ -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] !DSPAM:42c03666260791431712512!
Re: Please help with PermGen OutOfMemory error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Phillip Qin wrote: I did see this issue happened with my tomcat 4.1/5.0. After I upgraded to 5.5, I have encountered any outofmemory even after 100 hundreds deployments. Does your web app use struts? You can always clean up resource by adding Introspector.flushCaches(); in your context listener's contextDestroyed method. Otherwise, you will have to go through your web app carefully to find out if there is any memory leak. Struts is used in my beehive-based project (http://incubator.apache.org/beehive), but I will need to check if there is some memory leak otherwise. Thanx. - -- Love is mutual self-giving that ends in self-recovery. Fulton Sheen James Black[EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCwEduikQgpVn8xrARAooaAJsEjG6T/a52rsNyIQjIPbbOP7nm7ACfepMP ukLUqtHP8YY5mkK41AEdcFk= =lOrA -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Please help with PermGen OutOfMemory error
As per tools - I think you can use JMeter. It gives u some pretty useful graphs and analysis. -Anoop On 6/27/05, James Black [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Phillip Qin wrote: I did see this issue happened with my tomcat 4.1/5.0. After I upgraded to 5.5, I have encountered any outofmemory even after 100 hundreds deployments. Does your web app use struts? You can always clean up resource by adding Introspector.flushCaches(); in your context listener's contextDestroyed method. Otherwise, you will have to go through your web app carefully to find out if there is any memory leak. Struts is used in my beehive-based project (http://incubator.apache.org/beehive), but I will need to check if there is some memory leak otherwise. Thanx. - -- Love is mutual self-giving that ends in self-recovery. Fulton Sheen James Black[EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCwEduikQgpVn8xrARAooaAJsEjG6T/a52rsNyIQjIPbbOP7nm7ACfepMP ukLUqtHP8YY5mkK41AEdcFk= =lOrA -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks and best regards, Anoop - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
OutOfMemory on FreeBSD
Hello, I'm trying to find how to send jvm parameters (-Xm128m) to the JVM during tomcat startup. I have an application (openreports) that fails with outofmemory exception intermittently. I have seen some references here and there, but nothing that indicates which tomcat (or java, [or freebsd]) configuration file that I need to touch. Any pointers are appreciated. thanks, lane - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OutOfMemory on FreeBSD
Hey, I guess I can answer my own question! Don't you just love it when that
happens!
The makefile for tomcat5 on FreeBSD doesn't give the option to add additional
parameters. There is probably a better way to do this than to hard-code more
variables, but I'm not sure how to do it. So for anyone else who runs into
OutOfMemory exceptions on FreeBSD or the dreaded Can't connect to X DISPLAY
error, make these changes to /usr/ports/www/jakarta-tomcat5/Makefile:
In the do-install target:
change:
-e /%%JAVA_ARGS%%/s//\-Dcatalina.home=${APP_HOME:S/\//\\\//g}\,/g \
to:
-e /%%JAVA_ARGS%%/s//\-Djava.awt.headless=true\,\-Xms128m\,\-Xmx256m\,
\-Dcatalina.home=${APP_HOME:S/\//\\\//g}\,/g \
then do:
make -DFORCE_PKG_REGISTER do-install
This will overwrite the current tomcat50ctl but will preserve your existing
tomcat installation.
PortMaintainer: Kang Liu - which email address is correct for you? both
[EMAIL PROTECTED] and [EMAIL PROTECTED] appear
in /usr/ports/www/jakarta-tomcat5/Makefile
lane
On Sunday 22 May 2005 16:14, Lane wrote:
Hello,
I'm trying to find how to send jvm parameters (-Xm128m) to the JVM during
tomcat startup. I have an application (openreports) that fails with
outofmemory exception intermittently.
I have seen some references here and there, but nothing that indicates
which tomcat (or java, [or freebsd]) configuration file that I need to
touch.
Any pointers are appreciated.
thanks,
lane
-
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]
Re: OutOfMemory on FreeBSD
On Sun, May 22, 2005 at 04:14:30PM -0500, Lane wrote: : I'm trying to find how to send jvm parameters (-Xm128m) to the JVM during : tomcat startup. I have an application (openreports) that fails with : outofmemory exception intermittently. You can set the environment variable JAVA_OPTS, e.g. export JAVA_OPTS='-Xm128m' Note that this would require writing a wrapper script to call the Tomcat scripts, since it'd be silly to do this by hand all the time. The extra script may sound like a pain, but it actually makes your setup less sensitive to Tomcat upgrades because you won't have to modify anything in the Tomcat tree. -QM -- software -- http://www.brandxdev.net/ tech news -- http://www.RoarNetworX.com/ code scan -- http://www.JxRef.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat 5.0.30 OutOfMemory error
I've done a lot of google surfing on this issue. It would seem this is a known issue. Some people say to raise the heap. In the manager panel, I did that: min=256mb, max=512mp and I gave it 512k stack size (not sure if that's even close enough, in fact, I have no idea what that means). I'm running stress tests on localhost:8080. I'm using the apache HttpClient to rapidly access every known URL in the site I'm exercising: 390 distinct URLs. The database is inmemory (a Hashtable) and HTML is painted by way of Velocity. It's a simple site: no large graphics, etc. When HttpClient fails, I log that a URL was missed. When I fire up 1, 2, 4, 8, or 16 threads, nothing unhappy is noted. When I jump to 32 threads, each running simultaneously, I start to get missed URLS. While it's running, I try to access a page from a browser and get the 500 error and out of memory. The java process is calling up 66,500k of heap so it strikes me that the OutOfMemory issue isn't related to the heap. If I try to place set CATALINA_OPTS= -Xms256m -Xmx512m -Xss512k in catalina.bat, Tomcat won't start at all. I confess, I'm really confused. It strikes me that 32 threads banging away on Tomcat 5 on a 2.5 ghz Athalon box just on localhost shouldn't be all that much stress. I'll greatly appreciate any concrete suggestions available. Thanks Jack - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 5.0.30 OutOfMemory error
From: Jack Park [mailto:[EMAIL PROTECTED] Subject: Tomcat 5.0.30 OutOfMemory error It would be helpful if you told us what OS you're using, along with what version of the JDK you have installed. Did you check your logs for any pertinent diagnostic information? The java process is calling up 66,500k of heap so it strikes me that the OutOfMemory issue isn't related to the heap. Highly likely that it's not complete heap exhaustion. If you've searched the archives at all, you should have found the following: 1) The OutOfMemoryError is a catch-all for exhausting not only the heap, but also pretty much any system resource, such as the number of open files. You need to look at the stack trace in the logs to find out what was being attempted at the time. 2) You can run out of Perm Gen space rather easily in any app server. Look at the JVM documentation and the archives for details. If I try to place set CATALINA_OPTS= -Xms256m -Xmx512m -Xss512k in catalina.bat, Tomcat won't start at all. Exactly what errors are displayed? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 5.0.30 OutOfMemory error
Thanks very much, Chuck. Looking in the server log did, indeed, show an error going on down in my database code. Nice theory, but fixing that changed nothing. Here is a typical error in that log now: 2005-05-15 17:49:29 StandardWrapperValve[TopicMap]: Servlet.service() for servlet TopicMap threw exception java.lang.OutOfMemoryError There are no other statements in the TC log that hint at what was being tried when the error was thrown. It throws hundreds of them. Then, Tomcat seems to die -- that is, it stops using 99% of the cycles in the Windows (XP Pro) task manager, drops to 0, cycles up to 88% then 0 in a slow pulsing fashion -- maybe one cycle every two seconds, with nothing moving in the tomcat console, all the while still tossing OutOfMemoryError messages in its logfile. One experiment I have tried is this. I am running the stress engine in jdk 1.5 and TC in 1.4 -- both on the same box. The only files I open are the 3 for the database, a couple of log files, a couple of velocity macros, and the occasional gif image. I just ran it twice in a row without rebooting TC and with 16 threads. Nothing in my log or TC's log until the end when the results were printed. 208 to 210 thousand milliseconds on the first run and 197 to 199 thousand millis on the second. It's in the middle of a run with 24 threads hitting the server and, thus far, only one connection refused message in each of two threads, and those didn't result in a missed URL (failure after 4 tries). Browsing the site while the test is running remains snappy. The run ended and it took 741 seconds on average for each thread. I upped it to 28 threads -- on the way to 32. Now, the TC log is slowly tossing out OutOfMemoryErrors, I got one while browsing, and my tester is receiving lots of connection refused or 500 errors, and just one missed URL (cave in after 4 tries with a 4-second delay). I think you can see the nonlinearity going on. 16 is right at the edge, 28 puts a foot in the grave, and 32 seems to take out a howitzer and start blasting. I'm at somewhat a loss to understand how this relates to Perm Gen space, or if that's an issue. All of the errors mimic the one I pasted in above, except for the Http response codes shown in the error handler in my test framework, and those are only connection refused or 500 type errors. It certainly doesn't sound like heap exhaustion, but, whatever it is, it seems rather nonlinear, where 16 threads don't provoke any errors, 24 threads show the server stumbling, but not tossing errors, and 28 threads appear to have tickled a sleeping tiger. At 28 threads, the OOM errors are being recorded at a rate of one every 4 or so seconds. Still don't know why inserting heap size info in catalina.bat causes Tomcat to boot, flash something, then close the console before you can read it. Dunno if that helps, but that's the story from this end. I do hope that provokes further ideas. Many thanks. Jack Caldarale, Charles R wrote: From: Jack Park [mailto:[EMAIL PROTECTED] Subject: Tomcat 5.0.30 OutOfMemory error It would be helpful if you told us what OS you're using, along with what version of the JDK you have installed. Did you check your logs for any pertinent diagnostic information? The java process is calling up 66,500k of heap so it strikes me that the OutOfMemory issue isn't related to the heap. Highly likely that it's not complete heap exhaustion. If you've searched the archives at all, you should have found the following: 1) The OutOfMemoryError is a catch-all for exhausting not only the heap, but also pretty much any system resource, such as the number of open files. You need to look at the stack trace in the logs to find out what was being attempted at the time. 2) You can run out of Perm Gen space rather easily in any app server. Look at the JVM documentation and the archives for details. If I try to place set CATALINA_OPTS= -Xms256m -Xmx512m -Xss512k in catalina.bat, Tomcat won't start at all. Exactly what errors are displayed? - Chuck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: OutOfMemory / JMeter / Profiler questions
Thanks Harry for your input. But we just can't do any upgrades to the production environment at this point :( Hopefully soon. Guillaume -Original Message- From: Harry Mantheakis [mailto:[EMAIL PROTECTED] Sent: 03 March 2005 10:45 To: Tomcat Users List Subject: Re: OutOfMemory / JMeter / Profiler questions We've started performance testing one of our REMOTE web apps using JMeter. We're gathering benchmark data before doing further fine tuning. Details: Win2K only have ssh + cygwin access to this remote server JDK 1.4.1_03 Tomcat 4.1.26, running as a service: a.. Use security manager 1 b.. Security policy file D:\Tomcat4\conf\catalina.policy c.. Initial heap 256 d.. Max heap 512 e.. Stack size 256 f.. JVM server I cannot help you with respect to your OOM problems, but I would recommend that you consider upgrading to JVM 1.4.2. You should also be able to migrate your app to TC 5.0.28 without too much grief. You should probably avoid TC 5.5.x for the meantime. JVM 1.4.2 and TC 5.0.28 play well together. Good luck in case! Harry Mantheakis London, UK - 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]
RE: OutOfMemory / JMeter / Profiler questions
Alan, Thanks for your feedback. You got me curious here: Why does/would Tomcat reload sessions after startup? Aren't the sessions destroyed upon Tomcat shutdown? Also, I could only find a $TOMCAT_HOME/work/Standalone/localhost/prti-rpt-engine.2.4.2.b17/SESSIONS.se r, which is NOT the context I have been load testing. Sessions should be serialized per context, shouldn't they? We do not store anything in the session (our test just calls a servlet which generate a PDF report) so I can't see why the sessions would be using so much memory. But I'll definitely keep your idea in mind for other tests. I should hopefully be able to run the same tests on our staging platform and see if we get similar behaviors. Thanks for your inputs. Please keep them coming! Cheers, Guillaume -Original Message- From: Flisch, Alan [mailto:[EMAIL PROTECTED] Sent: 03 March 2005 12:17 To: Tomcat Users List Subject: RE: OutOfMemory / JMeter / Profiler questions You probably have either very large or very many sessions which Tomcat is attempting to reload on startup. Tomcat serialises sessions into files called SESSIONS.ser (in the application directories under the work dir) and then when it is restarted it attempts to reload them all. I presume this behaviour can be turned off. In terms of testing your app, you want to figure out whether you have a memory leak issue with your app, or simply that your max heap size is set too low for the load you are running. To check for memory leaks, you could run jmeter reasonably (although not too hard) excercising as much of your app as you can, repetitively and for an extended period. If it eventually keels over then you may need to investigate memory leaks with a profiler. Another possibility is that you may not be invalidating sessions and they are just being left to expire naturally. This can use up a lot of memory if you aren't careful and I supect is a quite likely source of your problems. Cheers! -Original Message- From: Guillaume Lahitette [mailto:[EMAIL PROTECTED] Sent: 03 March 2005 09:51 To: tomcat-user@jakarta.apache.org Subject: OutOfMemory / JMeter / Profiler questions Hello Tomcat'oids! We've started performance testing one of our REMOTE web apps using JMeter. We're gathering benchmark data before doing further fine tuning. Details: Win2K only have ssh + cygwin access to this remote server JDK 1.4.1_03 Tomcat 4.1.26, running as a service: a.. Use security manager 1 b.. Security policy file D:\Tomcat4\conf\catalina.policy c.. Initial heap 256 d.. Max heap 512 e.. Stack size 256 f.. JVM server Issue: We are getting OutOfMemory errors with very few threads simulated (as low as 5). More problematic, we've seen the OOM just after a Tomcat service restart! From the stack trace below, you can see we get the OOM before any of our code is executed :( Questions: a.. Anyone has seen this behavior upon Tomcat start up? b.. Anything particular to watch for in our JMeter test plan? c.. Would a profiler help? Could it profile a remote Tomcat installation? Any +/- feedback on Eclipse Profiler plug in (http://eclipsecolorer.sourceforge.net/index_profiler.html)? We'll work on gathering more data (e.g. periodic free / allocated memory dumps). Untill then, thank you for sharing your experiences, suggestions, code,...! Cheers, Guillaume javax.servlet.ServletException: Servlet execution threw an exception at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(A pplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.access$000(Applica tionFilterChain.java:98) at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationF ilterChain.java:176) at java.security.AccessController.doPrivileged(Native Method) at org.apache.catalina.core.ApplicationFilterChain.doFilter(Applicati onFilterChain.java:172) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapp erValve.java:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveCon text.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline. java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardConte xtValve.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveCon text.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline. java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2416) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValv e.java:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveCon text.invokeNext(StandardPipeline.java:643
RE: OutOfMemory / JMeter / Profiler questions
Hi, Tomcat always serializes sessions on shutdown and reloads them on startup. This is the default behaviour but can be changed. You are right in thinking that sessions are serialized per context though. Are you using the standard manager or the persistent manager as they are stored differently with the persistent manager. Although you don't store anything in a session, do you perhaps instanciate it? The number of sessions you currently have can be viewed from the manager application. Ta Matt -Original Message- From: Guillaume Lahitette [mailto:[EMAIL PROTECTED] Sent: 04 March 2005 15:15 To: Tomcat Users List Subject: RE: OutOfMemory / JMeter / Profiler questions Alan, Thanks for your feedback. You got me curious here: Why does/would Tomcat reload sessions after startup? Aren't the sessions destroyed upon Tomcat shutdown? Also, I could only find a $TOMCAT_HOME/work/Standalone/localhost/prti-rpt-engine.2.4.2.b17/SESSIONS.se r, which is NOT the context I have been load testing. Sessions should be serialized per context, shouldn't they? We do not store anything in the session (our test just calls a servlet which generate a PDF report) so I can't see why the sessions would be using so much memory. But I'll definitely keep your idea in mind for other tests. I should hopefully be able to run the same tests on our staging platform and see if we get similar behaviors. Thanks for your inputs. Please keep them coming! Cheers, Guillaume -Original Message- From: Flisch, Alan [mailto:[EMAIL PROTECTED] Sent: 03 March 2005 12:17 To: Tomcat Users List Subject: RE: OutOfMemory / JMeter / Profiler questions You probably have either very large or very many sessions which Tomcat is attempting to reload on startup. Tomcat serialises sessions into files called SESSIONS.ser (in the application directories under the work dir) and then when it is restarted it attempts to reload them all. I presume this behaviour can be turned off. In terms of testing your app, you want to figure out whether you have a memory leak issue with your app, or simply that your max heap size is set too low for the load you are running. To check for memory leaks, you could run jmeter reasonably (although not too hard) excercising as much of your app as you can, repetitively and for an extended period. If it eventually keels over then you may need to investigate memory leaks with a profiler. Another possibility is that you may not be invalidating sessions and they are just being left to expire naturally. This can use up a lot of memory if you aren't careful and I supect is a quite likely source of your problems. Cheers! -Original Message- From: Guillaume Lahitette [mailto:[EMAIL PROTECTED] Sent: 03 March 2005 09:51 To: tomcat-user@jakarta.apache.org Subject: OutOfMemory / JMeter / Profiler questions Hello Tomcat'oids! We've started performance testing one of our REMOTE web apps using JMeter. We're gathering benchmark data before doing further fine tuning. Details: Win2K only have ssh + cygwin access to this remote server JDK 1.4.1_03 Tomcat 4.1.26, running as a service: a.. Use security manager 1 b.. Security policy file D:\Tomcat4\conf\catalina.policy c.. Initial heap 256 d.. Max heap 512 e.. Stack size 256 f.. JVM server Issue: We are getting OutOfMemory errors with very few threads simulated (as low as 5). More problematic, we've seen the OOM just after a Tomcat service restart! From the stack trace below, you can see we get the OOM before any of our code is executed :( Questions: a.. Anyone has seen this behavior upon Tomcat start up? b.. Anything particular to watch for in our JMeter test plan? c.. Would a profiler help? Could it profile a remote Tomcat installation? Any +/- feedback on Eclipse Profiler plug in (http://eclipsecolorer.sourceforge.net/index_profiler.html)? We'll work on gathering more data (e.g. periodic free / allocated memory dumps). Untill then, thank you for sharing your experiences, suggestions, code,...! Cheers, Guillaume javax.servlet.ServletException: Servlet execution threw an exception at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(A pplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.access$000(Applica tionFilterChain.java:98) at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationF ilterChain.java:176) at java.security.AccessController.doPrivileged(Native Method) at org.apache.catalina.core.ApplicationFilterChain.doFilter(Applicati onFilterChain.java:172) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapp erValve.java:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveCon text.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline. java:480) at org.apache.catalina.core.ContainerBase.invoke
RE: OutOfMemory / JMeter / Profiler questions
Matt, Thanks for your feedbackwhich triggered more questions below! -Original Message- From: Dale, Matt [mailto:[EMAIL PROTECTED] Sent: 04 March 2005 15:26 To: Tomcat Users List Subject: RE: OutOfMemory / JMeter / Profiler questions Hi, Tomcat always serializes sessions on shutdown and reloads them on startup. Can anyone explain what is the usage for this? You can not re-use a session after a restart, can you??? I would think new session ID is created. This is the default behaviour but can be changed. Does anyone know how? If I can't see any usage for this, I'm very keen on disabling it. You are right in thinking that sessions are serialized per context though. Are you using the standard manager or the persistent manager as they are stored differently with the persistent manager. First time I hear about these! I could see a commented PersistentManager in server.xml so I guess I am using the standard manager. Can you tell me more about these? Why/When would I use the PersistentManager? Although you don't store anything in a session, do you perhaps instanciate it? The number of sessions you currently have can be viewed from the manager application. Yes, I've been using it a lot for context stop / start / reload and monitoring the sessions... Cheers, G Ta Matt -Original Message- From: Guillaume Lahitette [mailto:[EMAIL PROTECTED] Sent: 04 March 2005 15:15 To: Tomcat Users List Subject: RE: OutOfMemory / JMeter / Profiler questions Alan, Thanks for your feedback. You got me curious here: Why does/would Tomcat reload sessions after startup? Aren't the sessions destroyed upon Tomcat shutdown? Also, I could only find a $TOMCAT_HOME/work/Standalone/localhost/prti-rpt-engine.2.4.2.b17/S ESSIONS.se r, which is NOT the context I have been load testing. Sessions should be serialized per context, shouldn't they? We do not store anything in the session (our test just calls a servlet which generate a PDF report) so I can't see why the sessions would be using so much memory. But I'll definitely keep your idea in mind for other tests. I should hopefully be able to run the same tests on our staging platform and see if we get similar behaviors. Thanks for your inputs. Please keep them coming! Cheers, Guillaume -Original Message- From: Flisch, Alan [mailto:[EMAIL PROTECTED] Sent: 03 March 2005 12:17 To: Tomcat Users List Subject: RE: OutOfMemory / JMeter / Profiler questions You probably have either very large or very many sessions which Tomcat is attempting to reload on startup. Tomcat serialises sessions into files called SESSIONS.ser (in the application directories under the work dir) and then when it is restarted it attempts to reload them all. I presume this behaviour can be turned off. In terms of testing your app, you want to figure out whether you have a memory leak issue with your app, or simply that your max heap size is set too low for the load you are running. To check for memory leaks, you could run jmeter reasonably (although not too hard) excercising as much of your app as you can, repetitively and for an extended period. If it eventually keels over then you may need to investigate memory leaks with a profiler. Another possibility is that you may not be invalidating sessions and they are just being left to expire naturally. This can use up a lot of memory if you aren't careful and I supect is a quite likely source of your problems. Cheers! -Original Message- From: Guillaume Lahitette [mailto:[EMAIL PROTECTED] Sent: 03 March 2005 09:51 To: tomcat-user@jakarta.apache.org Subject: OutOfMemory / JMeter / Profiler questions Hello Tomcat'oids! We've started performance testing one of our REMOTE web apps using JMeter. We're gathering benchmark data before doing further fine tuning. Details: Win2K only have ssh + cygwin access to this remote server JDK 1.4.1_03 Tomcat 4.1.26, running as a service: a.. Use security manager 1 b.. Security policy file D:\Tomcat4\conf\catalina.policy c.. Initial heap 256 d.. Max heap 512 e.. Stack size 256 f.. JVM server Issue: We are getting OutOfMemory errors with very few threads simulated (as low as 5). More problematic, we've seen the OOM just after a Tomcat service restart! From the stack trace below, you can see we get the OOM before any of our code is executed :( Questions: a.. Anyone has seen this behavior upon Tomcat start up? b.. Anything particular to watch for in our JMeter test plan? c.. Would a profiler help? Could it profile a remote Tomcat installation? Any +/- feedback on Eclipse Profiler plug in (http://eclipsecolorer.sourceforge.net/index_profiler.html)? We'll work on gathering more data (e.g. periodic free / allocated memory dumps). Untill then, thank you for sharing your experiences, suggestions, code
RE: OutOfMemory / JMeter / Profiler questions
Hi, This can be very useful behaviour. It means a tomcat instance can be bounced with only a short loss of service to the users. The sessions CAN be reused after a restart. Information on the session managers and how to disable persistence can be found in the tomcat documentation so it's a case of RTFM. http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/manager.html should get you started. It sounds like it is not a case of session persistence or sessions not being invalidated that is causing your problem however. I recommend, as always, that you get jvmstat from sun and monitor your tomcat instance with it. It will allow you to observe the jvm and the various parts of the heap and diagnose where the problem is. Ta Matt -Original Message- From: Guillaume Lahitette [mailto:[EMAIL PROTECTED] Sent: 04 March 2005 17:58 To: Tomcat Users List Subject: RE: OutOfMemory / JMeter / Profiler questions Matt, Thanks for your feedbackwhich triggered more questions below! -Original Message- From: Dale, Matt [mailto:[EMAIL PROTECTED] Sent: 04 March 2005 15:26 To: Tomcat Users List Subject: RE: OutOfMemory / JMeter / Profiler questions Hi, Tomcat always serializes sessions on shutdown and reloads them on startup. Can anyone explain what is the usage for this? You can not re-use a session after a restart, can you??? I would think new session ID is created. This is the default behaviour but can be changed. Does anyone know how? If I can't see any usage for this, I'm very keen on disabling it. You are right in thinking that sessions are serialized per context though. Are you using the standard manager or the persistent manager as they are stored differently with the persistent manager. First time I hear about these! I could see a commented PersistentManager in server.xml so I guess I am using the standard manager. Can you tell me more about these? Why/When would I use the PersistentManager? Although you don't store anything in a session, do you perhaps instanciate it? The number of sessions you currently have can be viewed from the manager application. Yes, I've been using it a lot for context stop / start / reload and monitoring the sessions... Cheers, G Ta Matt -Original Message- From: Guillaume Lahitette [mailto:[EMAIL PROTECTED] Sent: 04 March 2005 15:15 To: Tomcat Users List Subject: RE: OutOfMemory / JMeter / Profiler questions Alan, Thanks for your feedback. You got me curious here: Why does/would Tomcat reload sessions after startup? Aren't the sessions destroyed upon Tomcat shutdown? Also, I could only find a $TOMCAT_HOME/work/Standalone/localhost/prti-rpt-engine.2.4.2.b17/S ESSIONS.se r, which is NOT the context I have been load testing. Sessions should be serialized per context, shouldn't they? We do not store anything in the session (our test just calls a servlet which generate a PDF report) so I can't see why the sessions would be using so much memory. But I'll definitely keep your idea in mind for other tests. I should hopefully be able to run the same tests on our staging platform and see if we get similar behaviors. Thanks for your inputs. Please keep them coming! Cheers, Guillaume -Original Message- From: Flisch, Alan [mailto:[EMAIL PROTECTED] Sent: 03 March 2005 12:17 To: Tomcat Users List Subject: RE: OutOfMemory / JMeter / Profiler questions You probably have either very large or very many sessions which Tomcat is attempting to reload on startup. Tomcat serialises sessions into files called SESSIONS.ser (in the application directories under the work dir) and then when it is restarted it attempts to reload them all. I presume this behaviour can be turned off. In terms of testing your app, you want to figure out whether you have a memory leak issue with your app, or simply that your max heap size is set too low for the load you are running. To check for memory leaks, you could run jmeter reasonably (although not too hard) excercising as much of your app as you can, repetitively and for an extended period. If it eventually keels over then you may need to investigate memory leaks with a profiler. Another possibility is that you may not be invalidating sessions and they are just being left to expire naturally. This can use up a lot of memory if you aren't careful and I supect is a quite likely source of your problems. Cheers! -Original Message- From: Guillaume Lahitette [mailto:[EMAIL PROTECTED] Sent: 03 March 2005 09:51 To: tomcat-user@jakarta.apache.org Subject: OutOfMemory / JMeter / Profiler questions Hello Tomcat'oids! We've started performance testing one of our REMOTE web apps using JMeter. We're gathering benchmark data before doing further fine tuning. Details: Win2K only have ssh + cygwin access to this remote server JDK 1.4.1_03 Tomcat 4.1.26, running as a service
OutOfMemory / JMeter / Profiler questions
Hello Tomcat'oids! We've started performance testing one of our REMOTE web apps using JMeter. We're gathering benchmark data before doing further fine tuning. Details: Win2K only have ssh + cygwin access to this remote server JDK 1.4.1_03 Tomcat 4.1.26, running as a service: a.. Use security manager 1 b.. Security policy file D:\Tomcat4\conf\catalina.policy c.. Initial heap 256 d.. Max heap 512 e.. Stack size 256 f.. JVM server Issue: We are getting OutOfMemory errors with very few threads simulated (as low as 5). More problematic, we've seen the OOM just after a Tomcat service restart! From the stack trace below, you can see we get the OOM before any of our code is executed :( Questions: a.. Anyone has seen this behavior upon Tomcat start up? b.. Anything particular to watch for in our JMeter test plan? c.. Would a profiler help? Could it profile a remote Tomcat installation? Any +/- feedback on Eclipse Profiler plug in (http://eclipsecolorer.sourceforge.net/index_profiler.html)? We'll work on gathering more data (e.g. periodic free / allocated memory dumps). Untill then, thank you for sharing your experiences, suggestions, code,...! Cheers, Guillaume javax.servlet.ServletException: Servlet execution threw an exception at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:98) at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:176) at java.security.AccessController.doPrivileged(Native Method) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:172) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2416) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:577) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:601) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619) at java.lang.Thread.run(Thread.java:536) root cause java.lang.OutOfMemoryError
Re: OutOfMemory / JMeter / Profiler questions
We've started performance testing one of our REMOTE web apps using JMeter. We're gathering benchmark data before doing further fine tuning. Details: Win2K only have ssh + cygwin access to this remote server JDK 1.4.1_03 Tomcat 4.1.26, running as a service: a.. Use security manager 1 b.. Security policy file D:\Tomcat4\conf\catalina.policy c.. Initial heap 256 d.. Max heap 512 e.. Stack size 256 f.. JVM server I cannot help you with respect to your OOM problems, but I would recommend that you consider upgrading to JVM 1.4.2. You should also be able to migrate your app to TC 5.0.28 without too much grief. You should probably avoid TC 5.5.x for the meantime. JVM 1.4.2 and TC 5.0.28 play well together. Good luck in case! Harry Mantheakis London, UK - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: OutOfMemory / JMeter / Profiler questions
You probably have either very large or very many sessions which Tomcat is attempting to reload on startup. Tomcat serialises sessions into files called SESSIONS.ser (in the application directories under the work dir) and then when it is restarted it attempts to reload them all. I presume this behaviour can be turned off. In terms of testing your app, you want to figure out whether you have a memory leak issue with your app, or simply that your max heap size is set too low for the load you are running. To check for memory leaks, you could run jmeter reasonably (although not too hard) excercising as much of your app as you can, repetitively and for an extended period. If it eventually keels over then you may need to investigate memory leaks with a profiler. Another possibility is that you may not be invalidating sessions and they are just being left to expire naturally. This can use up a lot of memory if you aren't careful and I supect is a quite likely source of your problems. Cheers! -Original Message- From: Guillaume Lahitette [mailto:[EMAIL PROTECTED] Sent: 03 March 2005 09:51 To: tomcat-user@jakarta.apache.org Subject: OutOfMemory / JMeter / Profiler questions Hello Tomcat'oids! We've started performance testing one of our REMOTE web apps using JMeter. We're gathering benchmark data before doing further fine tuning. Details: Win2K only have ssh + cygwin access to this remote server JDK 1.4.1_03 Tomcat 4.1.26, running as a service: a.. Use security manager 1 b.. Security policy file D:\Tomcat4\conf\catalina.policy c.. Initial heap 256 d.. Max heap 512 e.. Stack size 256 f.. JVM server Issue: We are getting OutOfMemory errors with very few threads simulated (as low as 5). More problematic, we've seen the OOM just after a Tomcat service restart! From the stack trace below, you can see we get the OOM before any of our code is executed :( Questions: a.. Anyone has seen this behavior upon Tomcat start up? b.. Anything particular to watch for in our JMeter test plan? c.. Would a profiler help? Could it profile a remote Tomcat installation? Any +/- feedback on Eclipse Profiler plug in (http://eclipsecolorer.sourceforge.net/index_profiler.html)? We'll work on gathering more data (e.g. periodic free / allocated memory dumps). Untill then, thank you for sharing your experiences, suggestions, code,...! Cheers, Guillaume javax.servlet.ServletException: Servlet execution threw an exception at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:98) at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:176) at java.security.AccessController.doPrivileged(Native Method) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:172) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2416) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:577) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480
OutOfMemory
Hello, I have some OUtOfMemory exception with my tomcat and I was wondering how could I increase the amount of memory allocate to Tomcat. Right now it is running the default amount of memory which is 64 MB and it is not enought. Thanx by advance Edouard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OutOfMemory
CATALINA_OPT=-Xmx256M -Xms256M Viorel Dragomir . .. --- - Original Message - From: Edouard Dalla-Costa To: Tomcat Users List Sent: Tuesday, March 01, 2005 11:11 Subject: OutOfMemory Hello, I have some OUtOfMemory exception with my tomcat and I was wondering how could I increase the amount of memory allocate to Tomcat. Right now it is running the default amount of memory which is 64 MB and it is not enought. Thanx by advance Edouard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: outOfMemory exception under high load
Just a thought, I was having the same problem using JNDI for database connection. Our database pool was going crazy due to a lot of connections left unterminated and database memory usage was enormous. Restarting Tomcat would only help for a day or two and than OutOfMemory errors would come up again. Restarting the database, gave us several weeks until the error started coming up again once the memory used by database grew. Thinking that it had something to do with the memory it took to maintain the pool. Oleg On Mon, 7 Feb 2005 23:02:36 -0600, Caldarale, Charles R [EMAIL PROTECTED] wrote: From: Dale, Matt [mailto:[EMAIL PROTECTED] Subject: RE: outOfMemory exception under high load It could be your permanent generation that is running out of space. Get a hold of jvmstat to determine if this is the case. Another possibility is that you're exceeding your limit on the number of open files. Exceeding any underlying OS limit is usually translated to an OutOfMemory exception by the JVM. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - 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]
outOfMemory exception under high load
Hi, Hi, I am experiencing a problem many others seem to have had before, but have found no answers. I am running Tomcat 5.0.25 using jdk 1.4.2_06 hotspot vm on RedHat Linux ES with 4G Ram and twin Intel procs. When load-testing, under high stress I receive the error below and the thread dies. 04-Feb-2005 13:39:24 org.apache.coyote.tomcat5.CoyoteAdapter service SEVERE: An exception or error occurred in the container during the request processing java.lang.OutOfMemoryError at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.init(ZipFile.java:112) at java.util.jar.JarFile.init(JarFile.java:127) .. I have adjusted the vm parameters to the below ( the perm space does not get full and the Xint to not use the optimised settings.. -server -Xms1G -Xmx1G -Xmn384m -XX:SurvivorRatio=7 -XX:PermSize=64m -XX:MaxPermSize=128m -Xint In addition I have added the reloading=false and development=false in conf/web.xml. as per instruction from this thread: http://www.junlu.com/msg/78566.html My connector is configured thus: Connector port=80 maxThreads=1000 minSpareThreads=1000 maxSpareThreads=1000 enableLookups=false redirectPort=8443 acceptCount=3000 debug=0 connectionTimeout=2 disableUploadTimeout=true / However all of this is to no avail, and under high stress (80+ concurrent requests, tomcat dies and terminates the thread dumping a hs_pid12345.log with the above message Is this a known hotspot 1.4.x problem (some threads have hinted at this), or does someone have a solution for this?? Thanks, M - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: outOfMemory exception under high load
how much memory is your process using when it crashes ? -r Michael Cornell wrote: Hi, Hi, I am experiencing a problem many others seem to have had before, but have found no answers. I am running Tomcat 5.0.25 using jdk 1.4.2_06 hotspot vm on RedHat Linux ES with 4G Ram and twin Intel procs. When load-testing, under high stress I receive the error below and the thread dies. 04-Feb-2005 13:39:24 org.apache.coyote.tomcat5.CoyoteAdapter service SEVERE: An exception or error occurred in the container during the request processing java.lang.OutOfMemoryError at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.init(ZipFile.java:112) at java.util.jar.JarFile.init(JarFile.java:127) .. I have adjusted the vm parameters to the below ( the perm space does not get full and the Xint to not use the optimised settings.. -server -Xms1G -Xmx1G -Xmn384m -XX:SurvivorRatio=7 -XX:PermSize=64m -XX:MaxPermSize=128m -Xint In addition I have added the reloading=false and development=false in conf/web.xml. as per instruction from this thread: http://www.junlu.com/msg/78566.html My connector is configured thus: Connector port=80 maxThreads=1000 minSpareThreads=1000 maxSpareThreads=1000 enableLookups=false redirectPort=8443 acceptCount=3000 debug=0 connectionTimeout=2 disableUploadTimeout=true / However all of this is to no avail, and under high stress (80+ concurrent requests, tomcat dies and terminates the thread dumping a hs_pid12345.log with the above message Is this a known hotspot 1.4.x problem (some threads have hinted at this), or does someone have a solution for this?? Thanks, M - 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]
Re: outOfMemory exception under high load
Not exactly sure but by running vmstat, it look like I am nearing the 2G limit .. maybe about 1.8G consumed.. /m reynir wrote: how much memory is your process using when it crashes ? -r Michael Cornell wrote: Hi, Hi, I am experiencing a problem many others seem to have had before, but have found no answers. I am running Tomcat 5.0.25 using jdk 1.4.2_06 hotspot vm on RedHat Linux ES with 4G Ram and twin Intel procs. When load-testing, under high stress I receive the error below and the thread dies. 04-Feb-2005 13:39:24 org.apache.coyote.tomcat5.CoyoteAdapter service SEVERE: An exception or error occurred in the container during the request processing java.lang.OutOfMemoryError at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.init(ZipFile.java:112) at java.util.jar.JarFile.init(JarFile.java:127) .. I have adjusted the vm parameters to the below ( the perm space does not get full and the Xint to not use the optimised settings.. -server -Xms1G -Xmx1G -Xmn384m -XX:SurvivorRatio=7 -XX:PermSize=64m -XX:MaxPermSize=128m -Xint In addition I have added the reloading=false and development=false in conf/web.xml. as per instruction from this thread: http://www.junlu.com/msg/78566.html My connector is configured thus: Connector port=80 maxThreads=1000 minSpareThreads=1000 maxSpareThreads=1000 enableLookups=false redirectPort=8443 acceptCount=3000 debug=0 connectionTimeout=2 disableUploadTimeout=true / However all of this is to no avail, and under high stress (80+ concurrent requests, tomcat dies and terminates the thread dumping a hs_pid12345.log with the above message Is this a known hotspot 1.4.x problem (some threads have hinted at this), or does someone have a solution for this?? Thanks, M - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: outOfMemory exception under high load
well, your -Xmx1G set's the limit for memory usage at 1 gig. ? -server -Xms1G -Xmx1G -Xmn384m -XX:SurvivorRatio=7 -XX:PermSize=64m -XX:MaxPermSize=128m -Xint you might want to set that a little higher. Michael Cornell wrote: Not exactly sure but by running vmstat, it look like I am nearing the 2G limit .. maybe about 1.8G consumed.. /m reynir wrote: how much memory is your process using when it crashes ? -r Michael Cornell wrote: Hi, Hi, I am experiencing a problem many others seem to have had before, but have found no answers. I am running Tomcat 5.0.25 using jdk 1.4.2_06 hotspot vm on RedHat Linux ES with 4G Ram and twin Intel procs. When load-testing, under high stress I receive the error below and the thread dies. 04-Feb-2005 13:39:24 org.apache.coyote.tomcat5.CoyoteAdapter service SEVERE: An exception or error occurred in the container during the request processing java.lang.OutOfMemoryError at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.init(ZipFile.java:112) at java.util.jar.JarFile.init(JarFile.java:127) .. I have adjusted the vm parameters to the below ( the perm space does not get full and the Xint to not use the optimised settings.. -server -Xms1G -Xmx1G -Xmn384m -XX:SurvivorRatio=7 -XX:PermSize=64m -XX:MaxPermSize=128m -Xint In addition I have added the reloading=false and development=false in conf/web.xml. as per instruction from this thread: http://www.junlu.com/msg/78566.html My connector is configured thus: Connector port=80 maxThreads=1000 minSpareThreads=1000 maxSpareThreads=1000 enableLookups=false redirectPort=8443 acceptCount=3000 debug=0 connectionTimeout=2 disableUploadTimeout=true / However all of this is to no avail, and under high stress (80+ concurrent requests, tomcat dies and terminates the thread dumping a hs_pid12345.log with the above message Is this a known hotspot 1.4.x problem (some threads have hinted at this), or does someone have a solution for this?? Thanks, M - 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] - 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]
Re: outOfMemory exception under high load
Sorry, that was a copy and paste typo :( Its set at 2G (4G for the whole machine) /m reynir wrote: well, your -Xmx1G set's the limit for memory usage at 1 gig. ? -server -Xms1G -Xmx1G -Xmn384m -XX:SurvivorRatio=7 -XX:PermSize=64m -XX:MaxPermSize=128m -Xint you might want to set that a little higher. Michael Cornell wrote: Not exactly sure but by running vmstat, it look like I am nearing the 2G limit .. maybe about 1.8G consumed.. /m reynir wrote: how much memory is your process using when it crashes ? -r Michael Cornell wrote: Hi, Hi, I am experiencing a problem many others seem to have had before, but have found no answers. I am running Tomcat 5.0.25 using jdk 1.4.2_06 hotspot vm on RedHat Linux ES with 4G Ram and twin Intel procs. When load-testing, under high stress I receive the error below and the thread dies. 04-Feb-2005 13:39:24 org.apache.coyote.tomcat5.CoyoteAdapter service SEVERE: An exception or error occurred in the container during the request processing java.lang.OutOfMemoryError at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.init(ZipFile.java:112) at java.util.jar.JarFile.init(JarFile.java:127) .. I have adjusted the vm parameters to the below ( the perm space does not get full and the Xint to not use the optimised settings.. -server -Xms1G -Xmx1G -Xmn384m -XX:SurvivorRatio=7 -XX:PermSize=64m -XX:MaxPermSize=128m -Xint In addition I have added the reloading=false and development=false in conf/web.xml. as per instruction from this thread: http://www.junlu.com/msg/78566.html My connector is configured thus: Connector port=80 maxThreads=1000 minSpareThreads=1000 maxSpareThreads=1000 enableLookups=false redirectPort=8443 acceptCount=3000 debug=0 connectionTimeout=2 disableUploadTimeout=true / However all of this is to no avail, and under high stress (80+ concurrent requests, tomcat dies and terminates the thread dumping a hs_pid12345.log with the above message Is this a known hotspot 1.4.x problem (some threads have hinted at this), or does someone have a solution for this?? Thanks, M - 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] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: outOfMemory exception under high load
If I remember it correctly Xmn384m defines the next step in increasing the allocated memory. there for if you have 1800m used and the max is at 2g, taking a step of almost 400m may not work. Why are you setting these paremeters : -Xmn384m -XX:SurvivorRatio=7 -XX:PermSize=64m -XX:MaxPermSize=128m -Xint I usually only set the -Xmx and -server Your problem might also be kernel based problem, you might need a kernel update, but I'm not a specialist on that subject. I only know that there are some limitations in some linux setups on how much memory it can make use of, but I think the limit lies around 4gigs. but that dependes on which kernel you are using etc. Michael Cornell wrote: Sorry, that was a copy and paste typo :( Its set at 2G (4G for the whole machine) /m reynir wrote: well, your -Xmx1G set's the limit for memory usage at 1 gig. ? -server -Xms1G -Xmx1G -Xmn384m -XX:SurvivorRatio=7 -XX:PermSize=64m -XX:MaxPermSize=128m -Xint you might want to set that a little higher. Michael Cornell wrote: Not exactly sure but by running vmstat, it look like I am nearing the 2G limit .. maybe about 1.8G consumed.. /m reynir wrote: how much memory is your process using when it crashes ? -r Michael Cornell wrote: Hi, Hi, I am experiencing a problem many others seem to have had before, but have found no answers. I am running Tomcat 5.0.25 using jdk 1.4.2_06 hotspot vm on RedHat Linux ES with 4G Ram and twin Intel procs. When load-testing, under high stress I receive the error below and the thread dies. 04-Feb-2005 13:39:24 org.apache.coyote.tomcat5.CoyoteAdapter service SEVERE: An exception or error occurred in the container during the request processing java.lang.OutOfMemoryError at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.init(ZipFile.java:112) at java.util.jar.JarFile.init(JarFile.java:127) .. I have adjusted the vm parameters to the below ( the perm space does not get full and the Xint to not use the optimised settings.. -server -Xms1G -Xmx1G -Xmn384m -XX:SurvivorRatio=7 -XX:PermSize=64m -XX:MaxPermSize=128m -Xint In addition I have added the reloading=false and development=false in conf/web.xml. as per instruction from this thread: http://www.junlu.com/msg/78566.html My connector is configured thus: Connector port=80 maxThreads=1000 minSpareThreads=1000 maxSpareThreads=1000 enableLookups=false redirectPort=8443 acceptCount=3000 debug=0 connectionTimeout=2 disableUploadTimeout=true / However all of this is to no avail, and under high stress (80+ concurrent requests, tomcat dies and terminates the thread dumping a hs_pid12345.log with the above message Is this a known hotspot 1.4.x problem (some threads have hinted at this), or does someone have a solution for this?? Thanks, M - 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] - 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] - 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]
RE: outOfMemory exception under high load
It could be your permanent generation that is running out of space. Get a hold of jvmstat to determine if this is the case. Ta Matt -Original Message- From: Michael Cornell [mailto:[EMAIL PROTECTED] Sent: 07 February 2005 11:31 To: Tomcat Users List Subject: Re: outOfMemory exception under high load Sorry, that was a copy and paste typo :( Its set at 2G (4G for the whole machine) /m reynir wrote: well, your -Xmx1G set's the limit for memory usage at 1 gig. ? -server -Xms1G -Xmx1G -Xmn384m -XX:SurvivorRatio=7 -XX:PermSize=64m -XX:MaxPermSize=128m -Xint you might want to set that a little higher. Michael Cornell wrote: Not exactly sure but by running vmstat, it look like I am nearing the 2G limit .. maybe about 1.8G consumed.. /m reynir wrote: how much memory is your process using when it crashes ? -r Michael Cornell wrote: Hi, Hi, I am experiencing a problem many others seem to have had before, but have found no answers. I am running Tomcat 5.0.25 using jdk 1.4.2_06 hotspot vm on RedHat Linux ES with 4G Ram and twin Intel procs. When load-testing, under high stress I receive the error below and the thread dies. 04-Feb-2005 13:39:24 org.apache.coyote.tomcat5.CoyoteAdapter service SEVERE: An exception or error occurred in the container during the request processing java.lang.OutOfMemoryError at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.init(ZipFile.java:112) at java.util.jar.JarFile.init(JarFile.java:127) .. I have adjusted the vm parameters to the below ( the perm space does not get full and the Xint to not use the optimised settings.. -server -Xms1G -Xmx1G -Xmn384m -XX:SurvivorRatio=7 -XX:PermSize=64m -XX:MaxPermSize=128m -Xint In addition I have added the reloading=false and development=false in conf/web.xml. as per instruction from this thread: http://www.junlu.com/msg/78566.html My connector is configured thus: Connector port=80 maxThreads=1000 minSpareThreads=1000 maxSpareThreads=1000 enableLookups=false redirectPort=8443 acceptCount=3000 debug=0 connectionTimeout=2 disableUploadTimeout=true / However all of this is to no avail, and under high stress (80+ concurrent requests, tomcat dies and terminates the thread dumping a hs_pid12345.log with the above message Is this a known hotspot 1.4.x problem (some threads have hinted at this), or does someone have a solution for this?? Thanks, M - 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] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Any opinions expressed in this E-mail may be those of the individual and not necessarily the company. This E-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this E-mail in error and that any use or copying is strictly prohibited. If you have received this E-mail in error please notify the beCogent postmaster at [EMAIL PROTECTED] Unless expressly stated, opinions in this email are those of the individual sender and not beCogent Ltd. You must take full responsibility for virus checking this email and any attachments. Please note that the content of this email or any of its attachments may contain data that falls within the scope of the Data Protection Acts and that you must ensure that any handling or processing of such data by you is fully compliant with the terms and provisions of the Data Protection Act 1984 and 1998. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: outOfMemory exception under high load
Hi, RE Matt: // I am already running visualgc (jvmstat) on it... the behavior is just that the heap fills up (no gc) and then at about 80% full it just bombs out. Perm Gen is only 20% full and none of the others are used.. RE reynir: Why are you setting these paremeters : -Xmn384m -XX:SurvivorRatio=7 -XX:PermSize=64m -XX:MaxPermSize=128m -Xint I usually only set the -Xmx and -server // The Permsize params have been put in in case that was the problem (running out of perm space) and the -Xint as this makes it run without any optimisations (I believe) ie all interpreted. Xmn is the New Generation= (eden) + (from + to) and survivor ratio is just that.. the ratio of eden - survivors I can see no reason why these should mess anything up sufficiently to produce this error. Dale, Matt wrote: It could be your permanent generation that is running out of space. Get a hold of jvmstat to determine if this is the case. Ta Matt -Original Message- From: Michael Cornell [mailto:[EMAIL PROTECTED] Sent: 07 February 2005 11:31 To: Tomcat Users List Subject: Re: outOfMemory exception under high load Sorry, that was a copy and paste typo :( Its set at 2G (4G for the whole machine) /m reynir wrote: well, your -Xmx1G set's the limit for memory usage at 1 gig. ? -server -Xms1G -Xmx1G -Xmn384m -XX:SurvivorRatio=7 -XX:PermSize=64m -XX:MaxPermSize=128m -Xint you might want to set that a little higher. Michael Cornell wrote: Not exactly sure but by running vmstat, it look like I am nearing the 2G limit .. maybe about 1.8G consumed.. /m reynir wrote: how much memory is your process using when it crashes ? -r Michael Cornell wrote: Hi, Hi, I am experiencing a problem many others seem to have had before, but have found no answers. I am running Tomcat 5.0.25 using jdk 1.4.2_06 hotspot vm on RedHat Linux ES with 4G Ram and twin Intel procs. When load-testing, under high stress I receive the error below and the thread dies. 04-Feb-2005 13:39:24 org.apache.coyote.tomcat5.CoyoteAdapter service SEVERE: An exception or error occurred in the container during the request processing java.lang.OutOfMemoryError at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.init(ZipFile.java:112) at java.util.jar.JarFile.init(JarFile.java:127) .. I have adjusted the vm parameters to the below ( the perm space does not get full and the Xint to not use the optimised settings.. -server -Xms1G -Xmx1G -Xmn384m -XX:SurvivorRatio=7 -XX:PermSize=64m -XX:MaxPermSize=128m -Xint In addition I have added the reloading=false and development=false in conf/web.xml. as per instruction from this thread: http://www.junlu.com/msg/78566.html My connector is configured thus: Connector port=80 maxThreads=1000 minSpareThreads=1000 maxSpareThreads=1000 enableLookups=false redirectPort=8443 acceptCount=3000 debug=0 connectionTimeout=2 disableUploadTimeout=true / However all of this is to no avail, and under high stress (80+ concurrent requests, tomcat dies and terminates the thread dumping a hs_pid12345.log with the above message Is this a known hotspot 1.4.x problem (some threads have hinted at this), or does someone have a solution for this?? Thanks, M - 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] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Any opinions expressed in this E-mail may be those of the individual and not necessarily the company. This E-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this E-mail in error and that any use or copying is strictly prohibited. If you have received this E-mail in error please notify the beCogent postmaster at [EMAIL PROTECTED] Unless expressly stated, opinions in this email are those of the individual sender and not beCogent Ltd. You must
RE: outOfMemory exception under high load
In that case then it sounds like either a memory leak or you just don't have enough memory to support your application. Do you have large objects in your sessions? I'd get a profilier and find out what objects are in your heap when you get the exceptions and it should lead you to the root cause of your problem. Ta Matt -Original Message- From: Michael Cornell [mailto:[EMAIL PROTECTED] Sent: 07 February 2005 12:01 To: Tomcat Users List Subject: Re: outOfMemory exception under high load Hi, RE Matt: // I am already running visualgc (jvmstat) on it... the behavior is just that the heap fills up (no gc) and then at about 80% full it just bombs out. Perm Gen is only 20% full and none of the others are used.. RE reynir: Why are you setting these paremeters : -Xmn384m -XX:SurvivorRatio=7 -XX:PermSize=64m -XX:MaxPermSize=128m -Xint I usually only set the -Xmx and -server // The Permsize params have been put in in case that was the problem (running out of perm space) and the -Xint as this makes it run without any optimisations (I believe) ie all interpreted. Xmn is the New Generation= (eden) + (from + to) and survivor ratio is just that.. the ratio of eden - survivors I can see no reason why these should mess anything up sufficiently to produce this error. Dale, Matt wrote: It could be your permanent generation that is running out of space. Get a hold of jvmstat to determine if this is the case. Ta Matt -Original Message- From: Michael Cornell [mailto:[EMAIL PROTECTED] Sent: 07 February 2005 11:31 To: Tomcat Users List Subject: Re: outOfMemory exception under high load Sorry, that was a copy and paste typo :( Its set at 2G (4G for the whole machine) /m reynir wrote: well, your -Xmx1G set's the limit for memory usage at 1 gig. ? -server -Xms1G -Xmx1G -Xmn384m -XX:SurvivorRatio=7 -XX:PermSize=64m -XX:MaxPermSize=128m -Xint you might want to set that a little higher. Michael Cornell wrote: Not exactly sure but by running vmstat, it look like I am nearing the 2G limit .. maybe about 1.8G consumed.. /m reynir wrote: how much memory is your process using when it crashes ? -r Michael Cornell wrote: Hi, Hi, I am experiencing a problem many others seem to have had before, but have found no answers. I am running Tomcat 5.0.25 using jdk 1.4.2_06 hotspot vm on RedHat Linux ES with 4G Ram and twin Intel procs. When load-testing, under high stress I receive the error below and the thread dies. 04-Feb-2005 13:39:24 org.apache.coyote.tomcat5.CoyoteAdapter service SEVERE: An exception or error occurred in the container during the request processing java.lang.OutOfMemoryError at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.init(ZipFile.java:112) at java.util.jar.JarFile.init(JarFile.java:127) .. I have adjusted the vm parameters to the below ( the perm space does not get full and the Xint to not use the optimised settings.. -server -Xms1G -Xmx1G -Xmn384m -XX:SurvivorRatio=7 -XX:PermSize=64m -XX:MaxPermSize=128m -Xint In addition I have added the reloading=false and development=false in conf/web.xml. as per instruction from this thread: http://www.junlu.com/msg/78566.html My connector is configured thus: Connector port=80 maxThreads=1000 minSpareThreads=1000 maxSpareThreads=1000 enableLookups=false redirectPort=8443 acceptCount=3000 debug=0 connectionTimeout=2 disableUploadTimeout=true / However all of this is to no avail, and under high stress (80+ concurrent requests, tomcat dies and terminates the thread dumping a hs_pid12345.log with the above message Is this a known hotspot 1.4.x problem (some threads have hinted at this), or does someone have a solution for this?? Thanks, M - 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] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Any opinions expressed in this E-mail may be those of the individual and not necessarily the company. This E-mail and any files transmitted
RE: outOfMemory exception under high load
Once you rule out your heap and perm generation, you can look at thread stacks. Under high loads, you create a lot of threads. There are variations depending on the host OS and VM, but in a 32-bit operating system with thread stacks in the 1-4 MB range and a big heap, you can easily run out of virtual address space. In addition, I'm not sure if there aren't some cases where thread stacks are allocated reserved, which means you could also get an OOME from not having enough swap space. If you think this might be it, try tuning your thread pools (lower the max pool size), lowering perm gen size, heap size, switching to 64-bit, adding swap... Dale, Matt [EMAIL PROTECTED] wrote on 02/07/2005 07:34:36 AM: In that case then it sounds like either a memory leak or you just don't have enough memory to support your application. Do you have large objects in your sessions? I'd get a profilier and find out what objects are in your heap when you get the exceptions and it should lead you to the root cause of your problem. Ta Matt -Original Message- From: Michael Cornell [mailto:[EMAIL PROTECTED] Sent: 07 February 2005 12:01 To: Tomcat Users List Subject: Re: outOfMemory exception under high load Hi, RE Matt: // I am already running visualgc (jvmstat) on it... the behavior is just that the heap fills up (no gc) and then at about 80% full it just bombs out. Perm Gen is only 20% full and none of the others are used.. RE reynir: Why are you setting these paremeters : -Xmn384m -XX:SurvivorRatio=7 -XX:PermSize=64m -XX:MaxPermSize=128m -Xint I usually only set the -Xmx and -server // The Permsize params have been put in in case that was the problem (running out of perm space) and the -Xint as this makes it run without any optimisations (I believe) ie all interpreted. Xmn is the New Generation= (eden) + (from + to) and survivor ratio is just that.. the ratio of eden - survivors I can see no reason why these should mess anything up sufficiently to produce this error. Dale, Matt wrote: It could be your permanent generation that is running out of space. Get a hold of jvmstat to determine if this is the case. Ta Matt -Original Message- From: Michael Cornell [mailto:[EMAIL PROTECTED] Sent: 07 February 2005 11:31 To: Tomcat Users List Subject: Re: outOfMemory exception under high load Sorry, that was a copy and paste typo :( Its set at 2G (4G for the whole machine) /m reynir wrote: well, your -Xmx1G set's the limit for memory usage at 1 gig. ? -server -Xms1G -Xmx1G -Xmn384m -XX:SurvivorRatio=7 -XX:PermSize=64m -XX:MaxPermSize=128m -Xint you might want to set that a little higher. Michael Cornell wrote: Not exactly sure but by running vmstat, it look like I am nearing the 2G limit .. maybe about 1.8G consumed.. /m reynir wrote: how much memory is your process using when it crashes ? -r Michael Cornell wrote: Hi, Hi, I am experiencing a problem many others seem to have had before, but have found no answers. I am running Tomcat 5.0.25 using jdk 1.4.2_06 hotspot vm on RedHat Linux ES with 4G Ram and twin Intel procs. When load-testing, under high stress I receive the error below and the thread dies. 04-Feb-2005 13:39:24 org.apache.coyote.tomcat5.CoyoteAdapter service SEVERE: An exception or error occurred in the container during the request processing java.lang.OutOfMemoryError at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.init(ZipFile.java:112) at java.util.jar.JarFile.init(JarFile.java:127) .. I have adjusted the vm parameters to the below ( the perm space does not get full and the Xint to not use the optimised settings.. -server -Xms1G -Xmx1G -Xmn384m -XX:SurvivorRatio=7 -XX:PermSize=64m -XX:MaxPermSize=128m -Xint In addition I have added the reloading=false and development=false in conf/web.xml. as per instruction from this thread: http://www.junlu.com/msg/78566.html My connector is configured thus: Connector port=80 maxThreads=1000 minSpareThreads=1000 maxSpareThreads=1000 enableLookups=false redirectPort=8443 acceptCount=3000 debug=0 connectionTimeout=2 disableUploadTimeout=true / However all of this is to no avail, and under high stress (80+ concurrent requests, tomcat dies and terminates the thread dumping a hs_pid12345.log with the above message Is this a known hotspot 1.4.x problem (some threads have hinted at this), or does someone have a solution for this?? Thanks, M - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED
RE: outOfMemory exception under high load
I would suggest running findbugs: http://findbugs.sourceforge.net/ It has found issues in application code for other people on the list. George Sexton MH Software, Inc. http://www.mhsoftware.com/ Voice: 303 438 9585 -Original Message- From: Michael Cornell [mailto:[EMAIL PROTECTED] Sent: Monday, February 07, 2005 3:37 AM To: Tomcat-User Subject: outOfMemory exception under high load Hi, Hi, I am experiencing a problem many others seem to have had before, but have found no answers. I am running Tomcat 5.0.25 using jdk 1.4.2_06 hotspot vm on RedHat Linux ES with 4G Ram and twin Intel procs. When load-testing, under high stress I receive the error below and the thread dies. 04-Feb-2005 13:39:24 org.apache.coyote.tomcat5.CoyoteAdapter service SEVERE: An exception or error occurred in the container during the request processing java.lang.OutOfMemoryError at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.init(ZipFile.java:112) at java.util.jar.JarFile.init(JarFile.java:127) .. I have adjusted the vm parameters to the below ( the perm space does not get full and the Xint to not use the optimised settings.. -server -Xms1G -Xmx1G -Xmn384m -XX:SurvivorRatio=7 -XX:PermSize=64m -XX:MaxPermSize=128m -Xint In addition I have added the reloading=false and development=false in conf/web.xml. as per instruction from this thread: http://www.junlu.com/msg/78566.html My connector is configured thus: Connector port=80 maxThreads=1000 minSpareThreads=1000 maxSpareThreads=1000 enableLookups=false redirectPort=8443 acceptCount=3000 debug=0 connectionTimeout=2 disableUploadTimeout=true / However all of this is to no avail, and under high stress (80+ concurrent requests, tomcat dies and terminates the thread dumping a hs_pid12345.log with the above message Is this a known hotspot 1.4.x problem (some threads have hinted at this), or does someone have a solution for this?? Thanks, M - 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]
RE: outOfMemory exception under high load
From: Dale, Matt [mailto:[EMAIL PROTECTED] Subject: RE: outOfMemory exception under high load It could be your permanent generation that is running out of space. Get a hold of jvmstat to determine if this is the case. Another possibility is that you're exceeding your limit on the number of open files. Exceeding any underlying OS limit is usually translated to an OutOfMemory exception by the JVM. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Still having OutOfMemory Problems (Tomcat 4.1.31)
If it is taking these settings then either those are not enough or you are running out space in the permanent generation. Use -XX:MaxPermSize=128m to boost the max size of it. -Original Message- From: David Johnson [mailto:[EMAIL PROTECTED] Sent: 17 January 2005 17:52 To: Tomcat Users List Subject: Still having OutOfMemory Problems (Tomcat 4.1.31) HI all. Well I'm still getting my out of memory problem fairly consistently (again) using Tomcat 4.1.31 with my Struts application. When I look st the memory usage, it says tomcat is using about 110k of memory for the VM, but that's just looking at the task manager. Tomcat is installed as a service using a bat file (follows). Note the -Xms128M and -Xmx512M options are set...if doesnt seem to matter what I set these options toeven if I set them to 32m/64m! How can I tell if tomcat is REALLY using those settings? It doesnt seem to be Thanks - install.bat: @SET JAVA_HOME=C:\j2sdk_1_4_0_2 @SET TOMCAT_HOME=C:\Tomcat4.1 @SET TOMCAT_JVM=%JAVA_HOME%\jre\bin\client\jvm.dll @SET TOMCAT_CLASSPATH=%TOMCAT_HOME%\bin\bootstrap.jar;%TOMCAT_HOME%\common\lib\servlet.jar @SET TOMCAT_ENDORSED=%TOMCAT_HOME%\common\endorsed @SET TOMCAT_LOG=%TOMCAT_HOME%\logs\stdout.log @SET TOMCAT_ERR_LOG=%TOMCAT_HOME%\logs\stderr.log %TOMCAT_HOME%\bin\tomcat.exe -install Apache Tomcat 4.1.31 %TOMCAT_JVM% -Djava.class.path=%TOMCAT_CLASSPATH% -DXms128M -DXmx512M -DXX:+PrintTenuringDistribution -DXX:+PrintGCDetails -Xverbosegc -Djava.endorsed.dirs=%TOMCAT_ENDORSED% -Dcatalina.home=%TOMCAT_HOME% -start org.apache.catalina.startup.BootstrapService -params start -stop org.apache.catalina.startup.BootstrapService -params stop -out %TOMCAT_LOG% -err %TOMCAT_ERR_LOG% - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Any opinions expressed in this E-mail may be those of the individual and not necessarily the company. This E-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this E-mail in error and that any use or copying is strictly prohibited. If you have received this E-mail in error please notify the beCogent postmaster at [EMAIL PROTECTED] Unless expressly stated, opinions in this email are those of the individual sender and not beCogent Ltd. You must take full responsibility for virus checking this email and any attachments. Please note that the content of this email or any of its attachments may contain data that falls within the scope of the Data Protection Acts and that you must ensure that any handling or processing of such data by you is fully compliant with the terms and provisions of the Data Protection Act 1984 and 1998. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Still having OutOfMemory Problems (Tomcat 4.1.31)
HI all. Well I'm still getting my out of memory problem fairly consistently (again) using Tomcat 4.1.31 with my Struts application. When I look st the memory usage, it says tomcat is using about 110k of memory for the VM, but that's just looking at the task manager. Tomcat is installed as a service using a bat file (follows). Note the -Xms128M and -Xmx512M options are set...if doesnt seem to matter what I set these options toeven if I set them to 32m/64m! How can I tell if tomcat is REALLY using those settings? It doesnt seem to be Thanks - install.bat: @SET JAVA_HOME=C:\j2sdk_1_4_0_2 @SET TOMCAT_HOME=C:\Tomcat4.1 @SET TOMCAT_JVM=%JAVA_HOME%\jre\bin\client\jvm.dll @SET TOMCAT_CLASSPATH=%TOMCAT_HOME%\bin\bootstrap.jar;%TOMCAT_HOME%\common\lib\servlet.jar @SET TOMCAT_ENDORSED=%TOMCAT_HOME%\common\endorsed @SET TOMCAT_LOG=%TOMCAT_HOME%\logs\stdout.log @SET TOMCAT_ERR_LOG=%TOMCAT_HOME%\logs\stderr.log %TOMCAT_HOME%\bin\tomcat.exe -install Apache Tomcat 4.1.31 %TOMCAT_JVM% -Djava.class.path=%TOMCAT_CLASSPATH% -DXms128M -DXmx512M -DXX:+PrintTenuringDistribution -DXX:+PrintGCDetails -Xverbosegc -Djava.endorsed.dirs=%TOMCAT_ENDORSED% -Dcatalina.home=%TOMCAT_HOME% -start org.apache.catalina.startup.BootstrapService -params start -stop org.apache.catalina.startup.BootstrapService -params stop -out %TOMCAT_LOG% -err %TOMCAT_ERR_LOG% - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Still having OutOfMemory Problems (Tomcat 4.1.31)
Try printing out this: Runtime.getRuntime().freeMemory(): Runtime.getRuntime().maxMemory(); Check out the API if you want to know the exact meaning of these methods, but they are pretty obvious I think. Now print these somewhere you know you'll get before the OutOfMemError occurs, or some place like the service() method or something. David -Original Message- From: David Johnson [mailto:[EMAIL PROTECTED] Sent: maandag 17 januari 2005 18:52 To: Tomcat Users List Subject: Still having OutOfMemory Problems (Tomcat 4.1.31) HI all. Well I'm still getting my out of memory problem fairly consistently (again) using Tomcat 4.1.31 with my Struts application. When I look st the memory usage, it says tomcat is using about 110k of memory for the VM, but that's just looking at the task manager. Tomcat is installed as a service using a bat file (follows). Note the -Xms128M and -Xmx512M options are set...if doesnt seem to matter what I set these options toeven if I set them to 32m/64m! How can I tell if tomcat is REALLY using those settings? It doesnt seem to be Thanks - install.bat: @SET JAVA_HOME=C:\j2sdk_1_4_0_2 @SET TOMCAT_HOME=C:\Tomcat4.1 @SET TOMCAT_JVM=%JAVA_HOME%\jre\bin\client\jvm.dll @SET TOMCAT_CLASSPATH=%TOMCAT_HOME%\bin\bootstrap.jar;%TOMCAT_HOME%\common\lib\servlet.jar @SET TOMCAT_ENDORSED=%TOMCAT_HOME%\common\endorsed @SET TOMCAT_LOG=%TOMCAT_HOME%\logs\stdout.log @SET TOMCAT_ERR_LOG=%TOMCAT_HOME%\logs\stderr.log %TOMCAT_HOME%\bin\tomcat.exe -install Apache Tomcat 4.1.31 %TOMCAT_JVM% -Djava.class.path=%TOMCAT_CLASSPATH% -DXms128M -DXmx512M -DXX:+PrintTenuringDistribution -DXX:+PrintGCDetails -Xverbosegc -Djava.endorsed.dirs=%TOMCAT_ENDORSED% -Dcatalina.home=%TOMCAT_HOME% -start org.apache.catalina.startup.BootstrapService -params start -stop org.apache.catalina.startup.BootstrapService -params stop -out %TOMCAT_LOG% -err %TOMCAT_ERR_LOG% - 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]
Re: Still having OutOfMemory Problems (Tomcat 4.1.31)
you should try using small m like -Xmx512m - this one. hope it helps -reynir David Johnson wrote: HI all. Well I'm still getting my out of memory problem fairly consistently (again) using Tomcat 4.1.31 with my Struts application. When I look st the memory usage, it says tomcat is using about 110k of memory for the VM, but that's just looking at the task manager. Tomcat is installed as a service using a bat file (follows). Note the -Xms128M and -Xmx512M options are set...if doesnt seem to matter what I set these options toeven if I set them to 32m/64m! How can I tell if tomcat is REALLY using those settings? It doesnt seem to be Thanks - install.bat: @SET JAVA_HOME=C:\j2sdk_1_4_0_2 @SET TOMCAT_HOME=C:\Tomcat4.1 @SET TOMCAT_JVM=%JAVA_HOME%\jre\bin\client\jvm.dll @SET TOMCAT_CLASSPATH=%TOMCAT_HOME%\bin\bootstrap.jar;%TOMCAT_HOME%\common\lib\servlet.jar @SET TOMCAT_ENDORSED=%TOMCAT_HOME%\common\endorsed @SET TOMCAT_LOG=%TOMCAT_HOME%\logs\stdout.log @SET TOMCAT_ERR_LOG=%TOMCAT_HOME%\logs\stderr.log %TOMCAT_HOME%\bin\tomcat.exe -install Apache Tomcat 4.1.31 %TOMCAT_JVM% -Djava.class.path=%TOMCAT_CLASSPATH% -DXms128M -DXmx512M -DXX:+PrintTenuringDistribution -DXX:+PrintGCDetails -Xverbosegc -Djava.endorsed.dirs=%TOMCAT_ENDORSED% -Dcatalina.home=%TOMCAT_HOME% -start org.apache.catalina.startup.BootstrapService -params start -stop org.apache.catalina.startup.BootstrapService -params stop -out %TOMCAT_LOG% -err %TOMCAT_ERR_LOG% - 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]
RE: Still having OutOfMemory Problems (Tomcat 4.1.31)
David, -D defines System properties, -X defines vendor specific JVM options. Thus, -DXms128M is incorrect. It should be just -Xms128M. Same for the other -DX arguments. Cheers, Larry -Original Message- From: David Johnson [mailto:[EMAIL PROTECTED] Sent: Monday, January 17, 2005 12:52 PM To: Tomcat Users List Subject: Still having OutOfMemory Problems (Tomcat 4.1.31) HI all. Well I'm still getting my out of memory problem fairly consistently (again) using Tomcat 4.1.31 with my Struts application. When I look st the memory usage, it says tomcat is using about 110k of memory for the VM, but that's just looking at the task manager. Tomcat is installed as a service using a bat file (follows). Note the -Xms128M and -Xmx512M options are set...if doesnt seem to matter what I set these options toeven if I set them to 32m/64m! How can I tell if tomcat is REALLY using those settings? It doesnt seem to be Thanks - install.bat: @SET JAVA_HOME=C:\j2sdk_1_4_0_2 @SET TOMCAT_HOME=C:\Tomcat4.1 @SET TOMCAT_JVM=%JAVA_HOME%\jre\bin\client\jvm.dll @SET TOMCAT_CLASSPATH=%TOMCAT_HOME%\bin\bootstrap.jar;%TOMCAT_HOME% \common\lib\servlet.jar @SET TOMCAT_ENDORSED=%TOMCAT_HOME%\common\endorsed @SET TOMCAT_LOG=%TOMCAT_HOME%\logs\stdout.log @SET TOMCAT_ERR_LOG=%TOMCAT_HOME%\logs\stderr.log %TOMCAT_HOME%\bin\tomcat.exe -install Apache Tomcat 4.1.31 %TOMCAT_JVM% -Djava.class.path=%TOMCAT_CLASSPATH% -DXms128M -DXmx512M -DXX:+PrintTenuringDistribution -DXX:+PrintGCDetails -Xverbosegc -Djava.endorsed.dirs=%TOMCAT_ENDORSED% -Dcatalina.home=%TOMCAT_HOME% -start org.apache.catalina.startup.BootstrapService -params start -stop org.apache.catalina.startup.BootstrapService -params stop -out %TOMCAT_LOG% -err %TOMCAT_ERR_LOG% - 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]
Re: Still having OutOfMemory Problems (Tomcat 4.1.31)
I think that was the problem My new batch file is # @SET JAVA_HOME=C:\j2sdk_1_4_0_2 @SET TOMCAT_HOME=C:\Tomcat4.1 @SET TOMCAT_JVM=%JAVA_HOME%\jre\bin\client\jvm.dll @SET TOMCAT_CLASSPATH=%TOMCAT_HOME%\bin\bootstrap.jar;%TOMCAT_HOME%\common\lib\servlet.jar @SET TOMCAT_ENDORSED=%TOMCAT_HOME%\common\endorsed @SET TOMCAT_LOG=%TOMCAT_HOME%\logs\stdout.log @SET TOMCAT_ERR_LOG=%TOMCAT_HOME%\logs\stderr.log %TOMCAT_HOME%\bin\tomcat.exe -install Apache Tomcat 4.1.31 %TOMCAT_JVM% -Djava.class.path=%TOMCAT_CLASSPATH% -Xms64m -Xmx512m -DXX:+PrintTenuringDistribution -DXX:+PrintGCDetails -Xverbosegc -Djava.endorsed.dirs=%TOMCAT_ENDORSED% -Dcatalina.home=%TOMCAT_HOME% -start org.apache.catalina.startup.BootstrapService -params start -stop org.apache.catalina.startup.BootstrapService -params stop -out %TOMCAT_LOG% -err %TOMCAT_ERR_LOG% On Mon, 17 Jan 2005 13:08:05 -0500, David Johnson [EMAIL PROTECTED] wrote: I'll give it a try. thanks! On Mon, 17 Jan 2005 13:07:26 -0500, Larry Isaacs [EMAIL PROTECTED] wrote: David, -D defines System properties, -X defines vendor specific JVM options. Thus, -DXms128M is incorrect. It should be just -Xms128M. Same for the other -DX arguments. Cheers, Larry -Original Message- From: David Johnson [mailto:[EMAIL PROTECTED] Sent: Monday, January 17, 2005 12:52 PM To: Tomcat Users List Subject: Still having OutOfMemory Problems (Tomcat 4.1.31) HI all. Well I'm still getting my out of memory problem fairly consistently (again) using Tomcat 4.1.31 with my Struts application. When I look st the memory usage, it says tomcat is using about 110k of memory for the VM, but that's just looking at the task manager. Tomcat is installed as a service using a bat file (follows). Note the -Xms128M and -Xmx512M options are set...if doesnt seem to matter what I set these options toeven if I set them to 32m/64m! How can I tell if tomcat is REALLY using those settings? It doesnt seem to be Thanks - install.bat: @SET JAVA_HOME=C:\j2sdk_1_4_0_2 @SET TOMCAT_HOME=C:\Tomcat4.1 @SET TOMCAT_JVM=%JAVA_HOME%\jre\bin\client\jvm.dll @SET TOMCAT_CLASSPATH=%TOMCAT_HOME%\bin\bootstrap.jar;%TOMCAT_HOME% \common\lib\servlet.jar @SET TOMCAT_ENDORSED=%TOMCAT_HOME%\common\endorsed @SET TOMCAT_LOG=%TOMCAT_HOME%\logs\stdout.log @SET TOMCAT_ERR_LOG=%TOMCAT_HOME%\logs\stderr.log %TOMCAT_HOME%\bin\tomcat.exe -install Apache Tomcat 4.1.31 %TOMCAT_JVM% -Djava.class.path=%TOMCAT_CLASSPATH% -DXms128M -DXmx512M -DXX:+PrintTenuringDistribution -DXX:+PrintGCDetails -Xverbosegc -Djava.endorsed.dirs=%TOMCAT_ENDORSED% -Dcatalina.home=%TOMCAT_HOME% -start org.apache.catalina.startup.BootstrapService -params start -stop org.apache.catalina.startup.BootstrapService -params stop -out %TOMCAT_LOG% -err %TOMCAT_ERR_LOG% - 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]
RE: Still having OutOfMemory Problems (Tomcat 4.1.31)
The -DX problem applies to the -DXX arguments too. Larry -Original Message- From: David Johnson [mailto:[EMAIL PROTECTED] Sent: Monday, January 17, 2005 1:16 PM To: Tomcat Users List Subject: Re: Still having OutOfMemory Problems (Tomcat 4.1.31) I think that was the problem My new batch file is # @SET JAVA_HOME=C:\j2sdk_1_4_0_2 @SET TOMCAT_HOME=C:\Tomcat4.1 @SET TOMCAT_JVM=%JAVA_HOME%\jre\bin\client\jvm.dll @SET TOMCAT_CLASSPATH=%TOMCAT_HOME%\bin\bootstrap.jar;%TOMCAT_HOME% \common\lib\servlet.jar @SET TOMCAT_ENDORSED=%TOMCAT_HOME%\common\endorsed @SET TOMCAT_LOG=%TOMCAT_HOME%\logs\stdout.log @SET TOMCAT_ERR_LOG=%TOMCAT_HOME%\logs\stderr.log %TOMCAT_HOME%\bin\tomcat.exe -install Apache Tomcat 4.1.31 %TOMCAT_JVM% -Djava.class.path=%TOMCAT_CLASSPATH% -Xms64m -Xmx512m -DXX:+PrintTenuringDistribution -DXX:+PrintGCDetails -Xverbosegc -Djava.endorsed.dirs=%TOMCAT_ENDORSED% -Dcatalina.home=%TOMCAT_HOME% -start org.apache.catalina.startup.BootstrapService -params start -stop org.apache.catalina.startup.BootstrapService -params stop -out %TOMCAT_LOG% -err %TOMCAT_ERR_LOG% On Mon, 17 Jan 2005 13:08:05 -0500, David Johnson [EMAIL PROTECTED] wrote: I'll give it a try. thanks! On Mon, 17 Jan 2005 13:07:26 -0500, Larry Isaacs [EMAIL PROTECTED] wrote: David, -D defines System properties, -X defines vendor specific JVM options. Thus, -DXms128M is incorrect. It should be just -Xms128M. Same for the other -DX arguments. Cheers, Larry -Original Message- From: David Johnson [mailto:[EMAIL PROTECTED] Sent: Monday, January 17, 2005 12:52 PM To: Tomcat Users List Subject: Still having OutOfMemory Problems (Tomcat 4.1.31) HI all. Well I'm still getting my out of memory problem fairly consistently (again) using Tomcat 4.1.31 with my Struts application. When I look st the memory usage, it says tomcat is using about 110k of memory for the VM, but that's just looking at the task manager. Tomcat is installed as a service using a bat file (follows). Note the -Xms128M and -Xmx512M options are set...if doesnt seem to matter what I set these options toeven if I set them to 32m/64m! How can I tell if tomcat is REALLY using those settings? It doesnt seem to be Thanks - install.bat: @SET JAVA_HOME=C:\j2sdk_1_4_0_2 @SET TOMCAT_HOME=C:\Tomcat4.1 @SET TOMCAT_JVM=%JAVA_HOME%\jre\bin\client\jvm.dll @SET TOMCAT_CLASSPATH=%TOMCAT_HOME%\bin\bootstrap.jar;%TOMCAT_HOME% \common\lib\servlet.jar @SET TOMCAT_ENDORSED=%TOMCAT_HOME%\common\endorsed @SET TOMCAT_LOG=%TOMCAT_HOME%\logs\stdout.log @SET TOMCAT_ERR_LOG=%TOMCAT_HOME%\logs\stderr.log %TOMCAT_HOME%\bin\tomcat.exe -install Apache Tomcat 4.1.31 %TOMCAT_JVM% -Djava.class.path=%TOMCAT_CLASSPATH% -DXms128M -DXmx512M -DXX:+PrintTenuringDistribution -DXX:+PrintGCDetails -Xverbosegc -Djava.endorsed.dirs=%TOMCAT_ENDORSED% -Dcatalina.home=%TOMCAT_HOME% -start org.apache.catalina.startup.BootstrapService -params start -stop org.apache.catalina.startup.BootstrapService -params stop -out %TOMCAT_LOG% -err %TOMCAT_ERR_LOG% - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OutOfMemory Errors
Hi, another idea... try to increase the size of the perm heap with -XX:permSize and -XX:maxPermSize. (See the JVM and garbage collector tuning docus from Sun for more information and google for more). Also try to enable the garbage collector log to check what happens to the perm memory in case of GCs. AFAIK the maxPermSize can be set fairly high, because it will be cut off your -Xmx setting, just when needed. We had a similar issue because the perm size was limited to/reached 64mb and at some point during runtime everything broke apart as we need about 100MB. Interesting: using the -d64 -server crashed already during Tomcat startup with too low perm size. Obviously the classes and all other perm memory code need more heap right from the beginning due to 64bit addressing. Unfortunately having not enough perm memory here can lead to out of memory exceptions although you seem to have enough free heap. ;-) Somebody at Sun forgot to offer a Java 1.4.x method to dump the free perm memory besides max, total and free heap that you could easily find out whats wrong without GC logging... Cheers, Michael Asim Alp wrote: Hello Peter, Sorry. My system config is: Windows Server 2003 Apache 2.0.49 (Win32) mod_ssl/2.0.51 OpenSSL/0.9.7d DAV/2 mod_jk/1.2.6 Tomcat 5.5.4 sun jdk 1.5.0-b64 We have a 2 node tomcat cluster each running with the -Xms128m -Xmx1024m options. We have a heavily loaded JDBC application running and our MySQL server has enough max_connections to handle our load. For now, we have Apache, one of the Tomcats and MySQL running on the same machine (2 x 3.8 Ghz Intel with 2GB of Ram). We're also using this server as a file server with RAID 5. From Task Managers performance monitor, I'm looking at the Handles (I hope I'm looking at the correct thing). Total number of handles is around 30400 (almost two times 16K). Apache is usually using about 3000, Tomcat 5000, MySQL 9000, System 2600, svchost 1000. Do these values look normal? Asim On Mon, 13 Dec 2004 17:53:35 -, Peter Crowther [EMAIL PROTECTED] wrote: From: Asim Alp [mailto:[EMAIL PROTECTED] I'm trying to solve an OOME on our Tomcat. Tomcat version? JVM version and settings? Application characteristics? Other libraries in use (eg JDBC)? We profiled our application using JProfiler and there are no memory leakages on our end. Currently, I'm focusing on some system resource problems such as file descriptors. Would this be a valid problem on Windows Server 2003? And if so, how can I change the max number of file descriptors? I suspect someone else will give a better Java solution, but I'm a Windows hack who's a relative latecomer to Java... You've got 16k to go at by default. How many are you using, according to Performance Monitor? And how many in the JVM running Tomcat? One last thing... What other resources should I investigate for this sort of OOME? http://www.sysinternals.com/ for 'handle' and Process Explorer if you suspect a resource problem on Windows. - Peter - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
OutOfMemory Errors
I'm trying to solve an OOME on our Tomcat. We profiled our application using JProfiler and there are no memory leakages on our end. Currently, I'm focusing on some system resource problems such as file descriptors. Would this be a valid problem on Windows Server 2003? And if so, how can I change the max number of file descriptors? One last thing... What other resources should I investigate for this sort of OOME? Thanks, Asim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: OutOfMemory Errors
From: Asim Alp [mailto:[EMAIL PROTECTED] I'm trying to solve an OOME on our Tomcat. Tomcat version? JVM version and settings? Application characteristics? Other libraries in use (eg JDBC)? We profiled our application using JProfiler and there are no memory leakages on our end. Currently, I'm focusing on some system resource problems such as file descriptors. Would this be a valid problem on Windows Server 2003? And if so, how can I change the max number of file descriptors? I suspect someone else will give a better Java solution, but I'm a Windows hack who's a relative latecomer to Java... You've got 16k to go at by default. How many are you using, according to Performance Monitor? And how many in the JVM running Tomcat? One last thing... What other resources should I investigate for this sort of OOME? http://www.sysinternals.com/ for 'handle' and Process Explorer if you suspect a resource problem on Windows. - Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: OutOfMemory Errors
Perhaps you just arent allocating enough memory for your application and there is no leak. As always i recommend getting a hold of jvmstat from sun and it'll give you some visual clues as to what is going on. -Original Message- From: Asim Alp [mailto:[EMAIL PROTECTED] Sent: 13 December 2004 17:47 To: Tomcat Users List Subject: OutOfMemory Errors I'm trying to solve an OOME on our Tomcat. We profiled our application using JProfiler and there are no memory leakages on our end. Currently, I'm focusing on some system resource problems such as file descriptors. Would this be a valid problem on Windows Server 2003? And if so, how can I change the max number of file descriptors? One last thing... What other resources should I investigate for this sort of OOME? Thanks, Asim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Any opinions expressed in this E-mail may be those of the individual and not necessarily the company. This E-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this E-mail in error and that any use or copying is strictly prohibited. If you have received this E-mail in error please notify the beCogent postmaster at [EMAIL PROTECTED] Unless expressly stated, opinions in this email are those of the individual sender and not beCogent Ltd. You must take full responsibility for virus checking this email and any attachments. Please note that the content of this email or any of its attachments may contain data that falls within the scope of the Data Protection Acts and that you must ensure that any handling or processing of such data by you is fully compliant with the terms and provisions of the Data Protection Act 1984 and 1998. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: OutOfMemory Errors
You probably have a resource leak in your application. You might want to run FindBugs on it: http://findbugs.sourceforge.net/ George Sexton MH Software, Inc. http://www.mhsoftware.com/ Voice: 303 438 9585 -Original Message- From: Asim Alp [mailto:[EMAIL PROTECTED] Sent: Monday, December 13, 2004 11:32 AM To: Tomcat Users List Subject: Re: OutOfMemory Errors Hello Peter, Sorry. My system config is: Windows Server 2003 Apache 2.0.49 (Win32) mod_ssl/2.0.51 OpenSSL/0.9.7d DAV/2 mod_jk/1.2.6 Tomcat 5.5.4 sun jdk 1.5.0-b64 We have a 2 node tomcat cluster each running with the -Xms128m -Xmx1024m options. We have a heavily loaded JDBC application running and our MySQL server has enough max_connections to handle our load. For now, we have Apache, one of the Tomcats and MySQL running on the same machine (2 x 3.8 Ghz Intel with 2GB of Ram). We're also using this server as a file server with RAID 5. From Task Managers performance monitor, I'm looking at the Handles (I hope I'm looking at the correct thing). Total number of handles is around 30400 (almost two times 16K). Apache is usually using about 3000, Tomcat 5000, MySQL 9000, System 2600, svchost 1000. Do these values look normal? Asim On Mon, 13 Dec 2004 17:53:35 -, Peter Crowther [EMAIL PROTECTED] wrote: From: Asim Alp [mailto:[EMAIL PROTECTED] I'm trying to solve an OOME on our Tomcat. Tomcat version? JVM version and settings? Application characteristics? Other libraries in use (eg JDBC)? We profiled our application using JProfiler and there are no memory leakages on our end. Currently, I'm focusing on some system resource problems such as file descriptors. Would this be a valid problem on Windows Server 2003? And if so, how can I change the max number of file descriptors? I suspect someone else will give a better Java solution, but I'm a Windows hack who's a relative latecomer to Java... You've got 16k to go at by default. How many are you using, according to Performance Monitor? And how many in the JVM running Tomcat? One last thing... What other resources should I investigate for this sort of OOME? http://www.sysinternals.com/ for 'handle' and Process Explorer if you suspect a resource problem on Windows. - Peter - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OutOfMemory Errors
Thank you for the suggestion. Actually, we have upgraded from JDK 1.4.x to JDK 1.5.0 hoping to solve the problem, so I doubt that it is JDK related. On Mon, 13 Dec 2004 19:38:14 -0200, Ivan F. Martinez [EMAIL PROTECTED] wrote: On Mon, 13 Dec 2004 13:31:50 -0500 Asim Alp [EMAIL PROTECTED] wrote: AA Hello Peter, AA AA Sorry. My system config is: AA AA Windows Server 2003 AA Apache 2.0.49 (Win32) mod_ssl/2.0.51 OpenSSL/0.9.7d DAV/2 AA mod_jk/1.2.6 Tomcat 5.5.4 AA sun jdk 1.5.0-b64 Have you tried with JDK 1.4.x ? I have one app that eat all memory when running on jdk 1.5.0, and works fine on 1.4.x. I did not find any memory leak in APP. I think is related with JDK 1.5.0 -- - 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]
Re: OutOfMemory Errors
On Mon, 13 Dec 2004 13:31:50 -0500 Asim Alp [EMAIL PROTECTED] wrote: AA Hello Peter, AA AA Sorry. My system config is: AA AA Windows Server 2003 AA Apache 2.0.49 (Win32) mod_ssl/2.0.51 OpenSSL/0.9.7d DAV/2 AA mod_jk/1.2.6 Tomcat 5.5.4 AA sun jdk 1.5.0-b64 Have you tried with JDK 1.4.x ? I have one app that eat all memory when running on jdk 1.5.0, and works fine on 1.4.x. I did not find any memory leak in APP. I think is related with JDK 1.5.0 -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OutOfMemory Errors
Hello Peter, Sorry. My system config is: Windows Server 2003 Apache 2.0.49 (Win32) mod_ssl/2.0.51 OpenSSL/0.9.7d DAV/2 mod_jk/1.2.6 Tomcat 5.5.4 sun jdk 1.5.0-b64 We have a 2 node tomcat cluster each running with the -Xms128m -Xmx1024m options. We have a heavily loaded JDBC application running and our MySQL server has enough max_connections to handle our load. For now, we have Apache, one of the Tomcats and MySQL running on the same machine (2 x 3.8 Ghz Intel with 2GB of Ram). We're also using this server as a file server with RAID 5. From Task Managers performance monitor, I'm looking at the Handles (I hope I'm looking at the correct thing). Total number of handles is around 30400 (almost two times 16K). Apache is usually using about 3000, Tomcat 5000, MySQL 9000, System 2600, svchost 1000. Do these values look normal? Asim On Mon, 13 Dec 2004 17:53:35 -, Peter Crowther [EMAIL PROTECTED] wrote: From: Asim Alp [mailto:[EMAIL PROTECTED] I'm trying to solve an OOME on our Tomcat. Tomcat version? JVM version and settings? Application characteristics? Other libraries in use (eg JDBC)? We profiled our application using JProfiler and there are no memory leakages on our end. Currently, I'm focusing on some system resource problems such as file descriptors. Would this be a valid problem on Windows Server 2003? And if so, how can I change the max number of file descriptors? I suspect someone else will give a better Java solution, but I'm a Windows hack who's a relative latecomer to Java... You've got 16k to go at by default. How many are you using, according to Performance Monitor? And how many in the JVM running Tomcat? One last thing... What other resources should I investigate for this sort of OOME? http://www.sysinternals.com/ for 'handle' and Process Explorer if you suspect a resource problem on Windows. - Peter - 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]
RE: OutOfMemory! Tomcat meets sudden spikes of used memory sometimes.
Hi, Thank Yoav very much. I will report my ending for the problem. Li Zhenxing No problem, I'm glad to help. These are the interesting problems, to me at least. Especially when the person working on them seems to have a good grip on things, like you do. I look forward to seeing your results / solution... Yoav Shapira http://www.yoavshapira.com This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Registry problems followed by OutOfMemory errors
Here is our configuration: Windows Server 2003 Apache 2.0.49 (Win32) mod_ssl/2.0.51 OpenSSL/0.9.7d DAV/2 mod_jk/1.2.6 Tomcat 5.5.4 sun jdk 1.5.0-b64 We have a 2 node tomcat cluster each running with the -Xms128m -Xmx1024m options. We have the following thread options set in the AJP/1.3 connector: maxThreads=1000 minSpareThreads=50 maxSpareThreads=300 And the following corresponding values in our workers.properties (same for each tomcat) worker.tomcat1.type=ajp13 worker.tomcat1.cachesize=300 worker.tomcat1.cache_timeout=60 worker.worker1.local_worker=1 worker.tomcat1.lbfactor=1 worker.tomcat1.connect_timeout = 1000 worker.tomcat1.prepost_timeout = 1000 worker.tomcat1.reply_timeout = 7000 ... worker.loadbalancer.local_worker_only=0 We have a heavily loaded database application running. Same application runs on about 180 different virtual hosts on each Tomcat. We did profiling with JProfile and couldn't find any memory leaks in our application. Each Tomcat works perfect for about 8 to 10 hours, then all of a sudden, they start hanging (not necessarily at the same time). We monitor our heap memory very closely and we usually have enough FREE memory (more than 25%) when the following errors occur: First, we get a couple of SEVERE registering errors: record date2004-12-09T18:19:51/date millis1102634391333/millis sequence270/sequence loggerorg.apache.commons.modeler.Registry/logger levelSEVERE/level classorg.apache.commons.modeler.Registry/class methodregisterComponent/method thread44/thread messageError registering Catalina:type=RequestProcessor,worker=jk-8009,name=JkRequest2291/ message exception messagejavax.management.InstanceAlreadyExistsException: Catalina:type=RequestProcessor,worker=jk-8009,name=JkRequest2291/ message frame classcom.sun.jmx.mbeanserver.RepositorySupport/class methodaddMBean/method line452/line /frame frame classcom.sun.jmx.interceptor.DefaultMBeanServerInterceptor/class methodinternal_addObject/method line1410/line /frame /exception /record record date2004-12-09T18:19:51/date millis1102634391333/millis sequence271/sequence loggerorg.apache.jk.common.ChannelSocket/logger levelWARNING/level classorg.apache.jk.common.ChannelSocket/class methodregisterRequest/method thread44/thread messageError registering request/message /record Followed by a couple of java.lang.OutOfMemoryError: PermGen space messages record date2004-12-09T21:48:25/date millis1102646905849/millis sequence294/sequence loggerStandardWrapper[/apps:jsp]/logger levelSEVERE/level classorg.apache.catalina.core.StandardWrapperValve/class methodinvoke/method thread47/thread messageServlet.service() for servlet jsp threw exception/message exception messagejava.lang.OutOfMemoryError: PermGen space/message /exception /record ... Followed by HUNDREDS (basically for each thread) of Error unregistering mbean messages record date2004-12-09T21:53:29/date millis1102647209630/millis sequence302/sequence loggerorg.apache.commons.modeler.Registry/logger levelSEVERE/level classorg.apache.commons.modeler.Registry/class methodunregisterComponent/method thread20/thread messageError unregistering mbean /message exception messagejavax.management.RuntimeOperationsException: Object name cannot be null/message frame classcom.sun.jmx.interceptor.DefaultMBeanServerInterceptor/class methodisRegistered/method line545/line /frame frame classcom.sun.jmx.mbeanserver.JmxMBeanServer/class methodisRegistered/method line619/line /frame frame classorg.apache.commons.modeler.Registry/class methodunregisterComponent/method line642/line /frame ... /exception /record Any ideas? Is this something to do with our thread counts (maxThreads=1000 minSpareThreads=50 maxSpareThreads=300)? If so, how can we determine these numbers for fastest performance. We get about 5 hits every second and we want our Tomcats to serve static files as well (such as image files), so we want to make sure that we have enough threads. It's very important for our pages to load fast on the client side. Thank you very much! Any help would be greatly appreciated! Asim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Registry problems followed by OutOfMemory errors
Hi, Do you need JMX request registration? If not, turn it off by setting it to false in the configuration file. That'll save you some memory by itself. Your OOME is the root cause, so if you fix that the hundreds of others errors will likely go away. The OOME, in turn, is probably caused not because you're out of heap memory, but because you're out of another resource, such as file descriptors or threads. Yoav Shapira http://www.yoavshapira.com -Original Message- From: Asim Alp [mailto:[EMAIL PROTECTED] Sent: Friday, December 10, 2004 10:59 AM To: Tomcat Users List Subject: Registry problems followed by OutOfMemory errors Here is our configuration: Windows Server 2003 Apache 2.0.49 (Win32) mod_ssl/2.0.51 OpenSSL/0.9.7d DAV/2 mod_jk/1.2.6 Tomcat 5.5.4 sun jdk 1.5.0-b64 We have a 2 node tomcat cluster each running with the -Xms128m -Xmx1024m options. We have the following thread options set in the AJP/1.3 connector: maxThreads=1000 minSpareThreads=50 maxSpareThreads=300 And the following corresponding values in our workers.properties (same for each tomcat) worker.tomcat1.type=ajp13 worker.tomcat1.cachesize=300 worker.tomcat1.cache_timeout=60 worker.worker1.local_worker=1 worker.tomcat1.lbfactor=1 worker.tomcat1.connect_timeout = 1000 worker.tomcat1.prepost_timeout = 1000 worker.tomcat1.reply_timeout = 7000 ... worker.loadbalancer.local_worker_only=0 We have a heavily loaded database application running. Same application runs on about 180 different virtual hosts on each Tomcat. We did profiling with JProfile and couldn't find any memory leaks in our application. Each Tomcat works perfect for about 8 to 10 hours, then all of a sudden, they start hanging (not necessarily at the same time). We monitor our heap memory very closely and we usually have enough FREE memory (more than 25%) when the following errors occur: First, we get a couple of SEVERE registering errors: record date2004-12-09T18:19:51/date millis1102634391333/millis sequence270/sequence loggerorg.apache.commons.modeler.Registry/logger levelSEVERE/level classorg.apache.commons.modeler.Registry/class methodregisterComponent/method thread44/thread messageError registering Catalina:type=RequestProcessor,worker=jk-8009,name=JkRequest2291/ message exception messagejavax.management.InstanceAlreadyExistsException: Catalina:type=RequestProcessor,worker=jk-8009,name=JkRequest2291/ message frame classcom.sun.jmx.mbeanserver.RepositorySupport/class methodaddMBean/method line452/line /frame frame classcom.sun.jmx.interceptor.DefaultMBeanServerInterceptor/class methodinternal_addObject/method line1410/line /frame /exception /record record date2004-12-09T18:19:51/date millis1102634391333/millis sequence271/sequence loggerorg.apache.jk.common.ChannelSocket/logger levelWARNING/level classorg.apache.jk.common.ChannelSocket/class methodregisterRequest/method thread44/thread messageError registering request/message /record Followed by a couple of java.lang.OutOfMemoryError: PermGen space messages record date2004-12-09T21:48:25/date millis1102646905849/millis sequence294/sequence loggerStandardWrapper[/apps:jsp]/logger levelSEVERE/level classorg.apache.catalina.core.StandardWrapperValve/class methodinvoke/method thread47/thread messageServlet.service() for servlet jsp threw exception/message exception messagejava.lang.OutOfMemoryError: PermGen space/message /exception /record ... Followed by HUNDREDS (basically for each thread) of Error unregistering mbean messages record date2004-12-09T21:53:29/date millis1102647209630/millis sequence302/sequence loggerorg.apache.commons.modeler.Registry/logger levelSEVERE/level classorg.apache.commons.modeler.Registry/class methodunregisterComponent/method thread20/thread messageError unregistering mbean /message exception messagejavax.management.RuntimeOperationsException: Object name cannot be null/message frame classcom.sun.jmx.interceptor.DefaultMBeanServerInterceptor/class methodisRegistered/method line545/line /frame frame classcom.sun.jmx.mbeanserver.JmxMBeanServer/class methodisRegistered/method line619/line /frame frame classorg.apache.commons.modeler.Registry/class methodunregisterComponent/method line642/line /frame ... /exception /record Any ideas? Is this something to do with our thread counts (maxThreads=1000 minSpareThreads=50 maxSpareThreads=300)? If so, how can we determine these numbers for fastest performance. We get about 5 hits every second and we want our Tomcats to serve static files as well (such as image files), so we want to make sure that we have enough threads. It's very important for our pages to load fast on the client side. Thank you very much! Any help would be greatly appreciated! Asim
Re: Registry problems followed by OutOfMemory errors
Thanks for the quick reply! How can I turn off JMX request registration? I tried to find it in the Tomcat documentation, but all I could find was the MBean Descriptor How To which wasn't very helpful. I doubt that we need it. I will look into the resource problem. I doubt that we're running out of threads, because 1000 of them should be more than enough. Another resource problem could be the number of SQL connections, but on our SQL Side (MySQL), max_connections is set to 5000 which is about 7 times more than we need. Number of file descriptors might be a problem. For each web application, we have to load properties files and these files are automatically checked once every minute for possible updates. How can I configure the number of file descriptors? Thank you very much! Asim On Dec 10, 2004, at 11:02 AM, Shapira, Yoav wrote: Hi, Do you need JMX request registration? If not, turn it off by setting it to false in the configuration file. That'll save you some memory by itself. Your OOME is the root cause, so if you fix that the hundreds of others errors will likely go away. The OOME, in turn, is probably caused not because you're out of heap memory, but because you're out of another resource, such as file descriptors or threads. Yoav Shapira http://www.yoavshapira.com -Original Message- From: Asim Alp [mailto:[EMAIL PROTECTED] Sent: Friday, December 10, 2004 10:59 AM To: Tomcat Users List Subject: Registry problems followed by OutOfMemory errors Here is our configuration: Windows Server 2003 Apache 2.0.49 (Win32) mod_ssl/2.0.51 OpenSSL/0.9.7d DAV/2 mod_jk/1.2.6 Tomcat 5.5.4 sun jdk 1.5.0-b64 We have a 2 node tomcat cluster each running with the -Xms128m -Xmx1024m options. We have the following thread options set in the AJP/1.3 connector: maxThreads=1000 minSpareThreads=50 maxSpareThreads=300 And the following corresponding values in our workers.properties (same for each tomcat) worker.tomcat1.type=ajp13 worker.tomcat1.cachesize=300 worker.tomcat1.cache_timeout=60 worker.worker1.local_worker=1 worker.tomcat1.lbfactor=1 worker.tomcat1.connect_timeout = 1000 worker.tomcat1.prepost_timeout = 1000 worker.tomcat1.reply_timeout = 7000 ... worker.loadbalancer.local_worker_only=0 We have a heavily loaded database application running. Same application runs on about 180 different virtual hosts on each Tomcat. We did profiling with JProfile and couldn't find any memory leaks in our application. Each Tomcat works perfect for about 8 to 10 hours, then all of a sudden, they start hanging (not necessarily at the same time). We monitor our heap memory very closely and we usually have enough FREE memory (more than 25%) when the following errors occur: First, we get a couple of SEVERE registering errors: record date2004-12-09T18:19:51/date millis1102634391333/millis sequence270/sequence loggerorg.apache.commons.modeler.Registry/logger levelSEVERE/level classorg.apache.commons.modeler.Registry/class methodregisterComponent/method thread44/thread messageError registering Catalina:type=RequestProcessor,worker=jk-8009,name=JkRequest2291/ message exception messagejavax.management.InstanceAlreadyExistsException: Catalina:type=RequestProcessor,worker=jk-8009,name=JkRequest2291/ message frame classcom.sun.jmx.mbeanserver.RepositorySupport/class methodaddMBean/method line452/line /frame frame classcom.sun.jmx.interceptor.DefaultMBeanServerInterceptor/class methodinternal_addObject/method line1410/line /frame /exception /record record date2004-12-09T18:19:51/date millis1102634391333/millis sequence271/sequence loggerorg.apache.jk.common.ChannelSocket/logger levelWARNING/level classorg.apache.jk.common.ChannelSocket/class methodregisterRequest/method thread44/thread messageError registering request/message /record Followed by a couple of java.lang.OutOfMemoryError: PermGen space messages record date2004-12-09T21:48:25/date millis1102646905849/millis sequence294/sequence loggerStandardWrapper[/apps:jsp]/logger levelSEVERE/level classorg.apache.catalina.core.StandardWrapperValve/class methodinvoke/method thread47/thread messageServlet.service() for servlet jsp threw exception/message exception messagejava.lang.OutOfMemoryError: PermGen space/message /exception /record ... Followed by HUNDREDS (basically for each thread) of Error unregistering mbean messages record date2004-12-09T21:53:29/date millis1102647209630/millis sequence302/sequence loggerorg.apache.commons.modeler.Registry/logger levelSEVERE/level classorg.apache.commons.modeler.Registry/class methodunregisterComponent/method thread20/thread messageError unregistering mbean /message exception messagejavax.management.RuntimeOperationsException: Object name cannot be null/message frame classcom.sun.jmx.interceptor.DefaultMBeanServerInterceptor/class methodisRegistered/method line545/line /frame frame
Re: Registry problems followed by OutOfMemory errors
Asim Alp [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Thanks for the quick reply! How can I turn off JMX request registration? I tried to find it in the Tomcat documentation, but all I could find was the MBean Descriptor How To which wasn't very helpful. I doubt that we need it. Set request.registerRequests=false on the Connector. I will look into the resource problem. I doubt that we're running out of threads, because 1000 of them should be more than enough. Another resource problem could be the number of SQL connections, but on our SQL Side (MySQL), max_connections is set to 5000 which is about 7 times more than we need. Number of file descriptors might be a problem. For each web application, we have to load properties files and these files are automatically checked once every minute for possible updates. How can I configure the number of file descriptors? Thank you very much! Asim On Dec 10, 2004, at 11:02 AM, Shapira, Yoav wrote: Hi, Do you need JMX request registration? If not, turn it off by setting it to false in the configuration file. That'll save you some memory by itself. Your OOME is the root cause, so if you fix that the hundreds of others errors will likely go away. The OOME, in turn, is probably caused not because you're out of heap memory, but because you're out of another resource, such as file descriptors or threads. Yoav Shapira http://www.yoavshapira.com -Original Message- From: Asim Alp [mailto:[EMAIL PROTECTED] Sent: Friday, December 10, 2004 10:59 AM To: Tomcat Users List Subject: Registry problems followed by OutOfMemory errors Here is our configuration: Windows Server 2003 Apache 2.0.49 (Win32) mod_ssl/2.0.51 OpenSSL/0.9.7d DAV/2 mod_jk/1.2.6 Tomcat 5.5.4 sun jdk 1.5.0-b64 We have a 2 node tomcat cluster each running with the -Xms128m -Xmx1024m options. We have the following thread options set in the AJP/1.3 connector: maxThreads=1000 minSpareThreads=50 maxSpareThreads=300 And the following corresponding values in our workers.properties (same for each tomcat) worker.tomcat1.type=ajp13 worker.tomcat1.cachesize=300 worker.tomcat1.cache_timeout=60 worker.worker1.local_worker=1 worker.tomcat1.lbfactor=1 worker.tomcat1.connect_timeout = 1000 worker.tomcat1.prepost_timeout = 1000 worker.tomcat1.reply_timeout = 7000 ... worker.loadbalancer.local_worker_only=0 We have a heavily loaded database application running. Same application runs on about 180 different virtual hosts on each Tomcat. We did profiling with JProfile and couldn't find any memory leaks in our application. Each Tomcat works perfect for about 8 to 10 hours, then all of a sudden, they start hanging (not necessarily at the same time). We monitor our heap memory very closely and we usually have enough FREE memory (more than 25%) when the following errors occur: First, we get a couple of SEVERE registering errors: record date2004-12-09T18:19:51/date millis1102634391333/millis sequence270/sequence loggerorg.apache.commons.modeler.Registry/logger levelSEVERE/level classorg.apache.commons.modeler.Registry/class methodregisterComponent/method thread44/thread messageError registering Catalina:type=RequestProcessor,worker=jk-8009,name=JkRequest2291/ message exception messagejavax.management.InstanceAlreadyExistsException: Catalina:type=RequestProcessor,worker=jk-8009,name=JkRequest2291/ message frame classcom.sun.jmx.mbeanserver.RepositorySupport/class methodaddMBean/method line452/line /frame frame classcom.sun.jmx.interceptor.DefaultMBeanServerInterceptor/class methodinternal_addObject/method line1410/line /frame /exception /record record date2004-12-09T18:19:51/date millis1102634391333/millis sequence271/sequence loggerorg.apache.jk.common.ChannelSocket/logger levelWARNING/level classorg.apache.jk.common.ChannelSocket/class methodregisterRequest/method thread44/thread messageError registering request/message /record Followed by a couple of java.lang.OutOfMemoryError: PermGen space messages record date2004-12-09T21:48:25/date millis1102646905849/millis sequence294/sequence loggerStandardWrapper[/apps:jsp]/logger levelSEVERE/level classorg.apache.catalina.core.StandardWrapperValve/class methodinvoke/method thread47/thread messageServlet.service() for servlet jsp threw exception/message exception messagejava.lang.OutOfMemoryError: PermGen space/message /exception /record ... Followed by HUNDREDS (basically for each thread) of Error unregistering mbean messages record date2004-12-09T21:53:29/date millis1102647209630/millis sequence302/sequence loggerorg.apache.commons.modeler.Registry/logger levelSEVERE/level classorg.apache.commons.modeler.Registry/class methodunregisterComponent/method thread20/thread messageError unregistering mbean /message exception
RE: OutOfMemory! Tomcat meets sudden spikes of used memory sometimes.
Hi, I think it is a obvious memory leak because the number of request threads doesn't increase and the app hits just is normal when the inflexion of gc figure appreas. So there is a constant load and constant memory usage for a couple of days, and then under the same load the memory usage spikes up? No other external parameters change, e.g. the database going down? It should been given max memory as possible to avoid JVM increases heap progressively when the server machine only runs tomcat. I think all heavy load app should set two parameter equal. I disagree. Pretty much no performance tuning criterion applies to all heavy load apps. And the practice of setting -Xms = -Xmx is outdated, as recent JDKs are very good at rapidly allocating large chunks of the heap on-demand. However, it's your app and your call, and it sounds like you've given it some thought, which is good. I have 2~3 hundreds JSPs that almost be requested everyday. And they don't change, right? So they don't need to be recompiled by Jasper. Does one JSP has memory leak at a special situation? Or one JSP running at a special situation causes tomcat leak? Can you correlate your access log (assuming it's enabled: if not, enable it) to the increase in memory usage Maybe it will show one particular page being requested when the memory spikes up. Yoav Shapira http://www.yoavshapira.com This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OutOfMemory! Tomcat meets sudden spikes of used memory sometimes.
On Thu, 9 Dec 2004 08:30:26 -0500, Shapira, Yoav [EMAIL PROTECTED] wrote: So there is a constant load and constant memory usage for a couple of days, and then under the same load the memory usage spikes up? No other external parameters change, e.g. the database going down? I don't find other external parameters change. And the app gets right, once restart tomcat! And they don't change, right? So they don't need to be recompiled by Jasper. Yes, they don't change. Can you correlate your access log (assuming it's enabled: if not, enable it) to the increase in memory usage Maybe it will show one particular page being requested when the memory spikes up. I have already correlated all JSP. But find nothing. All the access JSPs during memory spiking up are normal pages. Those are visited everyday. Now I guess maybe some parameters of one JSP are wrong. I don't correlate every access URL. I am tring to finish this work. You know, this is big work because the access URL is more than 10 thousands within a few minutes. Thank Yoav very much. I will report my ending for the problem. Li Zhenxing - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
OutOfMemory! Tomcat meets sudden spikes of used memory sometimes.
Hi folks, I am puzzled by the situation that Tomcat 4.1.31 meets sudden spikes of used memory sometimes. Then it will increase to throw OutOfMemory Exception and tomcat is hanging. Those memory spikes appear in my Web application for a long time. The odd thing is that it does not seem to progressively go up but rather spike up with each next full GC will clean less objects out. This is three pictures of the gc log. http://my.sme.cn/jsp/main/memoryleak.png http://my.sme.cn/jsp/main/memoryleak2.png http://my.sme.cn/jsp/main/memoryleak3.png I used HPjtune tool to watch the gc log. System using windows 2000 server, 2*CPU, 2G memory, JSDK 1.4.2_05, tomcat 4.1.31, And set -Xms1250m -Xmx1250m -server -XX:+UseParallelGC -Xloggc:D:\tomcat\logs\gc.log At first, I doubt if my app program has memory leak. But the application only runs by JSPs and javabeans.(I abandon using DBCP pool and any thread operation because of the memory leak.) I think simple JSPs can't cause the memory spike. I have a monitor.jsp to show my application status. http://my.sme.cn/jsp/main/monitor.jsp The WebSite uses normally below 100M memory heap through my monitor.jsp. It can run a few days, or a few hours before the spike appears. It is irregular. I read the access_log and want to find answer. But I can't find any clue. Then, I think tomcat 4.1.* has some bugs causing the memory leak. I upgraded my application to tomcat 5.0.18, but I met same thing. The WebSite's hits is more than 200,000 per day. I try to use OptimizeIt 6 profile to watch memory status, but OptimizeIt always exits after runs 2~3 hours. I guess this program maybe need using progressive memory of system to log things and analyze those when I notice Optimizeit used 1.6G system memory.(and OptimizeIt 6 profile only runs under tomcat 4.1.*! So I return to tomcat 4.1.31) I don't know how to cause the thing and how to find solution. Any suggestion is appreciated. Thanks. Li Zhenxing - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: OutOfMemory! Tomcat meets sudden spikes of used memory sometimes.
The fact that you have the same symptons in tomcat 4 and in 5 points towards your application as being the culprit. Is there any reason why you chose tomcat 5.0.18 instead of one of the many newer releases? I would find another profiler that works with both and try your tests again. Ta Matt -Original Message- From: Li Zhenxing [mailto:[EMAIL PROTECTED] Sent: 08 December 2004 13:47 To: [EMAIL PROTECTED] Subject: OutOfMemory! Tomcat meets sudden spikes of used memory sometimes. Hi folks, I am puzzled by the situation that Tomcat 4.1.31 meets sudden spikes of used memory sometimes. Then it will increase to throw OutOfMemory Exception and tomcat is hanging. Those memory spikes appear in my Web application for a long time. The odd thing is that it does not seem to progressively go up but rather spike up with each next full GC will clean less objects out. This is three pictures of the gc log. http://my.sme.cn/jsp/main/memoryleak.png http://my.sme.cn/jsp/main/memoryleak2.png http://my.sme.cn/jsp/main/memoryleak3.png I used HPjtune tool to watch the gc log. System using windows 2000 server, 2*CPU, 2G memory, JSDK 1.4.2_05, tomcat 4.1.31, And set -Xms1250m -Xmx1250m -server -XX:+UseParallelGC -Xloggc:D:\tomcat\logs\gc.log At first, I doubt if my app program has memory leak. But the application only runs by JSPs and javabeans.(I abandon using DBCP pool and any thread operation because of the memory leak.) I think simple JSPs can't cause the memory spike. I have a monitor.jsp to show my application status. http://my.sme.cn/jsp/main/monitor.jsp The WebSite uses normally below 100M memory heap through my monitor.jsp. It can run a few days, or a few hours before the spike appears. It is irregular. I read the access_log and want to find answer. But I can't find any clue. Then, I think tomcat 4.1.* has some bugs causing the memory leak. I upgraded my application to tomcat 5.0.18, but I met same thing. The WebSite's hits is more than 200,000 per day. I try to use OptimizeIt 6 profile to watch memory status, but OptimizeIt always exits after runs 2~3 hours. I guess this program maybe need using progressive memory of system to log things and analyze those when I notice Optimizeit used 1.6G system memory.(and OptimizeIt 6 profile only runs under tomcat 4.1.*! So I return to tomcat 4.1.31) I don't know how to cause the thing and how to find solution. Any suggestion is appreciated. Thanks. Li Zhenxing - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Any opinions expressed in this E-mail may be those of the individual and not necessarily the company. This E-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this E-mail in error and that any use or copying is strictly prohibited. If you have received this E-mail in error please notify the beCogent postmaster at [EMAIL PROTECTED] Unless expressly stated, opinions in this email are those of the individual sender and not beCogent Ltd. You must take full responsibility for virus checking this email and any attachments. Please note that the content of this email or any of its attachments may contain data that falls within the scope of the Data Protection Acts and that you must ensure that any handling or processing of such data by you is fully compliant with the terms and provisions of the Data Protection Act 1984 and 1998. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: OutOfMemory! Tomcat meets sudden spikes of used memory sometimes.
Hi, Besides what Dale said, which is true, I'd like to point out a couple of other additional things. Those memory spikes appear in my Web application for a long time. The odd When a spike appears for a long time it's not a spike: it's the steady state. This is three pictures of the gc log. http://my.sme.cn/jsp/main/memoryleak.png http://my.sme.cn/jsp/main/memoryleak2.png http://my.sme.cn/jsp/main/memoryleak3.png Please don't jump to determine it's a memory leak just because more memory is used. I used HPjtune tool to watch the gc log. System using windows 2000 server, 2*CPU, 2G memory, JSDK 1.4.2_05, tomcat 4.1.31, And set -Xms1250m -Xmx1250m -server -XX:+UseParallelGC - Xloggc:D:\tomcat\logs\gc.log So you're setting the heap size to a constant 1250MB. How can there be big jumps all over the place? At first, I doubt if my app program has memory leak. But the application only runs by JSPs and javabeans.(I abandon using DBCP pool and any thread operation because of the memory leak.) I think simple JSPs can't cause the memory spike. I have a monitor.jsp to show my application status. http://my.sme.cn/jsp/main/monitor.jsp I bet your app is more likely than Tomcat to have a leak ;) Simple JSPs can cause memory spikes, as can simple servlets. DBCP and threads do NOT necessarily cause increased memory usage. The WebSite uses normally below 100M memory heap through my monitor.jsp. It can run a few days, or a few hours before the spike appears. It is irregular. I read the access_log and want to find answer. But I can't find any clue. Perhaps it's high load causing the spike? That would be normal and expected. The WebSite's hits is more than 200,000 per day. I try to use OptimizeIt 6 profile to watch memory status, but OptimizeIt always exits after runs 2~3 hours. I guess this program maybe need using progressive memory of system to log things and analyze those when I notice Optimizeit used 1.6G system memory.(and OptimizeIt 6 profile only runs under tomcat 4.1.*! So I return to tomcat 4.1.31) Yes, OptimizeIt, like other profilers, can routinely use an order of magnitude more memory than your app itself. I don't know how to cause the thing and how to find solution. Any suggestion is appreciated. Thanks. Get a test system, put your app on it, run it with a profiler, and simulate load using a test tool of your choice, e.g. JMeter, ab, wget, grinder, whatever. Then see where memory is retained during your spikes. Yoav Shapira http://www.yoavshapira.com This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OutOfMemory! Tomcat meets sudden spikes of used memory sometimes.
On Wed, 8 Dec 2004 09:10:02 -0500, Shapira, Yoav [EMAIL PROTECTED] wrote: When a spike appears for a long time it's not a spike: it's the steady state. Yes, it's the steady state. I just aim at the gc figure, the spike. Maybe this word don't discribes the figure exactly. I am sorry for my English words. Please don't jump to determine it's a memory leak just because more memory is used. I think it is a obvious memory leak because the number of request threads doesn't increase and the app hits just is normal when the inflexion of gc figure appreas. The question only is caused by my app, or tomcat. So you're setting the heap size to a constant 1250MB. How can there be big jumps all over the place? It should been given max memory as possible to avoid JVM increases heap progressively when the server machine only runs tomcat. I think all heavy load app should set two parameter equal. I bet your app is more likely than Tomcat to have a leak ;) Simple JSPs can cause memory spikes, as can simple servlets. DBCP and threads do NOT necessarily cause increased memory usage. It is probably that my app has a leak. I agree. But every JSP has been visited during four days of system in order. Why to appear spike at fifth day? I have 2~3 hundreds JSPs that almost be requested everyday. Does one JSP has memory leak at a special situation? Or one JSP running at a special situation causes tomcat leak? Get a test system, put your app on it, run it with a profiler, and simulate load using a test tool of your choice, e.g. JMeter, ab, wget, grinder, whatever. Then see where memory is retained during your spikes. Thanks for the advice. and thanks for Dale's suggustion. I will try to profile heap through -Xrunhprof and other tools. Li Zhenxing - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: OutOfMemory exceptions
I read in another thread about setting up one Tomcat instance per host. Is that something you'd recommend doing? At least then a redeploy wouldn't affect other webapps running on that same host... Maybe this should be another thread if it gets much attention. -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
OutOfMemory exceptions
All: I've seen a few threads regarding the OutOfMemory problems. Has it been decided that reloading webapps is one of the causes of this? And, if so, would an undeploy and a new deploy fix that issue? Thanks. -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: OutOfMemory exceptions
Hi, I've seen a few threads regarding the OutOfMemory problems. Has it been decided that reloading webapps is one of the causes of this? No, and such a decision could never be made. And, if so, would an undeploy and a new deploy fix that issue? No. Yoav This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: OutOfMemory exceptions
In our case we can certainly say that continued reloading of webapps caused by class reloading in the development environment does cause out of memory - however we use statics a fair amount that are not always reclaimed although we try to release those using a context listener as much as possible. However, our production server experiences no out of memory error ever, because when we redeploy a web application build, we schedule system downtime and restart tomcat completely. no hot deploy or class reloading is allowed on our production server. I think it depends much on how you program as to whether you reach out of memory with reloading but I am no expert in this area by any means. Allistair. -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: 23 November 2004 14:05 To: Tomcat Users List Subject: RE: OutOfMemory exceptions Hi, I've seen a few threads regarding the OutOfMemory problems. Has it been decided that reloading webapps is one of the causes of this? No, and such a decision could never be made. And, if so, would an undeploy and a new deploy fix that issue? No. Yoav This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLUE --- QAS Ltd. Developers of QuickAddress Software a href=http://www.qas.com;www.qas.com/a Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- /FONT - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: OutOfMemory exceptions
On Tue, 2004-11-23 at 09:05, Shapira, Yoav wrote: No, and such a decision could never be made. OK. So, reloading webapps should clean up items in memory consumed by that particular webapp, then? Do you know of a good memory profiler that can be run while webapps are up and return to me what each webapp is using? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: OutOfMemory exceptions
using a profiler with live systems is not good because of the amount of info it dumps from the jvm. use something like Quest JProfiler or others to test your consumption in the development environment. -Original Message- From: Ryan Daly [mailto:[EMAIL PROTECTED] Sent: 23 November 2004 14:12 To: Tomcat Users List Subject: RE: OutOfMemory exceptions On Tue, 2004-11-23 at 09:05, Shapira, Yoav wrote: No, and such a decision could never be made. OK. So, reloading webapps should clean up items in memory consumed by that particular webapp, then? Do you know of a good memory profiler that can be run while webapps are up and return to me what each webapp is using? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLUE --- QAS Ltd. Developers of QuickAddress Software a href=http://www.qas.com;www.qas.com/a Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- /FONT - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: OutOfMemory exceptions
Hi, OK. So, reloading webapps should clean up items in memory consumed by that particular webapp, then? Yes and no. You are vastly oversimplifying the real world here. It's extremely difficult to come up with a webapp that can truly be reloaded without a memory loss. Do you know of a good memory profiler that can be run while webapps are up and return to me what each webapp is using? No, I don't, because Java's heap cannot be split up that way without incurring 1-2 orders of magnitude of overhead. I know of good profilers and use them regularly, but none at this point can do the above in production without bringing even huge systems to a crawl. Yoav This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: OutOfMemory exceptions
On Tue, 2004-11-23 at 09:17, Shapira, Yoav wrote: Yes and no. You are vastly oversimplifying the real world here. It's extremely difficult to come up with a webapp that can truly be reloaded without a memory loss. Would undeploying the webapp follow the same route (meaning some memory loss)? No, I don't, because Java's heap cannot be split up that way without incurring 1-2 orders of magnitude of overhead. I know of good profilers and use them regularly, but none at this point can do the above in production without bringing even huge systems to a crawl. What profilers do you use? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: OutOfMemory exceptions
Hi, Would undeploying the webapp follow the same route (meaning some memory loss)? Undeploying without redeploying should always reduce memory usage. But it won't take away all the memory used by the app most likely. What profilers do you use? I like OptimizeIt. JProbe is good too, as are several others. A lot of it is learning how to use one and then using it in real-life examples. It's great experience. Yoav This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OutOfMemory exceptions
On Tuesday 23 November 2004 16:03, Ryan Daly wrote: All: Hi, I've seen a few threads regarding the OutOfMemory problems. Has it been decided that reloading webapps is one of the causes of this? And, if so, would an undeploy and a new deploy fix that issue? Check the memory usage of your Tomcat server using the manager application. Should be under the Server Status option. This will give you a line something like this: JVM Free memory: 1017.68 MB Total memory: 1023.93 MB Max memory: 2047.93 MB Normally the JVM is set up to only use 64MB of memory by default. Add the following line to your catalina.sh file (Unix/Linux): CATALINA_OPTS=-Xincgc -Xms1024m -Xmx2048m Or add the following line to your catalina.bat fil (Windows): set CATALINA_OPTS=-Xincgc -Xms1024m -Xmx2048m I put this just under the JAVADIR line in that file (which is line 50 in my file). Restarted tomcat and all my memory messages went away. Thanks. -- Q -- Quinton Delpeche Internal Systems Developer Softline VIP Telephone: +27 12 420 7000 Direct:+27 12 420 7007 Facsimile: +27 12 420 7344 http://www.vippayroll.co.za/ What good is a ticket to the good life, if you can't find the entrance? pgpDxVxigWlXo.pgp Description: PGP signature
RE: OutOfMemory errors compiling JSPs on 5.0.16 and 5.5.4
I have a copy of the old jvmstat if you'd like me to email it to you direct? -Original Message- From: Kevin A. Burton [mailto:[EMAIL PROTECTED] Sent: 15 November 2004 19:51 To: Tomcat Users List Subject: Re: OutOfMemory errors compiling JSPs on 5.0.16 and 5.5.4 Dale, Matt wrote: I've not been following this thread but my guess would be that you are running out of space in the permanent generation of the heap. Get a hold of jvmstat from sun and run visualgc on your JVM, it should become obvious then which pool is running out of space. God! How pathetic is this: http://java.sun.com/performance/jvmstat/#Download This distribution of the jvmstat tools requires J2SE 5.0 with the HotSpot JVM. So now I have to upgrade all our VMs to JDK 5.0 even though earlier versions of jvmstat supported JDK 1.4. Brilliant... who's the marketing genius that though of this one!? ... and of course they don't link to archival versions. The SUN has set my friends ;-) Kevin -- Use Rojo (RSS/Atom aggregator). Visit http://rojo.com. Ask me for an invite! Also see irc.freenode.net #rojo if you want to chat. Rojo is Hiring! - http://www.rojonetworks.com/JobsAtRojo.html If you're interested in RSS, Weblogs, Social Networking, etc... then you should work for Rojo! If you recommend someone and we hire them you'll get a free iPod! Kevin A. Burton, Location - San Francisco, CA AIM/YIM - sfburtonator, Web - http://peerfear.org/ GPG fingerprint: 5FB2 F3E2 760E 70A8 6174 D393 E84D 8D04 99F1 4412 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Any opinions expressed in this E-mail may be those of the individual and not necessarily the company. This E-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this E-mail in error and that any use or copying is strictly prohibited. If you have received this E-mail in error please notify the beCogent postmaster at [EMAIL PROTECTED] Unless expressly stated, opinions in this email are those of the individual sender and not beCogent Ltd. You must take full responsibility for virus checking this email and any attachments. Please note that the content of this email or any of its attachments may contain data that falls within the scope of the Data Protection Acts and that you must ensure that any handling or processing of such data by you is fully compliant with the terms and provisions of the Data Protection Act 1984 and 1998. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OutOfMemory errors compiling JSPs on 5.0.16 and 5.5.4
Remy Maucherat wrote: On Sat, 13 Nov 2004 17:30:38 -0800, Kevin A. Burton [EMAIL PROTECTED] wrote: Remy Maucherat wrote: On Fri, 12 Nov 2004 17:17:28 -0800, Kevin A. Burton [EMAIL PROTECTED] wrote: - For all my JSPs I fetch them with the URL foo.jsp?jsp_precompile=true to trigger precompilation How many JSPs must be compiled to cause problems ? About 50 or so... it changes every time. Sometimes I have to trigger a precompile twice. I don't quite understand in which cases problems occur: - if you ?jsp_precompile=true 50 times for the same JSP ? - if you ?jsp_precompile=true for 50 different JSPs ? - if you access normally 50 different JSPs (triggering compilation for each one) ? I would understand from your description only the second one is an issue. Can you confirm this ? Yes... I use #2 I trigger a ?jsp_precompile=true for each one of my JSPs and we have around 300-400 ... Around 100 or so it will run out of memory. Kevin -- Use Rojo (RSS/Atom aggregator). Visit http://rojo.com. Ask me for an invite! Also see irc.freenode.net #rojo if you want to chat. Rojo is Hiring! - http://www.rojonetworks.com/JobsAtRojo.html If you're interested in RSS, Weblogs, Social Networking, etc... then you should work for Rojo! If you recommend someone and we hire them you'll get a free iPod! Kevin A. Burton, Location - San Francisco, CA AIM/YIM - sfburtonator, Web - http://peerfear.org/ GPG fingerprint: 5FB2 F3E2 760E 70A8 6174 D393 E84D 8D04 99F1 4412
Re: OutOfMemory errors compiling JSPs on 5.0.16 and 5.5.4
Dale, Matt wrote: I've not been following this thread but my guess would be that you are running out of space in the permanent generation of the heap. Get a hold of jvmstat from sun and run visualgc on your JVM, it should become obvious then which pool is running out of space. God! How pathetic is this: http://java.sun.com/performance/jvmstat/#Download This distribution of the jvmstat tools requires J2SE 5.0 with the HotSpot JVM. So now I have to upgrade all our VMs to JDK 5.0 even though earlier versions of jvmstat supported JDK 1.4. Brilliant... who's the marketing genius that though of this one!? ... and of course they don't link to archival versions. The SUN has set my friends ;-) Kevin -- Use Rojo (RSS/Atom aggregator). Visit http://rojo.com. Ask me for an invite! Also see irc.freenode.net #rojo if you want to chat. Rojo is Hiring! - http://www.rojonetworks.com/JobsAtRojo.html If you're interested in RSS, Weblogs, Social Networking, etc... then you should work for Rojo! If you recommend someone and we hire them you'll get a free iPod! Kevin A. Burton, Location - San Francisco, CA AIM/YIM - sfburtonator, Web - http://peerfear.org/ GPG fingerprint: 5FB2 F3E2 760E 70A8 6174 D393 E84D 8D04 99F1 4412 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: OutOfMemory errors compiling JSPs on 5.0.16 and 5.5.4
I've not been following this thread but my guess would be that you are running out of space in the permanent generation of the heap. Get a hold of jvmstat from sun and run visualgc on your JVM, it should become obvious then which pool is running out of space. Ta Matt -Original Message- From: Kevin A. Burton [mailto:[EMAIL PROTECTED] Sent: 14 November 2004 01:31 To: Tomcat Users List Subject: Re: OutOfMemory errors compiling JSPs on 5.0.16 and 5.5.4 Remy Maucherat wrote: On Fri, 12 Nov 2004 17:17:28 -0800, Kevin A. Burton [EMAIL PROTECTED] wrote: - For all my JSPs I fetch them with the URL foo.jsp?jsp_precompile=true to trigger precompilation How many JSPs must be compiled to cause problems ? About 50 or so... it changes every time. Sometimes I have to trigger a precompile twice. Note that the VM still shows plenty of memory so I'm not sure what the heck is going on here. I also looked at our file handles and they seem fine too. In that kind of situation, a profiler will have to be used. All I can tell right now is that it has nothing to do with the Java compilation, which is not very surprising. Why is it then that doing a ?jsp_precompile=true for all my JSPs and NO other action causes this? For really large web applications, I think you should precompile as many JSPs as possible anyway, as a JSP compiled dynamically will always use more resources (even if there is no bug in Jasper). Well thats probably an approach we will take but its unfortunate. If i had a profiler I would connect it to figure out whats going on but I'm really not happy with any of them. Kevin -- Use Rojo (RSS/Atom aggregator). Visit http://rojo.com. Ask me for an invite! Also see irc.freenode.net #rojo if you want to chat. Rojo is Hiring! - http://www.rojonetworks.com/JobsAtRojo.html If you're interested in RSS, Weblogs, Social Networking, etc... then you should work for Rojo! If you recommend someone and we hire them you'll get a free iPod! Kevin A. Burton, Location - San Francisco, CA AIM/YIM - sfburtonator, Web - http://peerfear.org/ GPG fingerprint: 5FB2 F3E2 760E 70A8 6174 D393 E84D 8D04 99F1 4412 Any opinions expressed in this E-mail may be those of the individual and not necessarily the company. This E-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this E-mail in error and that any use or copying is strictly prohibited. If you have received this E-mail in error please notify the beCogent postmaster at [EMAIL PROTECTED] Unless expressly stated, opinions in this email are those of the individual sender and not beCogent Ltd. You must take full responsibility for virus checking this email and any attachments. Please note that the content of this email or any of its attachments may contain data that falls within the scope of the Data Protection Acts and that you must ensure that any handling or processing of such data by you is fully compliant with the terms and provisions of the Data Protection Act 1984 and 1998. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OutOfMemory errors compiling JSPs on 5.0.16 and 5.5.4
On Sat, 13 Nov 2004 17:30:38 -0800, Kevin A. Burton [EMAIL PROTECTED] wrote: Remy Maucherat wrote: On Fri, 12 Nov 2004 17:17:28 -0800, Kevin A. Burton [EMAIL PROTECTED] wrote: - For all my JSPs I fetch them with the URL foo.jsp?jsp_precompile=true to trigger precompilation How many JSPs must be compiled to cause problems ? About 50 or so... it changes every time. Sometimes I have to trigger a precompile twice. I don't quite understand in which cases problems occur: - if you ?jsp_precompile=true 50 times for the same JSP ? - if you ?jsp_precompile=true for 50 different JSPs ? - if you access normally 50 different JSPs (triggering compilation for each one) ? I would understand from your description only the second one is an issue. Can you confirm this ? -- x Rémy Maucherat Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OutOfMemory errors compiling JSPs on 5.0.16 and 5.5.4
On Fri, 12 Nov 2004 17:17:28 -0800, Kevin A. Burton [EMAIL PROTECTED] wrote: - For all my JSPs I fetch them with the URL foo.jsp?jsp_precompile=true to trigger precompilation How many JSPs must be compiled to cause problems ? Note that the VM still shows plenty of memory so I'm not sure what the heck is going on here. I also looked at our file handles and they seem fine too. In that kind of situation, a profiler will have to be used. All I can tell right now is that it has nothing to do with the Java compilation, which is not very surprising. For really large web applications, I think you should precompile as many JSPs as possible anyway, as a JSP compiled dynamically will always use more resources (even if there is no bug in Jasper). -- x Rémy Maucherat Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OutOfMemory errors compiling JSPs on 5.0.16 and 5.5.4
Remy Maucherat wrote: On Fri, 12 Nov 2004 17:17:28 -0800, Kevin A. Burton [EMAIL PROTECTED] wrote: - For all my JSPs I fetch them with the URL foo.jsp?jsp_precompile=true to trigger precompilation How many JSPs must be compiled to cause problems ? About 50 or so... it changes every time. Sometimes I have to trigger a precompile twice. Note that the VM still shows plenty of memory so I'm not sure what the heck is going on here. I also looked at our file handles and they seem fine too. In that kind of situation, a profiler will have to be used. All I can tell right now is that it has nothing to do with the Java compilation, which is not very surprising. Why is it then that doing a ?jsp_precompile=true for all my JSPs and NO other action causes this? For really large web applications, I think you should precompile as many JSPs as possible anyway, as a JSP compiled dynamically will always use more resources (even if there is no bug in Jasper). Well thats probably an approach we will take but its unfortunate. If i had a profiler I would connect it to figure out whats going on but I'm really not happy with any of them. Kevin -- Use Rojo (RSS/Atom aggregator). Visit http://rojo.com. Ask me for an invite! Also see irc.freenode.net #rojo if you want to chat. Rojo is Hiring! - http://www.rojonetworks.com/JobsAtRojo.html If you're interested in RSS, Weblogs, Social Networking, etc... then you should work for Rojo! If you recommend someone and we hire them you'll get a free iPod! Kevin A. Burton, Location - San Francisco, CA AIM/YIM - sfburtonator, Web - http://peerfear.org/ GPG fingerprint: 5FB2 F3E2 760E 70A8 6174 D393 E84D 8D04 99F1 4412
OutOfMemory errors compiling JSPs on 5.0.16 and 5.5.4
I'm having a terrible time trying to get my JSPs compiled on Tomcat. We started having OutOfMemory problems a while back and I've tracked it down to JSP compilation. Here's what I can do to replicate the problem: - shutdown tomcat - remove the work directory - startup tomcat - For all my JSPs I fetch them with the URL foo.jsp?jsp_precompile=true to trigger precompilation After about 10 minutes (and 50-100 JSP files) Tomcat will fail with: SEVERE: Servlet.service() for servlet jsp threw exception java.lang.OutOfMemoryError Note that the VM still shows plenty of memory so I'm not sure what the heck is going on here. I also looked at our file handles and they seem fine too. I've followed all suggestions I've found via Google including: - setting fork to true - using jikes - Migrating to Tomcat 5.5.4 to use jdtool. The machine has PLENTY of memory available: export JAVA_OPTS=-server -Xmx1280M -Xms512M -Djava.awt.headless=true Any suggestions would be appreciated. We're probably going to migrate to using the command line JspC compiler to build all our JSPs before hand so the webapp doesn't need to compile them at runtime but this seems like a cheap workaround. I'd rather Tomcat weren't broken in this regard. Kevin -- Use Rojo (RSS/Atom aggregator). Visit http://rojo.com. Ask me for an invite! Also see irc.freenode.net #rojo if you want to chat. Rojo is Hiring! - http://www.rojonetworks.com/JobsAtRojo.html If you're interested in RSS, Weblogs, Social Networking, etc... then you should work for Rojo! If you recommend someone and we hire them you'll get a free iPod! Kevin A. Burton, Location - San Francisco, CA AIM/YIM - sfburtonator, Web - http://peerfear.org/ GPG fingerprint: 5FB2 F3E2 760E 70A8 6174 D393 E84D 8D04 99F1 4412 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
OutOfMemory on Tomcat webapp with awt use
Hi, I have a problem with this server configuration: - Server sun/solaris 5.8 Generic_108528-17 sun4u sparc SUNW,UltraAX-i2 - Apache 2.0.38 with mod_jk2 - Tomcat 4.1.30 - j2sdk1.4.2_05 Sun in pre-production environment. My webapp crashes also with few concurrent users when it uses awt for images generation on server side; the images are visualized to internet users by their requests. The server error (in catalina.out) is: java.lang.OutOfMemoryError Sep 27, 2004 4:33:11 PM org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run SEVERE: Caught exception (java.lang.OutOfMemoryError) executing [EMAIL PROTECTED], terminatin g thread -- Could be a bug or known problem on use of awt classes on Unix Systems? Without image generation my webapp works fine. On MS NT system the same problem seems doesn't arise: it's possible? My command line for running java is: java -Xms256m -Xmx256m -Djava.awt.headless=true .. Thanks in advance four your help. Best regards cg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OutOfMemory on Tomcat webapp with awt use
On Tue, Sep 28, 2004 at 11:32:40AM +0200, Camillo Granchelli wrote: : My webapp crashes also with few concurrent users when it : uses awt for images generation on server side; the images are : visualized to internet users by their requests. : The server error (in catalina.out) is: : : java.lang.OutOfMemoryError Perhaps you'll need more memory (larger heap, aka -Xmx). Image rendering can be memory-intensive, depending on what API is used on the backend and the type of image you're creating. Run a load-test to guage your memory settings. -QM -- software -- http://www.brandxdev.net tech news -- http://www.RoarNetworX.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
OutOfMemory Exceptions AGAIN
Hello Everyone, I am getting an OutOfMemory Exceptions again. I have been running JProbe on my web application for some time now and have not noticed any memory issues, as in, memory not being released by the application. This is what my environment look like: - The environment is a cluster running on 2 Sun Blade servers running RedHat 9. Clustering is handled by my app and am not using tomcats clustering. - Apache 2, httpd 2.0.49 - Tomcat 5.0.25 - Java 2 SDK version 1.4.2_04 - Ant 1.6.1 I modified the server.xml to show the following change advised by one of the posts on the list. Engine className=org.apache.catalina.core.StandardEngine debug=0 defaultHost=localhost mapperClass=org.apache.catalina.core.StandardEngineMapper name=Standalone backgroundProcessorDelay=-1 I also set the JAVA_OPTS to JAVA_OPTS=-Xmn32M -Xmx128M -XX:MaxHeapFreeRatio=30 -XX:+UseParallelGC. I can change the -Xmx to 256 or 512 but that is not a solution, its just a way of temporarily getting away from the problem. I have the following symptons - I got OutOfMemory Exception today after moving to tomcat 5 a couple of months ago, but have been noticing some funny memory usage. I was previously using tomcat 4.1.30 and was getting memory exceptions almost everyday. - When I shutdown the server and restart it java starts bloated, same size as when it was shutdown. I have tried this with the application removed but no difference. Attempts: - I have tested the app on windows machine and VMware installations of the same environment(RedHat 9) and can't duplicate the problems. - I have used JProbe to monitor memory cleaning in both environments and have found nothing. - I am in the process of getting JProbe installed on the cluster and will be able to monitor thereafter. I can use some really good suggestions at this point. Regards, Nandish Rudra ECI Conference Call Services, LLC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: OutOfMemory Exceptions AGAIN
This sounds like your sessions arent getting invalidated. If you look at the tomcat manager app it will tell you how many there are and you are likely to see this number increasing. The reason that it starts bloated is because when you shutdown the sessions get serialised and then reloaded once you restart tomcat. To stop it starting up bloated remove the SESSIONS.ser file from your context's work directory, while the server is shut down. As a more permanent solution you should explicitly invalidate the sessions in your code or reduce the session inactive timeout but i'd suggest the former. Ta Matt -Original Message- From: Nandish Rudra [mailto:[EMAIL PROTECTED] Sent: 17 August 2004 18:55 To: Tomcat Users List (E-mail) Subject: OutOfMemory Exceptions AGAIN Hello Everyone, I am getting an OutOfMemory Exceptions again. I have been running JProbe on my web application for some time now and have not noticed any memory issues, as in, memory not being released by the application. This is what my environment look like: - The environment is a cluster running on 2 Sun Blade servers running RedHat 9. Clustering is handled by my app and am not using tomcats clustering. - Apache 2, httpd 2.0.49 - Tomcat 5.0.25 - Java 2 SDK version 1.4.2_04 - Ant 1.6.1 I modified the server.xml to show the following change advised by one of the posts on the list. Engine className=org.apache.catalina.core.StandardEngine debug=0 defaultHost=localhost mapperClass=org.apache.catalina.core.StandardEngineMapper name=Standalone backgroundProcessorDelay=-1 I also set the JAVA_OPTS to JAVA_OPTS=-Xmn32M -Xmx128M -XX:MaxHeapFreeRatio=30 -XX:+UseParallelGC. I can change the -Xmx to 256 or 512 but that is not a solution, its just a way of temporarily getting away from the problem. I have the following symptons - I got OutOfMemory Exception today after moving to tomcat 5 a couple of months ago, but have been noticing some funny memory usage. I was previously using tomcat 4.1.30 and was getting memory exceptions almost everyday. - When I shutdown the server and restart it java starts bloated, same size as when it was shutdown. I have tried this with the application removed but no difference. Attempts: - I have tested the app on windows machine and VMware installations of the same environment(RedHat 9) and can't duplicate the problems. - I have used JProbe to monitor memory cleaning in both environments and have found nothing. - I am in the process of getting JProbe installed on the cluster and will be able to monitor thereafter. I can use some really good suggestions at this point. Regards, Nandish Rudra ECI Conference Call Services, LLC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Any opinions expressed in this E-mail may be those of the individual and not necessarily the company. This E-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this E-mail in error and that any use or copying is strictly prohibited. If you have received this E-mail in error please notify the beCogent postmaster at [EMAIL PROTECTED] Unless expressly stated, opinions in this email are those of the individual sender and not beCogent Ltd. You must take full responsibility for virus checking this email and any attachments. Please note that the content of this email or any of its attachments may contain data that falls within the scope of the Data Protection Acts and that you must ensure that any handling or processing of such data by you is fully compliant with the terms and provisions of the Data Protection Act 1984 and 1998. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: OutOfMemory Exceptions AGAIN
Hello Matt, Thanks for the reply. When I get an http request I do not attach any session information or create and cookies/httpsessions and not using tomcat clustering, would the sessions still be serialized. Is there a way I can disable sessions completely from server.xml? Nandish Rudra ECI Conference Call Services, LLC -Original Message- From: Dale, Matt [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 17, 2004 2:07 PM To: Tomcat Users List Subject: RE: OutOfMemory Exceptions AGAIN This sounds like your sessions arent getting invalidated. If you look at the tomcat manager app it will tell you how many there are and you are likely to see this number increasing. The reason that it starts bloated is because when you shutdown the sessions get serialised and then reloaded once you restart tomcat. To stop it starting up bloated remove the SESSIONS.ser file from your context's work directory, while the server is shut down. As a more permanent solution you should explicitly invalidate the sessions in your code or reduce the session inactive timeout but i'd suggest the former. Ta Matt -Original Message- From: Nandish Rudra [mailto:[EMAIL PROTECTED] Sent: 17 August 2004 18:55 To: Tomcat Users List (E-mail) Subject: OutOfMemory Exceptions AGAIN Hello Everyone, I am getting an OutOfMemory Exceptions again. I have been running JProbe on my web application for some time now and have not noticed any memory issues, as in, memory not being released by the application. This is what my environment look like: - The environment is a cluster running on 2 Sun Blade servers running RedHat 9. Clustering is handled by my app and am not using tomcats clustering. - Apache 2, httpd 2.0.49 - Tomcat 5.0.25 - Java 2 SDK version 1.4.2_04 - Ant 1.6.1 I modified the server.xml to show the following change advised by one of the posts on the list. Engine className=org.apache.catalina.core.StandardEngine debug=0 defaultHost=localhost mapperClass=org.apache.catalina.core.StandardEngineMapper name=Standalone backgroundProcessorDelay=-1 I also set the JAVA_OPTS to JAVA_OPTS=-Xmn32M -Xmx128M -XX:MaxHeapFreeRatio=30 -XX:+UseParallelGC. I can change the -Xmx to 256 or 512 but that is not a solution, its just a way of temporarily getting away from the problem. I have the following symptons - I got OutOfMemory Exception today after moving to tomcat 5 a couple of months ago, but have been noticing some funny memory usage. I was previously using tomcat 4.1.30 and was getting memory exceptions almost everyday. - When I shutdown the server and restart it java starts bloated, same size as when it was shutdown. I have tried this with the application removed but no difference. Attempts: - I have tested the app on windows machine and VMware installations of the same environment(RedHat 9) and can't duplicate the problems. - I have used JProbe to monitor memory cleaning in both environments and have found nothing. - I am in the process of getting JProbe installed on the cluster and will be able to monitor thereafter. I can use some really good suggestions at this point. Regards, Nandish Rudra ECI Conference Call Services, LLC - 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]
Re: OutOfMemory Exceptions AGAIN
On Tue, Aug 17, 2004 at 02:13:40PM -0400, Nandish Rudra wrote: : Thanks for the reply. When I get an http request I do not attach any session : information or create and cookies/httpsessions and not using tomcat : clustering, would the sessions still be serialized. You may not explicitly put anything in a session, but they can still be created. For example, do all of your JSPs call %@ page session=false % ? As for your other point: :I can change the -Xmx to 256 or512 but that is not a solution, its just :a way of temporarily getting awayfrom the problem. Not necessarily true. Your app may just need more than 128M heap size. Have you load-tested the app, with your expected number of concurrent users, to see what the app's mem usage would be? -QM -- software -- http://www.brandxdev.net tech news -- http://www.RoarNetworX.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: OutOfMemory Exceptions AGAIN
As previously mentioned you may not be explicitly using them but doesnt mean they arent there. Have you looked in your manager webapp to see how many sessions it say you are using? The sessions are always (by default) serialised on shutdown so that they are brought back again on restart. You can change this behaviour in the config. Check the documentation on session managers. I'm pretty sure you can't disable them completely but someone may put me right on this if i'm wrong. -Original Message- From: Nandish Rudra [mailto:[EMAIL PROTECTED] Sent: 17 August 2004 19:14 To: 'Tomcat Users List' Subject: RE: OutOfMemory Exceptions AGAIN Hello Matt, Thanks for the reply. When I get an http request I do not attach any session information or create and cookies/httpsessions and not using tomcat clustering, would the sessions still be serialized. Is there a way I can disable sessions completely from server.xml? Nandish Rudra ECI Conference Call Services, LLC -Original Message- From: Dale, Matt [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 17, 2004 2:07 PM To: Tomcat Users List Subject: RE: OutOfMemory Exceptions AGAIN This sounds like your sessions arent getting invalidated. If you look at the tomcat manager app it will tell you how many there are and you are likely to see this number increasing. The reason that it starts bloated is because when you shutdown the sessions get serialised and then reloaded once you restart tomcat. To stop it starting up bloated remove the SESSIONS.ser file from your context's work directory, while the server is shut down. As a more permanent solution you should explicitly invalidate the sessions in your code or reduce the session inactive timeout but i'd suggest the former. Ta Matt -Original Message- From: Nandish Rudra [mailto:[EMAIL PROTECTED] Sent: 17 August 2004 18:55 To: Tomcat Users List (E-mail) Subject: OutOfMemory Exceptions AGAIN Hello Everyone, I am getting an OutOfMemory Exceptions again. I have been running JProbe on my web application for some time now and have not noticed any memory issues, as in, memory not being released by the application. This is what my environment look like: - The environment is a cluster running on 2 Sun Blade servers running RedHat 9. Clustering is handled by my app and am not using tomcats clustering. - Apache 2, httpd 2.0.49 - Tomcat 5.0.25 - Java 2 SDK version 1.4.2_04 - Ant 1.6.1 I modified the server.xml to show the following change advised by one of the posts on the list. Engine className=org.apache.catalina.core.StandardEngine debug=0 defaultHost=localhost mapperClass=org.apache.catalina.core.StandardEngineMapper name=Standalone backgroundProcessorDelay=-1 I also set the JAVA_OPTS to JAVA_OPTS=-Xmn32M -Xmx128M -XX:MaxHeapFreeRatio=30 -XX:+UseParallelGC. I can change the -Xmx to 256 or 512 but that is not a solution, its just a way of temporarily getting away from the problem. I have the following symptons - I got OutOfMemory Exception today after moving to tomcat 5 a couple of months ago, but have been noticing some funny memory usage. I was previously using tomcat 4.1.30 and was getting memory exceptions almost everyday. - When I shutdown the server and restart it java starts bloated, same size as when it was shutdown. I have tried this with the application removed but no difference. Attempts: - I have tested the app on windows machine and VMware installations of the same environment(RedHat 9) and can't duplicate the problems. - I have used JProbe to monitor memory cleaning in both environments and have found nothing. - I am in the process of getting JProbe installed on the cluster and will be able to monitor thereafter. I can use some really good suggestions at this point. Regards, Nandish Rudra ECI Conference Call Services, LLC - 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] Any opinions expressed in this E-mail may be those of the individual and not necessarily the company. This E-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this E-mail in error and that any use or copying is strictly prohibited. If you have received this E-mail in error please notify the beCogent postmaster at [EMAIL PROTECTED] Unless expressly stated, opinions in this email are those of the individual sender and not beCogent Ltd. You must take full responsibility for virus checking this email and any attachments. Please note that the content of this email or any of its attachments may contain data that falls within
RE: OutOfMemory Exceptions AGAIN
Hello QM, As Matt had suggested, i check and there was a jsp from one of the other apps running, that was not invalidating sessions. I found 9000+ sessions of that jsp. The jsp now invalidates its sessions and hopefully things will be better. As the app is still under development the load is almost nothing hence the needs of the heap should not be great. I have been running the same app on my machine locally and have not had any memory issue as of yet. Thanks for the help guys. Regards, Nandish Rudra ECI Conference Call Services, LLC -Original Message- From: QM [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 17, 2004 4:25 PM To: Tomcat Users List Subject: Re: OutOfMemory Exceptions AGAIN On Tue, Aug 17, 2004 at 02:13:40PM -0400, Nandish Rudra wrote: : Thanks for the reply. When I get an http request I do not attach any session : information or create and cookies/httpsessions and not using tomcat : clustering, would the sessions still be serialized. You may not explicitly put anything in a session, but they can still be created. For example, do all of your JSPs call %@ page session=false % ? As for your other point: :I can change the -Xmx to 256 or512 but that is not a solution, its just :a way of temporarily getting awayfrom the problem. Not necessarily true. Your app may just need more than 128M heap size. Have you load-tested the app, with your expected number of concurrent users, to see what the app's mem usage would be? -QM -- software -- http://www.brandxdev.net tech news -- http://www.RoarNetworX.com - 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]
Strange OutOfMemory Error in TcpWorkerThread
Hi all, I have this strange error : SEVERE: Caught exception (java.lang.OutOfMemoryError: unable to create new native thread) executing [EMAIL PROTECTED], terminating thread I use those parameters : -verbose:gc -Xms756m -Xmx1024m -XX:+UseConcMarkSweepGC -XX:+UseParNewGC And the ParNew before and after the error gives me : Before : [ParNew 299307K-285970K(774080K), 0.0632930 secs] After : [ParNew 302226K-290481K(774080K), 0.0777970 secs] So, there is a LOT of memory available. I probably have to change some Jvm parameters. Note that the dev is out for holidays, so it will be difficult for me to look for a memory leak somewhere. Note that if I give more memory (say -Xms=1024m -Xmx=1536m, for example), the error arrives sooner. There are 800 connectors configured. I was also unable to increase the number of tomcat5.CoyoteConnector threads. Any help appreciated, François. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Strange OutOfMemory Error in TcpWorkerThread
Hi, It's not likely a memory problem, but a resources problem for creating threads. If you're running on unix, look at the ulimit command. Yoav Shapira Millennium Research Informatics -Original Message- From: Francois JEANMOUGIN [mailto:[EMAIL PROTECTED] Sent: Friday, July 30, 2004 4:00 AM To: Tomcat Users List Subject: Strange OutOfMemory Error in TcpWorkerThread Hi all, I have this strange error : SEVERE: Caught exception (java.lang.OutOfMemoryError: unable to create new native thread) executing [EMAIL PROTECTED], terminating thread I use those parameters : -verbose:gc -Xms756m -Xmx1024m -XX:+UseConcMarkSweepGC -XX:+UseParNewGC And the ParNew before and after the error gives me : Before : [ParNew 299307K-285970K(774080K), 0.0632930 secs] After : [ParNew 302226K-290481K(774080K), 0.0777970 secs] So, there is a LOT of memory available. I probably have to change some Jvm parameters. Note that the dev is out for holidays, so it will be difficult for me to look for a memory leak somewhere. Note that if I give more memory (say -Xms=1024m -Xmx=1536m, for example), the error arrives sooner. There are 800 connectors configured. I was also unable to increase the number of tomcat5.CoyoteConnector threads. Any help appreciated, François. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat Java OutOfMemory Error
Hi, I'm running Tomcat 3.2.1 on Windows 2000 Server as service with jk_nt_service.exe utility. I receive java.lang.OutOfMemory error in my JSP page. I need to increment memory for JVM to 512 MB by setting -Xms512m -Xmx512m. Where I do it? Thanks in advance. Marco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Java OutOfMemory Error
Hi, I not sure about tomcat 3.2.1. In tomcat 4 I have used the JAVA_OPTS . I set JAVA_OPTS as my environmental variable and that was it. Hope this helps you shyam -Original Message- From: Baldacchini Marco [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 5:41 AM To: [EMAIL PROTECTED] Subject: Tomcat Java OutOfMemory Error Hi, I'm running Tomcat 3.2.1 on Windows 2000 Server as service with jk_nt_service.exe utility. I receive java.lang.OutOfMemory error in my JSP page. I need to increment memory for JVM to 512 MB by setting -Xms512m -Xmx512m. Where I do it? Thanks in advance. Marco - 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]
Re: Tomcat Java OutOfMemory Error
I have already tried but it does not work (I have tried also TOMCAT_OPTS as environmental variable), remains set up to the default (64MB). Thanks shyam Scrive: Hi, I not sure about tomcat 3.2.1. In tomcat 4 I have used the JAVA_OPTS . I set JAVA_OPTS as my environmental variable and that was it. Hope this helps you shyam -Original Message- From: Baldacchini Marco [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 5:41 AM To: [EMAIL PROTECTED] Subject: Tomcat Java OutOfMemory Error Hi, I'm running Tomcat 3.2.1 on Windows 2000 Server as service with jk_nt_service.exe utility. I receive java.lang.OutOfMemory error in my JSP page. I need to increment memory for JVM to 512 MB by setting -Xms512m -Xmx512m. Where I do it? Thanks in advance. Marco - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Java OutOfMemory Error
JAVA_OPTS only works for standalone startup not as a service. Found this by googling. http://forum.java.sun.com/thread.jsp?thread=290568forum=33message=1211179 Solution is about six down and by user dfortae HTH, Jon shyam wrote: Hi, I not sure about tomcat 3.2.1. In tomcat 4 I have used the JAVA_OPTS . I set JAVA_OPTS as my environmental variable and that was it. Hope this helps you shyam -Original Message- From: Baldacchini Marco [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 5:41 AM To: [EMAIL PROTECTED] Subject: Tomcat Java OutOfMemory Error Hi, I'm running Tomcat 3.2.1 on Windows 2000 Server as service with jk_nt_service.exe utility. I receive java.lang.OutOfMemory error in my JSP page. I need to increment memory for JVM to 512 MB by setting -Xms512m -Xmx512m. Where I do it? Thanks in advance. Marco - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Java OutOfMemory Error
Hi. When using the jk_nt_service.exe you need to setup the wrapper.properties file. The very last line is where you set any additional VM parameters - use that. Thus you would change it from: wrapper.cmd_line=$(wrapper.javabin) -classpath $(wrapper.class_path) $(wrapper.startup_class) -config $(wrapper.server_xml) -home $(wrapper.tomcat_home) To: wrapper.cmd_line=$(wrapper.javabin) -Xms128m -Xmx512m -classpath $(wrapper.class_path) $(wrapper.startup_class) -config $(wrapper.server_xml) -home $(wrapper.tomcat_home) Hope that helps! Regards, Carl -Original Message- From: Baldacchini Marco [mailto:[EMAIL PROTECTED] Sent: 06 April 2004 03:13 PM To: Tomcat Users List Subject: Re: Tomcat Java OutOfMemory Error I have already tried but it does not work (I have tried also TOMCAT_OPTS as environmental variable), remains set up to the default (64MB). Thanks shyam Scrive: Hi, I not sure about tomcat 3.2.1. In tomcat 4 I have used the JAVA_OPTS . I set JAVA_OPTS as my environmental variable and that was it. Hope this helps you shyam -Original Message- From: Baldacchini Marco [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 5:41 AM To: [EMAIL PROTECTED] Subject: Tomcat Java OutOfMemory Error Hi, I'm running Tomcat 3.2.1 on Windows 2000 Server as service with jk_nt_service.exe utility. I receive java.lang.OutOfMemory error in my JSP page. I need to increment memory for JVM to 512 MB by setting -Xms512m -Xmx512m. Where I do it? Thanks in advance. Marco - 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] - 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]
Re: Tomcat Java OutOfMemory Error
Done. Thanks a lot!!! Marco Carl Olivier Scrive: Hi. When using the jk_nt_service.exe you need to setup the wrapper.properties file. The very last line is where you set any additional VM parameters - use that. Thus you would change it from: wrapper.cmd_line=$(wrapper.javabin) -classpath $(wrapper.class_path) $(wrapper.startup_class) -config $(wrapper.server_xml) -home $(wrapper.tomcat_home) To: wrapper.cmd_line=$(wrapper.javabin) -Xms128m -Xmx512m -classpath $(wrapper.class_path) $(wrapper.startup_class) -config $(wrapper.server_xml) -home $(wrapper.tomcat_home) Hope that helps! Regards, Carl -Original Message- From: Baldacchini Marco [mailto:[EMAIL PROTECTED] Sent: 06 April 2004 03:13 PM To: Tomcat Users List Subject: Re: Tomcat Java OutOfMemory Error I have already tried but it does not work (I have tried also TOMCAT_OPTS as environmental variable), remains set up to the default (64MB). Thanks shyam Scrive: Hi, I not sure about tomcat 3.2.1. In tomcat 4 I have used the JAVA_OPTS . I set JAVA_OPTS as my environmental variable and that was it. Hope this helps you shyam -Original Message- From: Baldacchini Marco [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 5:41 AM To: [EMAIL PROTECTED] Subject: Tomcat Java OutOfMemory Error Hi, I'm running Tomcat 3.2.1 on Windows 2000 Server as service with jk_nt_service.exe utility. I receive java.lang.OutOfMemory error in my JSP page. I need to increment memory for JVM to 512 MB by setting -Xms512m -Xmx512m. Where I do it? Thanks in advance. Marco - 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] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
