Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ldapRegistry-3.0 does not configure a read timeout for JNDI connections #3383

Closed
jvanhill opened this issue May 1, 2018 · 0 comments · Fixed by #3635
Closed

ldapRegistry-3.0 does not configure a read timeout for JNDI connections #3383

jvanhill opened this issue May 1, 2018 · 0 comments · Fixed by #3635
Assignees
Labels
release bug This bug is present in a released version of Open Liberty release-18.0.0.2 team:Wendigo East

Comments

@jvanhill
Copy link
Contributor

jvanhill commented May 1, 2018

The ldapRegistry-3.0 feature does not allow the user to configure, nor does it configure implicitly a read timeout on the JNDI context. This can lead to hangs when an LDAP server does not respond.

Set the read timeout either based on the connect timeout that is already exposed or add a separate read timeout. This value should align closely with the "searchTimeout" used on the SearchControls as the time limit for a search operation.

@jvanhill jvanhill added team:Wendigo East release bug This bug is present in a released version of Open Liberty labels May 1, 2018
@jvanhill jvanhill changed the title ldapRegistry-3.0 configure a read timeout for JNDI connections ldapRegistry-3.0 does not configure a read timeout for JNDI connections May 1, 2018
@jvanhill jvanhill self-assigned this May 18, 2018
jvanhill pushed a commit to jvanhill/open-liberty that referenced this issue May 24, 2018
jvanhill pushed a commit that referenced this issue May 29, 2018
Issue #3383: Add LDAP registry JNDI read timeout.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release bug This bug is present in a released version of Open Liberty release-18.0.0.2 team:Wendigo East
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants