Apache Directory Project - [jira] Commented: (DIRSERVER-1012) TimeLimitExceededException with

This is Interesting: Free IT Magazines  
Home > Archive > Apache Directory Project > November 2007 > [jira] Commented: (DIRSERVER-1012) TimeLimitExceededException with





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author [jira] Commented: (DIRSERVER-1012) TimeLimitExceededException with
Todd Kaplinger (JIRA)

2007-11-16, 1:11 pm


[ https://issues.apache.org/jira/brow...action_12543091 ]

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

Thanks for the quick response. I was not watching this bug so I was unaware that you had responded to the prior one so quickly. We use maven to resolve our projects so we would have to wait for an official release to validate the changes. Do you know w
hen the current trunk will be considered finalized?

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


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com