directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <>
Subject [jira] Commented: (DIRSERVER-1012) TimeLimitExceededException with the embedded ADS
Date Fri, 16 Nov 2007 15:11:43 GMT


Emmanuel Lecharny commented on DIRSERVER-1012:

We don't have any fixed date for the 1.5.2 release. However, we have done a lot of modifications
in a bigbang branch we want to inject into the trunk very shortly. This will be the perfect
timing to have a 1.5.2 release, but as it will cost us at least one week to cut this release,
and as we are really under heavy pressure right now, we can't guarantee that we will be able
to do that before mid-december.

Here are the issues we have to work on for this release :
- we have no Unix installer currently
- the configuration format has changed, and we need to renew the documentation
- there are around 85 open bugs for 1.5.2, and even if we postpone some of them, we really
want to fix some of them
- this is a terrible period to work on open source because we are all overhelmed with real
life projects ...

I would like to be a little bit pessimistic in saying that we will release for the end of
this year, the good news would be that we release earlier. Who knows ? ;)

Btw, any help on the installer would be very welcomed !

> TimeLimitExceededException with the embedded ADS
> ------------------------------------------------
>                 Key: DIRSERVER-1012
>                 URL:
>             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
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.

View raw message