The image did not get through.  Can you zip it?

Paul



                                                                           
             "Al Forbes"                                                   
             <[EMAIL PROTECTED]                                             
             mail.com>                                                  To 
                                       "JCS Users List"                    
             12/04/2006 11:29          <jcs-users@jakarta.apache.org>      
             AM                                                         cc 
                                                                           
                                                                   Subject 
             Please respond to         Re: Garbage collection              
             "JCS Users List"                                              
             <[EMAIL PROTECTED]                                             
               a.apache.org>                                               
                                                                           
                                                                           
                                                                           




Thanks Paul. Yes, I already use those params - I think they will be
the defaults in JDK1.6, but still need setting in pre-JDK 1.6.

I will try changing from a disk cache to Mysql just so I can narrow
down the problem.

Not sure if the attached image will get through, but this shows what
is happening.

Regards
Al


On 04/12/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> We ran into similar issues when first starting to use JCS.  The
underlying
> issue for us was that the remote cache uses RMI calls.  When RMI is in
use,
> the JVM may automatically trigger full GC's every 60 seconds as the
> default; at least under our JDK 1.3.1...not sure about JDK 1.5 but I
> believe they may have changed this to the values I will list below in the
> JVM parameters that we added...you can tell by examining the GC
consecutive
> cycles...if they are exactly 60 seconds apart, every 60 seconds, then if
> you add the parameters below you may see an improvement:
>
> -Dsun.rmi.dgc.client.gcInterval=3600000
> -Dsun.rmi.dgc.server.gcInterval=3600000
> -Dsun.rmi.transport.tcp.connectionPool=true
>
> Hope this helps.
>
> Paul
>
>
>
>
>
>              "Al Forbes"
>              <[EMAIL PROTECTED]
>              mail.com>
To
>                                        jcs-users@jakarta.apache.org
>              12/03/2006 04:30
cc
>              PM
>
Subject
>                                        Garbage collection
>              Please respond to
>              "JCS Users List"
>              <[EMAIL PROTECTED]
>                a.apache.org>
>
>
>
>
>
>
> Hi,
>
> I have a remote cache setup with a memory+disk cache, pure memory, and
> a mysql cache (0 memory). This uses the latest JCS jcs-1.2.7.9.2.jar
> in JDK1.5.
>
>
> After starting the times for a "Full" grabage collection get longer
> and longer. Eventually after about 10-12 days I need to restart the
> remote cache. Also when the full garbage collection runs it uses more
> and more CPU. Memory usage remains fairly constant (round 600M), and
> the incremental collections are fairly small 0.02 secs. I wonder if
> anyone these has seen the same thing, or has any better suggestions
> for the garbage collection.
>
> Full collection:
> 559228.304: [Full GC 559228.304: [CMS: 214224K->171110K(393216K),
> 1.2718260 secs] 328232K->171110K(524224K), [CMS Perm :
> 8565K->8540K(16384K)] icms_dc=0 , 1.2720400 secs]
>
> I currently have the garbage collection configured to:
>
>    MEMUSE="-Xms512m -Xmx1024m"
>    MEMUSE=" $MEMUSE -XX:+UseConcMarkSweepGC \
>      -XX:NewSize=128m -XX:MaxNewSize=128m \
>      -XX:+CMSIncrementalMode \
>      -XX:+CMSIncrementalPacing \
>      -XX:CMSIncrementalDutyCycleMin=0 \
>      -XX:CMSIncrementalDutyCycle=10 \
>      -XX:+PrintGCDetails \
>      -XX:+PrintGCTimeStamps \
>      -Xloggc:../logs/gc.log \
>      -XX:-TraceClassUnloading"
>
> Regards
> Al
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> CONFIDENTIALITY NOTICE:
> This is a transmission from Kohl's Department Stores, Inc.
> and may contain information which is confidential and proprietary.
> If you are not the addressee, any disclosure, copying or distribution or
use of the contents of this message is expressly prohibited.
> If you have received this transmission in error, please destroy it and
notify us immediately at 262-703-7000.
>
> CAUTION:
> Internet and e-mail communications are Kohl's property and Kohl's
reserves the right to retrieve and read any message created, sent and
received.  Kohl's reserves the right to monitor messages to or from
authorized Kohl's Associates at any time
> without any further consent.
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

CONFIDENTIALITY NOTICE: 
This is a transmission from Kohl's Department Stores, Inc.
and may contain information which is confidential and proprietary.
If you are not the addressee, any disclosure, copying or distribution or use of 
the contents of this message is expressly prohibited.
If you have received this transmission in error, please destroy it and notify 
us immediately at 262-703-7000.

CAUTION:
Internet and e-mail communications are Kohl's property and Kohl's reserves the 
right to retrieve and read any message created, sent and received.  Kohl's 
reserves the right to monitor messages to or from authorized Kohl's Associates 
at any time
without any further consent.

Reply via email to