Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 79447 invoked from network); 2 Nov 2007 13:29:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Nov 2007 13:29:16 -0000 Received: (qmail 21240 invoked by uid 500); 2 Nov 2007 13:29:04 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 21010 invoked by uid 500); 2 Nov 2007 13:29:03 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 20999 invoked by uid 99); 2 Nov 2007 13:29:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Nov 2007 06:29:03 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Nov 2007 13:29:33 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 9FA83714201 for ; Fri, 2 Nov 2007 06:28:51 -0700 (PDT) Message-ID: <9305372.1194010131650.JavaMail.jira@brutus> Date: Fri, 2 Nov 2007 06:28:51 -0700 (PDT) From: "Emmanuel Lecharny (JIRA)" To: dev@directory.apache.org Subject: [jira] Commented: (DIRSERVER-1012) TimeLimitExceededException with the embedded ADS In-Reply-To: <16697258.1185935993145.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DIRSERVER-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539578 ] Emmanuel Lecharny commented on DIRSERVER-1012: ---------------------------------------------- I would suggest that another test is done using ADS 1.5.1, and providing a sample code to demonstrate the bug, instead of a 9 Mb long log which does not help a lot. > TimeLimitExceededException with the embedded ADS > ------------------------------------------------ > > Key: DIRSERVER-1012 > URL: https://issues.apache.org/jira/browse/DIRSERVER-1012 > Project: Directory ApacheDS > Issue Type: Bug > Affects Versions: 1.5.0 > Environment: Win XP SP2 / J2RE 1.5.0 / eclipse 3.2.0 / ADS 1.5.0 > Reporter: hirot > Fix For: 1.5.2 > > Attachments: trace-log-0(Includes Timout Failure).txt > > > I'm using embedded Apache Directory Server for the unit testing with JUnit in eclipse. > The environment is : > - Win XP SP2 > - J2RE 1.5.0 > - eclipse 3.2.0 > - ADS 1.5.0 > Only when a search takes over around 1 second, javax.naming.TimeLimitExceededException is thrown as cited in the following : > javax.naming.TimeLimitExceededException: [LDAP: error code 3 - failed on search operation]; remaining name 'o=hq,dc=myco,dc=com' at > When a same search takes less than 1 second, it successfully returns results. > I'm sure to set 30000 ms to the client side timeout using javax.naming.directory.SearchControls.setTimeLimits(int ms), so the exception is caused by the server side timeout, I suppose. > Is the server side timeout of ADS 1 second ? > Is there any measure to lengthen the timeout ? > (I tried MutableServerStartupConfiguration.setMaxTimeLimit(int arg0). But I am not sure whether a parameter specifies ms or second, and it doesn't seem to work well in the embedded ADS at least because a search successfully returns results when I set 0 or 1 to "MaxTimeLimit".) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.