[jboss-jira] [JBoss JIRA] (WFLY-5377) Security realm using ldaps hangs forever during SSL handshake, when ldap server is killed
Martin Choma (JIRA)
issues at jboss.org
Mon Sep 21 23:56:00 EDT 2015
[ https://issues.jboss.org/browse/WFLY-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Choma moved JBEAP-1072 to WFLY-5377:
-------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-5377 (was: JBEAP-1072)
Workflow: GIT Pull Request workflow (was: CDW v1)
Component/s: Security
(was: Security)
Target Release: (was: 7.0.0.GA)
Affects Version/s: 10.0.0.CR1
(was: 7.0.0.DR9)
> Security realm using ldaps hangs forever during SSL handshake, when ldap server is killed
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-5377
> URL: https://issues.jboss.org/browse/WFLY-5377
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 10.0.0.CR1
> Reporter: Martin Choma
> Attachments: SecurityRealmLDAPSHandshakeHangs.pcap, StackTraceConnectTimeoutInLDAPSConnection.txt, StackTraceFromThreadDump.txt
>
>
> During failover testing we hit the problem of stuck thread. When ldap server is killed in particular time of ssl handshake EAP hangs and waits forever on response, which will never come. Causing thread to block forever. Same problem can be seen in LdapLoginModule using ldaps without specifying com.sun.jndi.ldap.connect.timeout value.
> Possible solution is to add option to declare com.sun.jndi.ldap.connect.timeout for security realm and provide some default non-empty value, e.g. 15 seconds.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list