Return-Path: Delivered-To: apmail-jakarta-jcs-users-archive@www.apache.org Received: (qmail 74785 invoked from network); 25 Jan 2007 18:49:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Jan 2007 18:49:03 -0000 Received: (qmail 61590 invoked by uid 500); 25 Jan 2007 18:49:09 -0000 Delivered-To: apmail-jakarta-jcs-users-archive@jakarta.apache.org Received: (qmail 61573 invoked by uid 500); 25 Jan 2007 18:49:09 -0000 Mailing-List: contact jcs-users-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "JCS Users List" Delivered-To: mailing list jcs-users@jakarta.apache.org Received: (qmail 61562 invoked by uid 99); 25 Jan 2007 18:49:09 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Jan 2007 10:49:09 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of lists@nabble.com designates 72.21.53.35 as permitted sender) Received: from [72.21.53.35] (HELO talk.nabble.com) (72.21.53.35) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Jan 2007 10:48:59 -0800 Received: from [72.21.53.38] (helo=jubjub.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1HA9eI-00058O-VM for jcs-users@jakarta.apache.org; Thu, 25 Jan 2007 10:48:38 -0800 Message-ID: <8638994.post@talk.nabble.com> Date: Thu, 25 Jan 2007 10:48:38 -0800 (PST) From: giriraj To: jcs-users@jakarta.apache.org Subject: RE: JCS shutdown causes JVM hang In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: giriraj.vengurlekar@gmail.com References: <8570883.post@talk.nabble.com> <8571705.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org Hi Aaron It would be helpful if you can tell me how to NOT go to disk in any circumstance. We would like to keep everything in memory if we can help it. We have enough memory so we think we can. How can i disbale writing to disk at all? Thanks Smuts, Aaron wrote: > > You might try turning off optimization on shutdown. > > jcs.auxiliary.DC.attributes.OptimizeOnShutdown=false > > > If you want to force the objects to go to disk when they pare put in the > cache, you can set the usage pattern to UPDATE > > jcs.default.cacheattributes.DiskUsagePatternName=UPDATE > > http://jakarta.apache.org/jcs/RegionProperties.html > > > This property determines how long to try and write to disk on shutdown > before giving up: > > jcs.auxiliary.DC.attributes.ShutdownSpoolTimeLimit=60 > >> -----Original Message----- >> From: giriraj [mailto:giriraj.vengurlekar@gmail.com] >> Sent: Wednesday, January 24, 2007 3:23 PM >> To: jcs-users@jakarta.apache.org >> Subject: RE: JCS shutdown causes JVM hang >> >> >> Thanks Aaron for the quick response. >> >> We use jcs 1.2.7.6 >> >> The cache size is about 5.5 gb. Rest is transient memory generated due > to >> processing. >> >> The cache.ccf has the following: >> >> ############################################################## >> ##### Default Region Configuration >> jcs.default=DC >> > jcs.default.cacheattributes=org.apache.jcs.engine.CompositeCacheAttribut > es >> jcs.default.cacheattributes.MaxObjects=@cache.max_obj@ (---2 million) >> > jcs.default.cacheattributes.MemoryCacheName=org.apache.jcs.engine.memory > .l >> ru.LRUMemoryCache >> jcs.default.cacheattributes.UseMemoryShrinker=true >> jcs.default.cacheattributes.MaxMemoryIdleTimeSeconds=-1 >> jcs.default.cacheattributes.ShrinkerIntervalSeconds=180 >> jcs.default.elementattributes=org.apache.jcs.engine.ElementAttributes >> jcs.default.elementattributes.IsEternal=true >> jcs.default.elementattributes.MaxLifeSeconds=-1 >> jcs.default.elementattributes.IdleTime=1800 >> jcs.default.elementattributes.IsSpool=true >> jcs.default.elementattributes.IsRemote=true >> jcs.default.elementattributes.IsLateral=true >> >> ############################################################## >> ##### Default Region Configuration by the JCS ObjectCache > implementations >> jcs.region.ojbDefaultJCSRegion=DC >> > jcs.region.ojbDefaultJCSRegion.cacheattributes=org.apache.jcs.engine.Com > po >> siteCacheAttributes >> jcs.region.ojbDefaultJCSRegion.cacheattributes.MaxObjects=2000000 >> > jcs.region.ojbDefaultJCSRegion.cacheattributes.MemoryCacheName=org.apach > e. >> jcs.engine.memory.lru.LRUMemoryCache >> >> jcs.region.ojbDefaultJCSRegion.cacheattributes.UseMemoryShrinker=true >> > jcs.region.ojbDefaultJCSRegion.cacheattributes.MaxMemoryIdleTimeSeconds= > -1 >> > jcs.region.ojbDefaultJCSRegion.cacheattributes.ShrinkerIntervalSeconds=6 > 0 >> jcs.region.ojbDefaultJCSRegion.cacheattributes.MaxSpoolPerRun=500 >> > jcs.region.ojbDefaultJCSRegion.elementattributes=org.apache.jcs.engine.E > le >> mentAttributes >> jcs.region.ojbDefaultJCSRegion.elementattributes.IsEternal=true >> jcs.region.ojbDefaultJCSRegion.elementattributes.MaxLifeSeconds=-1 >> > jcs.region.ojbDefaultJCSRegion.ojbDefaultJCSRegion.elementattributes.Idl > eT >> ime=1800 >> jcs.region.ojbDefaultJCSRegion.elementattributes.IsSpool=true >> jcs.region.ojbDefaultJCSRegion.elementattributes.IsRemote=true >> jcs.region.ojbDefaultJCSRegion.elementattributes.IsLateral=true >> >> >> # Primary Disk Cache-- faster than the rest because of memory key > storage >> > jcs.auxiliary.DC=org.apache.jcs.auxiliary.disk.indexed.IndexedDiskCacheF > ac >> tory >> > jcs.auxiliary.DC.attributes=org.apache.jcs.auxiliary.disk.indexed.Indexe > dD >> iskCacheAttributes >> jcs.auxiliary.DC.attributes.DiskPath=@cache.diskcache.file.path@ >> jcs.auxiliary.DC.attributes.MaxPurgatorySize=10000000 >> jcs.auxiliary.DC.attributes.MaxKeySize=1000000 >> jcs.auxiliary.DC.attributes.MaxRecycleBinSize=5000 >> jcs.auxiliary.DC.attributes.OptimizeAtRemoveCount=300000 >> jcs.auxiliary.DC.attributes.ShutdownSpoolTimeLimit=60 >> >> >> >> --------------------------------- >> >> >> >> >> >> >> >> Smuts, Aaron wrote: >> > >> > If you have a disk cache configured, then it will try to write the >> > contents of memory to disk on shutdown. 8gb is a lot of data to > write! >> > >> > What version of JCS are you using? >> > >> >> -----Original Message----- >> >> From: giriraj [mailto:giriraj.vengurlekar@gmail.com] >> >> Sent: Wednesday, January 24, 2007 2:37 PM >> >> To: jcs-users@jakarta.apache.org >> >> Subject: JCS shutdown causes JVM hang >> >> >> >> >> >> We have an application that loads up 5.5 gb of cached data. We use >> >> LRUMemoryCache. Once the cache is loaded, there is processing that >> > happens >> >> on the cached data and that ranges upto 7 gb max memory. ( > -Xmx=8gb) >> >> When the processing is done, when we do a System.exit() the > shutdown >> > hook >> >> is >> >> called and the application just hangs. I have attached the thread >> > dump. >> >> Has >> >> anyone seen this before or any advise would be helpful. >> >> >> >> Thanks >> >> http://www.nabble.com/file/5912/ErrorLog.txt ErrorLog.txt >> >> -- >> >> View this message in context: >> > http://www.nabble.com/JCS-shutdown-causes- >> >> JVM-hang-tf3084079.html#a8570883 >> >> Sent from the JCS - Users mailing list archive at Nabble.com. >> >> >> >> >> >> > --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org >> >> For additional commands, e-mail: jcs-users-help@jakarta.apache.org >> > >> > > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org >> > For additional commands, e-mail: jcs-users-help@jakarta.apache.org >> > >> > >> > >> >> -- >> View this message in context: > http://www.nabble.com/JCS-shutdown-causes- >> JVM-hang-tf3084079.html#a8571705 >> Sent from the JCS - Users mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org >> For additional commands, e-mail: jcs-users-help@jakarta.apache.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org > For additional commands, e-mail: jcs-users-help@jakarta.apache.org > > > -- View this message in context: http://www.nabble.com/JCS-shutdown-causes-JVM-hang-tf3084079.html#a8638994 Sent from the JCS - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org For additional commands, e-mail: jcs-users-help@jakarta.apache.org