I had a similar problem using Novell portal services on Tomcat 4.1.x and Apache 2.0.4x
where after I a while I'd start getting out of memory problems. Windows 2000 with JDK
1.4.x seems to completely ignore the -X parameters when starting tomcat. I ended up
switching the platform I was running the portal on because of how easy it was to
overload the system [for me holding down the refresh key for 5 minutes crashed both
Apache and Tomcat]
>>> [EMAIL PROTECTED] 10/03/02 05:34PM >>>
Yes, changing the heap was the first thing I changed and I actually
thought of mentioning that because I figured that would be the immediate
response :-) That wasn't the issue.
We have discovered that this problem only manifests itself when using
Tomcat as a service, with the provided tomcat.exe (and having JAVA_OPTS
set in the environment to handle the heap size options). When started
from the command line, with a minimum of 256mb on the heap, I get no
problems with Tomcat past 150 MB of usage in Task Manager.
We don't really like the idea of running it from a command prompt for
maintenance purposes (we don't manage the box), but if some procedures are
put in place, I don't see why it won't work in the short-term. I just
didn't have time to figure out how to check and see if tomcat.exe was
picking up my JAVA_OPTS environment variable and actually setting the heap
size. If it wasn't, I would have thought I'd see problems after 64mb
because I believe this is the default max on the heap size.
BTW- The memory creep appears to be normal and will clear itself up after
a long period of inactivity. I thought this was a leak on my part, but
the GC wasn't doing anything until way later because the heap is so huge
(I actually had to set a max of 1.5 GB when using "catalina.bat run" from
DOS command line...the JVM gave me an error until this was set to some
value...I eventually brought it down to this value, which was as high as I
could get it without it giving me an error).
Thanks for your help!
Jon Brisbin
"Zabel, Ian" <[EMAIL PROTECTED]>
10/03/2002 04:48 PM
Please respond to "Tomcat Users List"
To: 'Tomcat Users List' <[EMAIL PROTECTED]>
cc:
Fax to:
Subject: RE: OutOfMemoryError after 88MB on Win2K / Tomcat 4.0.4
First of all, have you increased the memory available to Tomcat's JVM?
You can do this by defining:
JAVA_OPTS=" -Xms128m -Xmx384m"
The numbers represent megabytes in that example. Xms is minimum and Xmx is
maximum. Change the amounts to suit you.
Another thing you might want to try is enabling Verbose Gargbage
Collection.
This will give you an ouput of what the garbage collector is doing. To
turn
it on, add this to the JAVA_OPTS:
-verbose:gc
Then, in catalina.out, you'll see status reports on the GC.
Ian.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 03, 2002 5:37 PM
To: [EMAIL PROTECTED]
Subject: OutOfMemoryError after 88MB on Win2K / Tomcat 4.0.4
We are running a heavily XML-based application on Tomcat 4.0.4 on a dual
P4 1.4 GHz box with 4GB of RAM. With 9 users hitting the application
continuously, we experience OutOfMemoryErrors after tomcat.exe gets up to
around 88MB of usage.
Has anyone else experienced strange happenings with Tomcat on Win2K JDK
1.3.1 under load? We're wondering if the JVM is doing this, if there's
something in Tomcat that is causing the memory to continuously creep up
and never go down significantly, or if we're just really overlooking
something in our application framework that is causing objects to not go
out of scope. We haven't experienced this problem like this on other
platforms (Linux and OS/400) and IBM is testing this application and not
seeing the same kinds of results in WebSphere.
I'd appreciate any feedback from other XML users here...we have a go-live
date just a few days off and these problems are making my life very
difficult. I'd like to at least be able to explain the situation, even if
it is our fault. Not knowing is very frustrating.
Thanks for your help!
Jon Brisbin
Sr. App. Developer
EFCO Corporation
www.efcocorp.com
417.235.3193 x2687
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
