Return-Path: Delivered-To: apmail-jakarta-jcs-users-archive@www.apache.org Received: (qmail 21671 invoked from network); 10 Sep 2009 15:59:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Sep 2009 15:59:04 -0000 Received: (qmail 44944 invoked by uid 500); 10 Sep 2009 15:59:04 -0000 Delivered-To: apmail-jakarta-jcs-users-archive@jakarta.apache.org Received: (qmail 44918 invoked by uid 500); 10 Sep 2009 15:59:04 -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 44908 invoked by uid 99); 10 Sep 2009 15:59:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Sep 2009 15:59:03 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jeffpk@gmail.com designates 209.85.132.248 as permitted sender) Received: from [209.85.132.248] (HELO an-out-0708.google.com) (209.85.132.248) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Sep 2009 15:58:56 +0000 Received: by an-out-0708.google.com with SMTP id d14so87247and.13 for ; Thu, 10 Sep 2009 08:58:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=e6vmv7oXGFPVrKwwcP6Ge9NICOazfK0XtDLRRcxAYZY=; b=lIAabHd4fLHqzeao+FSwz7nSVz+TzfHVe9xyUqu3Goie0AM5oMj62fga/586n6pwlQ 2ltGlDtdh86J3s1db4seibnmwh/YHYznWV1+dsB3Q7m/mWHVLI9wbBIi5M+CCnC+3OC+ 1nv0khB4Fek/3vDRtClqTR8Hc+3OZL0idvxgw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=w8YAg9ojBpRL9j6yJFrZYdvU1lbCAWhd5N/RCPDYqOIWIaML2n79EO+wWTKR8jG/vy Dj+MzLDgRAGZhIQ/6azGGA+kFg0DD2FyksC3rv6akB86Jot0d4VCss4V0GFeAqZhywVz 23xfc5/vLrxs/v/8Lm/ONTzwX74wW6vlaU5DI= MIME-Version: 1.0 Received: by 10.101.43.12 with SMTP id v12mr1794372anj.90.1252598315158; Thu, 10 Sep 2009 08:58:35 -0700 (PDT) Date: Thu, 10 Sep 2009 11:58:35 -0400 Message-ID: <330f74e70909100858g6f0e6860qcd71f7ee87136a8a@mail.gmail.com> Subject: Block Cache and garbaged entires? From: Jeffrey Kesselman To: JCS Users List Content-Type: multipart/alternative; boundary=001636ed72299f0d2f04733b45f6 X-Virus-Checked: Checked by ClamAV on apache.org --001636ed72299f0d2f04733b45f6 Content-Type: text/plain; charset=ISO-8859-1 Hi, I seem to remember a refernce to this earlier and think I am maybe running into it myself. I have a program that laods the cache up with a LOT of data pushign it basically as fast as the system can into the cache.Most of the data seems fine but a few entries are getting messed up or altogether lost. im not *positive* its JCS's fault yet but I seem to remembr a bug being mentioned on this lsit having to do with heavy write situations. SO I have a couple of questions: (1) Is there such a bug. (2) Is there a binary build yet with the fix and if so how do i get it? (3) Is it possible im not closing the cache right? Currently I do this... public void close() { CompositeCacheManager.getInstance().shutDown(); } -- ~~ Microsoft help desk says: reply hazy, ask again later. ~~ --001636ed72299f0d2f04733b45f6--