Hi (yes that's me again),
I have more details for those that would be willing to help. I have
started to use IBM's JDK that has the nice memory dump feature set up so
that whenever OutOfMemory occurs the heap is dumped. So my heap is here
My previous post should be longer ... here is the rest:
DFS from pure Roots
...done.
DFS from objects unreached from Roots
...done.
Found 1,051,382 objects which
Still I don't see the whole thing - and trying to send the rest here:
If I interpret it correctly the instance of
org/apache/coyote/RequestGroupInfo
holds 150 MB of heap memory. Also if I understand it correctly from here
Howdy,
If I interpret it correctly the instance of
org/apache/coyote/RequestGroupInfo
holds 150 MB of heap memory. Also if I understand it correctly from
here
http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-
connectors/coyote/src/java/org/apache/coyote/
someone just recently tried to do
Shapira, Yoav wrote:
You're not paranoid. There's a memory leak related to the
RequestGroup/RequestGroupInfo connector code. It's been discussed
during the past week on the dev mailing list, and addressed within the
past couple of days. You can try the tomcat 5.0.18 build which has the
fix.
Hi,
I have the very same problem. I have tried everything possible with no
outcome (the fork atribute for the jsp compiler did not help (with this
I refer to a previous discussion here)). I suspect the CoyoteConnector
being at fault but have no proof yet. I plan to run profiler but doing
that
Ooops. I was too fast with my previous post. My config is different form
yours:
Connector className=org.apache.coyote.tomcat4.CoyoteConnector
address=212.47.18.50 acceptCount=100 bufferSize=2048
compression=off connectionLinger=-1 connectionTimeout=2
connectionUploadTimeout=30 debug=0
Mohit Gupta wrote:
I am working on Tomcat 4.1.24 on Solatis-8, 12 CPU, 24GB RAM Machine.
I am using Apache 2.0.43 and the Jdk version is 1.4.1_02.
When I start my server then after 5-6 hours my server becomes very
slow and then I need to restart my server. I am taking the top stats
for the
David Rees wrote:
Additionally, upgrading to the latest Tomcat (4.1.27 or 5.0.16) and JDK
(1.4.2_03) is a good idea as the latest versions have bug fixes and
performance improvements.
I doubt it is a Tomcat issue, it is more than likely an issue with your
application, but the stack trace will
Hi!
David Strupl wrote:
I have tomcat 4.1.29, JDK1.4.2. Also my app was completely ok with
tomcat 3.x.x. The 100% of processor time occurs in my case only after
the OOME. Before the OOME all the threads (both tomcat's and mine) are
happy.
The processor usage is not too surprising. When your
Philipp Taprogge wrote:
The processor usage is not too surprising. When your machine runs out of
memory and there are still busy processes, most of the cpu time will go
into swapping in and out those processes. Still, since most prople are
perfectly happy with the tomcat build you are using,
Hi again!
David Strupl wrote:
Also the code was running for several
years in tomcat 3.x without any problem. After migrating to tomcat 4.x
the nightmare began.
Have you changed the JRE as well or are you running the tomcat 4
instance in the same VM as the tomcat 3 before? Just to make sure
Philipp Taprogge wrote:
Have you changed the JRE as well or are you running the tomcat 4
instance in the same VM as the tomcat 3 before? Just to make sure your
problems are not arising from changes made to the JVM in the meantime.
I have upgraged the VM as well as the OS on the machine. In fact
Howdy,
Yes - I was also not surprised with the CPU after the OOME. I will try
to prepare a heap shapshot and post it here (only a link, don't worry)
after I manage to get a usefull one.
Make sure it's one before the OutOfMemoryError ;)
server with couple of JSPs and servlets. The profiling has
Shapira, Yoav wrote:
(BTW, to refresh my memory, is this setup where the JSP pages change
hourly?)
I have already changed this ;-) Also added the fork attribute to true
for jsp compile. It is not caused by the app - after the app starts and
first 100 or so users connect the memory jumps up to
David Strupl wrote:
I have already changed this ;-) Also added the fork attribute to true
for jsp compile. It is not caused by the app - after the app starts
and first 100 or so users connect the memory jumps up to approx 130
MB. But during the next 24 hours it eats more than 300 megs. From
16 matches
Mail list logo
