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.

Sign up for GitHub

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

Jump to bottom

java.lang.IllegalStateException: stream has already been operated upon or closed on CompositeX509KeyManager #7

Open
r3tina opened this issue Mar 13, 2019 · 0 comments · May be fixed by #8
Open

java.lang.IllegalStateException: stream has already been operated upon or closed on CompositeX509KeyManager #7

r3tina opened this issue Mar 13, 2019 · 0 comments · May be fixed by #8

Comments

@r3tina
Copy link

r3tina commented Mar 13, 2019

This appears to be caused by reusing the Stream member. When storing the X509KeyManager array in the constructor instead and creating a new Stream on demand, this is fixed.

I encountered this when using the composite manager with a secure LDAP client connection.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fixed stream has already been operated upon or closed exception ChrisRaye/CompositeJKS
1 participant
@r3tina