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 Lécharny (Jira)" <ji...@apache.org> on 2022/07/28 08:27:00 UTC
[jira] [Commented] (DIRAPI-381) ERR_04112_OP_FAILED_TIMEOUT when binding with TLSv1.3
[ https://issues.apache.org/jira/browse/DIRAPI-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17572307#comment-17572307 ]
Emmanuel Lécharny commented on DIRAPI-381:
------------------------------------------
It should be fixed with 2.1.0, as we changed the whole TLS layer in MINA 2.1.1, which is the version that is going to be embedded. To be double checked, of course...
> ERR_04112_OP_FAILED_TIMEOUT when binding with TLSv1.3
> -----------------------------------------------------
>
> Key: DIRAPI-381
> URL: https://issues.apache.org/jira/browse/DIRAPI-381
> Project: Directory Client API
> Issue Type: Bug
> Affects Versions: 2.1.0
> Environment: any (macos, windows, ubuntu)
> Reporter: Marius Oancea
> Priority: Major
>
> I'm using apache directory api version 2.1.0 to bind to a directory server using startTLS.
> In about 1 case of 100 the binding fails with
> {code:java}
> 16:16:19.071 [Test worker] ERROR org.apache.directory.ldap.client.api.LdapNetworkConnection - ERR_04112_OP_FAILED_TIMEOUT (Bind)
> 16:16:19.077 [Test worker] ERROR org.apache.directory.ldap.client.api.LdapNetworkConnection - ERR_04169_RESPONSE_QUEUE_EMPTIED The response queue has been emptied, no response was found.
> org.apache.directory.api.ldap.model.exception.LdapException: ERR_04170_TIMEOUT_OCCURED TimeOut occurred
> at org.apache.directory.ldap.client.api.LdapNetworkConnection.bind(LdapNetworkConnection.java:1549)
> ...
> org.apache.directory.api.ldap.model.exception.LdapException: ERR_04169_RESPONSE_QUEUE_EMPTIED The response queue has been emptied, no response was found.
> at org.apache.directory.ldap.client.api.LdapNetworkConnection.bind(LdapNetworkConnection.java:1578)
> {code}
> If I change the server configuration to use only TLSv1.2, it starts to work as expected.
>
> Also if I change my code to use api 2.0.0, it never fails (I assume because 2.0.0 is not using TLSv1.3 but TLSv1.2
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org