-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Behavior unexpected sending bytes compressed with gzip setting property 'resteasy.gzip.max.input' #40806
Comments
cc @jamezp |
fix checkstyle rest-client tests disable test after resolve quarkusio/quarkus#40806
I can't seem to reproduce this with plain RESTEasy using the Jakarta SeBootstrap. I assume the issue is somewhere in Quarkus, but I can't figure out how to debug through the test. I'm not familiar with the Quarkus QE Test Framework. |
Closing the issue, it's test case design issue where recursive call through rest client is made in |
Good to know. I just wasn't sure what it was and I unfortunately just don't have much experience with Quarkus at all. One of these days I'll be able to dig into it more :) |
Describe the bug
I'm encountering a
java.net.SocketTimeoutException: Read timed out
exception when I send Gzip compressed data from my test to a Quarkus endpoint.I've configured my application.properties with:
I've created
byte[] gzip_max_input_1K = new byte[1000];
that after I compress in gzip data then I send to the Quarkus endpoint and then in the logs, I can see the error mentioned.My reproducer:
git clone -b gzip-input-bytes-reproducer https://github.com/jcarranzan/quarkus-reproducer.git
Logs with the error:
Expected behavior
The server successfully processes Gzip data sent from the test and response 200 OK.
Actual behavior
org.jboss.resteasy.spi.UnhandledException: jakarta.ws.rs.ProcessingException: RESTEASY004655: Unable to invoke request: java.net.SocketTimeoutException: Read timed out
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: