On 03/26/2017 10:55 AM, Emmanuel Lécharny wrote: > > > Le 26/03/2017 à 09:15, Stefan Seelmann a écrit : >> On 03/26/2017 04:37 AM, Emmanuel Lécharny wrote: >>> >>> Le 25/03/2017 à 23:42, Stefan Seelmann a écrit : >>>> Hi, >>>> >>>> I just noticed that some Studio tests that connect to invalid hostname >>>> or port fail. Reason is that in latest LDAP API trunk >>>> (1.0.0-RC3-SNAPSHOT) which is now used in Studio, the timeout (by >>>> default 30 seconds) seems to be also applied in case of invalid hostname >>>> and/or port, but by default the Studio tests timeout after 5 seconds. >>> I think this is specific to Studio. The default timeout is 30 seconds. >>> This is configurable, and can be set to something lower if needed. >>>> The tests "testConnectionWrongHost" and "testConnectionWrongPort" in >>>> "LdapConnectionTest" also take 30 seconds now. >>>> >>>> Is that intended behaviour? >>> This is the default since pretty much the beginning. >> I'm pretty sure it was different with 1.0.0-RC2. If the API was not able >> to connect because of invalid hostname (xyz cannot be resolved) or port >> (connection refused) it immediately threw an exception, even if the >> default timeout of 30 seconds was set. > > I don't remember having changed this, but it's easy to check. Can't it > be reated to the enviroment it was tested on ?
Maybe, I run locally on Linux (Arch) and Jenkins build also runs on Linux (Ubuntu 16.04). I setup a temporary Jenkins build that builds ApacheDS 2.0.0-M23 with API 1.0.0-RC1, here LdapConnectionTest is fast: https://builds.apache.org/view/A-D/view/Directory/job/dir-apacheds-M23/org.apache.directory.server$ldap-client-test/1/testReport/org.apache.directory.shared.client.api/LdapConnectionTest/ Compared with current trunk, testConnectionWrongHost and testConnectionWrongPort take 30 seconds each: https://builds.apache.org/view/A-D/view/Directory/job/dir-apacheds-ubuntu-deploy/org.apache.directory.server$ldap-client-test/1978/testReport/org.apache.directory.shared.client.api/LdapConnectionTest/ Anyway, it's not a big problem, Studio tests are already fixed. Kind Regard, Stefan
