directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Kaplinger (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRSERVER-1012) TimeLimitExceededException with the embedded ADS
Date Fri, 16 Nov 2007 14:08:43 GMT

    [ https://issues.apache.org/jira/browse/DIRSERVER-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543078
] 

Todd Kaplinger commented on DIRSERVER-1012:
-------------------------------------------

Problem still occurs after upgrading to ADS 1.5.1.  

Unfortunately providing sample code is not possible since it would require more than a simple
command line program and it also is intermittent.  Can you tell us what we can provide in
terms of trace or a possible debug module to help diagnose this issue.  I would assume that
you can debug issues without having to reproduce in your own environment for these types of
issues.  I know it would be ideal to have a testcase but we are not exactly sure what is triggering
this issue.

> 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.


Mime
View raw message