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 (Resolved) (JIRA)" <ji...@apache.org> on 2011/11/22 17:32:40 UTC
[jira] [Resolved] (DIRAPI-47) LdapConnection.bind fails on timeout
but there was SSL handshake problem
[ https://issues.apache.org/jira/browse/DIRAPI-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny resolved DIRAPI-47.
-------------------------------------
Resolution: Fixed
This is very true. The problem is that we don't do anything when we receive an exception, but printing a stack trace :/
public void exceptionCaught( IoSession session, Throwable cause ) throws Exception
{
LOG.warn( cause.getMessage(), cause );
if ( cause instanceof ProtocolEncoderException )
{
...
}
else
{
cause.printStackTrace();
}
> LdapConnection.bind fails on timeout but there was SSL handshake problem
> ------------------------------------------------------------------------
>
> Key: DIRAPI-47
> URL: https://issues.apache.org/jira/browse/DIRAPI-47
> Project: Directory Client API
> Issue Type: Bug
> Affects Versions: 1.0.0-M6
> Reporter: Martin Zdila
>
> Affects 1.0.0.M6-SNAPSHOT (from today).
> When SSL handshake error occurs LdapConnection.bind waits for timeout. Instead it should fail immediately.
> I can see SSL exception in the logs and after couple of seconds I get timeout exception.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira