Return-Path: 
 <dev-return-41097-apmail-directory-dev-archive=directory.apache.org@directory.apache.org>
X-Original-To: apmail-directory-dev-archive@www.apache.org
Delivered-To: apmail-directory-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id B05DE99CC
	for <apmail-directory-dev-archive@www.apache.org>;
 Wed, 13 Jun 2012 13:19:01 +0000 (UTC)
Received: (qmail 94293 invoked by uid 500); 13 Jun 2012 13:19:01 -0000
Delivered-To: apmail-directory-dev-archive@directory.apache.org
Received: (qmail 94224 invoked by uid 500); 13 Jun 2012 13:19:00 -0000
Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@directory.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@directory.apache.org>
List-Post: <mailto:dev@directory.apache.org>
List-Id: <dev.directory.apache.org>
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Delivered-To: mailing list dev@directory.apache.org
Received: (qmail 94215 invoked by uid 99); 13 Jun 2012 13:19:00 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jun 2012 13:19:00 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of gokturk.gezer@gmail.com
 designates 209.85.210.47 as permitted sender)
Received: from [209.85.210.47] (HELO mail-pz0-f47.google.com) (209.85.210.47)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jun 2012 13:18:53 +0000
Received: by dalh21 with SMTP id h21so1147911dal.34
        for <dev@directory.apache.org>; Wed, 13 Jun 2012 06:18:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=V9iejR/3EJQynX8Gf4bTrZtOjQZk6bHC3E53xFgPiO0=;
        b=ndninobWahG8wYrn/+2l+/ZeQE8oFClXCTqoA6sCeTJbhdqM7eTRA3v2WGE9LTepLZ
         orJbnUsWO1/ICl4L2t03rK9KATlcrnuknCIr99yQwQ/G5qms5YxvPlCzrTehxq8QlcIo
         ihr+oQcY8f6ORR1EX0EUCvC/TM6K11sLnFL4lzCKddXZNQFUuCQ03W/7gEU+Zag6SBg8
         eBv+kGGWSXqez6IUtPNDJmA7oUhgVOzFwworaqwBLqMy930SS0BxRaXZ/C2X55IDjf/A
         yJRTLL9P+5PSsdvekbzH+hWOIszCP5uFdkVvV24ahp49E4lM072/S980kucfxpR0Rjbr
         g00w==
MIME-Version: 1.0
Received: by 10.68.221.106 with SMTP id qd10mr51974861pbc.42.1339593512836;
 Wed, 13 Jun 2012 06:18:32 -0700 (PDT)
Received: by 10.68.64.74 with HTTP; Wed, 13 Jun 2012 06:18:32 -0700 (PDT)
Date: Wed, 13 Jun 2012 16:18:32 +0300
Message-ID: 
 <CAKjwzkp57jKJcychyW44qy4o=hmpJ9x-3yp_sOhKyipxcqjm8A@mail.gmail.com>
Subject: LdapOperation timeout issue.
From: =?UTF-8?B?R8O2a3TDvHJrIEdlemVy?= <gokturk.gezer@gmail.com>
To: Apache Directory Developers List <dev@directory.apache.org>
Content-Type: multipart/alternative; boundary=e89a8ff2550079de1004c25a6bda
X-Virus-Checked: Checked by ClamAV on apache.org

--e89a8ff2550079de1004c25a6bda
Content-Type: text/plain; charset=UTF-8

Hi Guys,

I have a little question with probably quick answers:

* Lets assume LdapServer is issuing some operation through
DirService.OperationManager. If i change the code in OperationManager to
obtain a Lock of target Partition which is exclusively owned by other
thread which is destroying the Partition. What happens then?

  -> Does ConcurrentReadWriteLock has some method to cause exception to be
thrown in Readers. I mean can i issue some kind of Abort on all waiting
readers when i'm actually destroying its attached object. (Yeah i'm Java
noob ATM :) )
  -> If this is not possible, does LdapServer's current threading model
ends the issued operation due to timeout or it just sits there(which would
be bad)?

Regards,
Gokturk

--e89a8ff2550079de1004c25a6bda
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Guys,<div><br></div><div>I have a little question with probably quick an=
swers:</div><div><br></div><div>* Lets assume LdapServer is issuing some op=
eration through DirService.OperationManager. If i change the code in Operat=
ionManager to obtain a Lock of target Partition which is exclusively owned =
by other thread which is destroying the Partition. What happens then?</div>
<div><br></div><div>=C2=A0 -&gt; Does ConcurrentReadWriteLock has some meth=
od to cause exception to be thrown in Readers. I mean can i issue some kind=
 of Abort on all waiting readers when i&#39;m actually destroying its attac=
hed object. (Yeah i&#39;m Java noob ATM :) )</div>
<div>=C2=A0 -&gt; If this is not possible, does LdapServer&#39;s current th=
reading model ends the issued operation due to timeout or it just sits ther=
e(which would be bad)?</div><div><br></div><div>Regards,</div><div>Gokturk<=
/div>

--e89a8ff2550079de1004c25a6bda--