Return-Path: Mailing-List: contact turbine-jcs-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list turbine-jcs-user@jakarta.apache.org Received: (qmail 15785 invoked by uid 98); 5 Dec 2002 19:44:57 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Received: (qmail 15748 invoked from network); 5 Dec 2002 19:44:55 -0000 Received: from daedalus.apache.org (HELO apache.org) (63.251.56.142) by nagoya.betaversion.org with SMTP; 5 Dec 2002 19:44:55 -0000 Received: (qmail 93556 invoked by uid 500); 5 Dec 2002 19:43:45 -0000 Received: (qmail 93547 invoked from network); 5 Dec 2002 19:43:45 -0000 Received: from amer-mta02.csc.com (20.137.2.248) by daedalus.apache.org with SMTP; 5 Dec 2002 19:43:45 -0000 Received: from amer-mta02.csc.com (localhost [127.0.0.1]) by amer-mta02.csc.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id gB5JhqQ14110 for ; Thu, 5 Dec 2002 14:43:52 -0500 (EST) Received: from csc.com (va-fch31.csc.com [20.6.39.231]) by amer-mta02.csc.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id gB5JhqQ14063 for ; Thu, 5 Dec 2002 14:43:52 -0500 (EST) Subject: Is this defect ??? To: Turbine JCS Users List X-Mailer: Lotus Notes Release 5.0.4a July 24, 2000 Message-ID: From: "Sunil Pandit" Date: Thu, 5 Dec 2002 13:43:37 -0600 X-MIMETrack: Serialize by Router on VA-FCH31/SRV/CSC(Release 5.0.8 |June 18, 2001) at 12/05/2002 02:43:55 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hello JCS Users I came across an interesting defect in JCS . During an Initialization of JCS instance when it creates a CompositeCache instance, It creates an instance of ElementEventQueue. ElementEventQueue further creates a thread in form of an instance of QProcessor. This thread is never destroyed. If we test our application under heavy load we found that several of these threads remain active. This thread is created per instance of CompositeCache and therefore should be destroyed when the composite cache is disposed. Also there is one more defect in JCS in same context. To correct the above defect I thought I can use ElementEventQueue::Destroy method which calls interrupt on QProcessor. The run method for this thread calls Thread::Destroy method which is unimplemented in JDK 1.4 . So we just modified the run method to set the destroy flag to true on Interrupt event so that the thread can gracefully exit. Can JCS team throw some light on this issue ? Thanks Sunil