----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
I have an additional 50 meg of memory so I bumped the memory
to ms48 mx72 from ms32 mx64 and I am getting far less GCverbose
cleanings - so far.
Still not sure why it got stuck on those two classes to remove and load
repeatedly. Unless they are the last two that needed to be loaded and it
is on the edge of the GC minimum memory criteria?
Don
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Riley,
> Cameron
> Sent: Wednesday, August 02, 2000 8:48 AM
> To: 'Java Apache Users'
> Subject: RE: GC problem?
>
>
> ----------------------------------------------------------------
> BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
> WHEN YOU POST, include all relevant version numbers, log files,
> and configuration files. Don't make us guess your problem!!!
> ----------------------------------------------------------------
>
> I am having a problem with my JVM
> It will all of a sudden jump to 50% CPU usage and then to 100%
> Then strange things start happening.
>
> I am running on NT4 SP6a. Jserv 1.1.1, Apache 1.3.12 SUN - JDK1.1.8
> on a dual P II 450 mhz with 256 ram.
> My Prop file is running java -ms32m -mx64m -verbosegc
>
> I have found nothing in the Apache or Jserv logs to correlate
> to these CPU jumps. I had a look at the GC info and
> I am finding the following excerpt spread through my error.log:
>
>
>
> >My understanding of this is that it has topped at 26.843m and has
> >to free up heap. Why? if I have -mx64m set?
>
> Garbage Collection is to remove dereferenced objects from the JVM
> stack(memory), the JVM schedules sweeps periodically to maintain free
> memory(resources). It doesnt wait until it is totally out of memory before
> doing a gc sweep, that wouldnt be too smart as the wait to free
> up resources
> would impact the user of the application the JVM is running. You can
> influence when the sweeps occur as the JVM watches out for when it is
> running out of resources and will hurriedly insert a sweep. That was the
> gist of the IBM article.
>
>
>
>
> Cameron Riley
>
>
>
> --
> --------------------------------------------------------------
> Please read the FAQ! <http://java.apache.org/faq/>
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search Archives:
> <http://www.mail-archive.com/java-apache-users%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search Archives:
<http://www.mail-archive.com/java-apache-users%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
