-
Notifications
You must be signed in to change notification settings - Fork 257
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
RESTEASY003765: Response is closed #1771
Labels
Comments
@niallrox would you be able to provide a small Github repository that showcases the problem (i.e. your classes and configuration from above)? |
Unfortunately, I can't share the whole repository, it's private. However, I will create a small repo that reproduces the same issue and easy to run. I'll do it approximately in 2 days. |
niallrox
pushed a commit
to niallrox/keycloak-logbook
that referenced
this issue
Jun 3, 2024
@lukasniemeier-zalando I've created the MRE repo |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello.
Exception that response is already closed is thrown, while involve logbook into keycloak admin client.
Steps to reproduce.
Using
SB3
and
Bean with client
application.yml
This is the log
And the error
jakarta.ws.rs.client.ResponseProcessingException: java.lang.IllegalStateException: RESTEASY003765: Response is closed.
I think after logbook read and log the response, client can't parse it, because you can't read response more than once. However, I haven't found another solution or sink implementation which could provide me that opportunity.
Thanks in advance.
The text was updated successfully, but these errors were encountered: