Hi Santiago,
thx for your very informative reply. U should have it up on the FAQ. My JDK
is a Sun latest one. It doens't have any such bugs. A couple of things :
A) Do u have the program/source code for the load testing program? I would
like to use/enhance it.
B) Yours is a 1.3a1 test. I have the 1.3a2 version but would have to repeat
it to see if it is similar.
C) Do u mean the running java program (under windows task manager) can grow
up to 128 MB even under low activity before serious GC will take place. That
is actually quite new to me. HOw do u differentiate between memory
utilisation and the heap? Any tool?
Lionel
----- Original Message -----
From: "Santiago Gala" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, August 08, 2001 6:17 PM
Subject: Re: JVM Memory Leak Ouch
> Lionel Siau wrote:
>
> >Hi,
> >
> >I've recently installed a2 on a tomcat(3.2.2) with no other apps. The
installation is fine but over time, I have noticed the mem allocation for
the JVM of tomcat serving jetspeed seems to rise over time. The memory size
required is a function of the activity of the jetspeed engine. The more
logins and clicksm, it grows. It start from about 30MB and now is already at
37MB. It ain't slowing down.
> >
> >I think u have some coding problems with the objects in the code of
jetspeed or even turbine...ugh...
> >
> There are two separate issues here:
>
> - memory leaks in the jdk. There are bugs related with this behaviour,
> specially in the hotspot JVM. I think 1.3.1 is fine to this regard, but
> one never knows. We have done stress testing of a Jetspeed based
> application, having it running continuously during days with 50
> simultaneous users requesting pages, and we have observed no memory
> leaks under jdk1.3.0_06 and jdk1.3.1
> - memory consumption by Jetspeed. A typical Jetspeed installation will
> require a java heap of between 128M and 384M (we use to run it with
> either -Xms256M -Xmx256M or 384, depending on the phisical memory of the
> machine where it is running and complexity of the portal)
>
> The memory as reported by the OS will start low (like 30-40M), and
> increase as hotspot optimizes and portlets are instantiated. The java
> heap will increase also.
>
> For instance, I have just started the tomcat process. Currently jetspeed
> admin shows 13,5M heap, about 1M free, and top shows 48M for the java
> process threads. It will grow progressively. But I have seen runtimes in
> the week order, without it escaping out of bounds.
>
> >
> >
> >Lionel
> >
>
>
>
>
> ---------------------------------------------------------------------
> 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]
