DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15513>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15513 OutOfMemoryError and adjusting the heap size not helping [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Additional Comments From [EMAIL PROTECTED] 2003-03-06 02:22 ------- David this bug was closed because you said "The memory size started working.". I'll bet you were running TomCat as a service and you started running it from a shell, cmd or desktop batch file. You inadvertently stumbled on a work around. If would like to reopen this and have it fixed. We have a customer who is having the same problem and after a lot of investigation we discovered that TomCat has a bug when running as a service under windows. The bug is it ignores the evironment variables set as catalina.opt or catalina.bat. Instead it uses the default stack and heap size for the JVM. You can set -Xms<size> set initial Java heap size -Xmx<size> set maximum Java heap size -Xss<size> set java thread stack size until your blue in the face and the JVM will never get close to that size. It will consistently throw out of memory errors when its 80 ~100 megabytes. Solution number 1: Don't run it as a service. Run it from a shell/command. Solution number 2: Grub through the @[EMAIL PROTECTED] registry till you find the service entry for TomCat. Figure out which parameter is used to set Java heap and stack size. Edit the numbers with REGEDIT. Sorry but I don't remember the registry key entries off the top of my head. Nota Bene: This may not really be a TomCat bug. This could be a bug in the @[EMAIL PROTECTED] installer that our customer used to set TomCat up as a service. Cleanest test is run TomCat directly from the desktop and I'll bet the problem goes away. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
