Return-Path: Delivered-To: apmail-jakarta-turbine-jcs-dev-archive@www.apache.org Received: (qmail 82683 invoked from network); 15 Sep 2004 08:12:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 15 Sep 2004 08:12:15 -0000 Received: (qmail 66892 invoked by uid 500); 15 Sep 2004 08:12:14 -0000 Delivered-To: apmail-jakarta-turbine-jcs-dev-archive@jakarta.apache.org Received: (qmail 66868 invoked by uid 500); 15 Sep 2004 08:12:13 -0000 Mailing-List: contact turbine-jcs-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Turbine JCS Developers List" Reply-To: "Turbine JCS Developers List" Delivered-To: mailing list turbine-jcs-dev@jakarta.apache.org Received: (qmail 66847 invoked by uid 99); 15 Sep 2004 08:12:13 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from [192.35.17.28] (HELO goliath.siemens.de) (192.35.17.28) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 15 Sep 2004 01:12:12 -0700 Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by goliath.siemens.de (8.12.6/8.12.6) with ESMTP id i8F8C7ec001644 for ; Wed, 15 Sep 2004 10:12:09 +0200 Received: from [139.25.11.53] (mhpaddrc.mch.sbs.de [139.25.11.53]) by mail3.siemens.de (8.12.6/8.12.6) with ESMTP id i8F8BufU019009 for ; Wed, 15 Sep 2004 10:12:06 +0200 Message-ID: <4147F931.8050201@siemens.com> Date: Wed, 15 Sep 2004 10:11:29 +0200 From: Eduardo Estefano User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Turbine JCS Developers List Subject: Re: Monitoring JCS References: <002401c49a6d$44e3f780$7e03a8c0@patni.com> In-Reply-To: <002401c49a6d$44e3f780$7e03a8c0@patni.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N There is an admin servlet that will give you some statistics on each cache. I'm not sure if it has the option to tell you what objects are inside the cache though. Rajkumar Singh wrote: >Hi > >How can we monitor the objects that are added, removed or updated in the JCS >using the JCS API? > >If JCS does not have such support then is there anyway to monitor the cache >using some other utility? I have used the dumpMap() and dumpCacheEntries() >of LRUMemoryCache in my update() method of a Java class that extends >LRUMemoryCache . The desription for these method says that "Dump the cache >entries from first to list for debugging". But I didn't get any output in my >log file. > >I am using log4j-1.2.7.jar file. My application server is Sybase EA Server. > >Thanks >Raj > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: turbine-jcs-dev-unsubscribe@jakarta.apache.org >For additional commands, e-mail: turbine-jcs-dev-help@jakarta.apache.org > > > --------------------------------------------------------------------- To unsubscribe, e-mail: turbine-jcs-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: turbine-jcs-dev-help@jakarta.apache.org