You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2015/03/31 00:40:52 UTC
[jira] [Commented] (DIRAPI-230) Connection to invalid host blocks
for 30 seconds
[ https://issues.apache.org/jira/browse/DIRAPI-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14387537#comment-14387537 ]
Emmanuel Lecharny commented on DIRAPI-230:
------------------------------------------
Good catch !
Yes, this is not a good idea to retry for 30 secs for obvious failures that are not depending from a remote peer temporarily being unreachable.
> Connection to invalid host blocks for 30 seconds
> ------------------------------------------------
>
> Key: DIRAPI-230
> URL: https://issues.apache.org/jira/browse/DIRAPI-230
> Project: Directory Client API
> Issue Type: Bug
> Affects Versions: 1.0.0-M28, 1.0.0-M29
> Reporter: Stefan Seelmann
> Fix For: 1.0.0-M30
>
>
> Connection to an invalid host like this
> {code:java}
> LdapNetworkConnection conn = new LdapNetworkConnection( "qwertyuiopasdfghjklzxcvbnm", 12389 );
> conn.connect();
> {code}
> results in a nice exception (InvalidConnectionException / UnresolvedAddressException).
> However it tries to connect for 30 seconds, only after that the exception is thrown. This looks like the default timeout is considered. I think the exception should be thrown faster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)