-
Notifications
You must be signed in to change notification settings - Fork 356
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
POST request to grizzly-http-server times out #5812
Comments
I just tried to use latest 3.1 version ( |
I just found out what I have to set on my explicitly setting the HTTP version
when not explicitly setting the version, version
My question now is: why do I need to explicitly set my HTTP version when using jersey grizzly http server with version Thank you and BR, David |
Interestingly enough, setting the version just to the module
fixes the issue |
These lines are responsible for the change. Note that the file is a repackaged Jackson file, not of Jersey origin. READ_FULL_STREAM option has been added in Jackson 2.15, with a default value of TRUE. From the documentation:
As a workaround, instead of |
Thank you for your response and your findings. I tried as you proposed, insteada of I register w/
but I'm getting the following error:
which is true, as I do not depend on Is there any other way to disable the feature ? |
Sorry about this. The fix for it is already in the development branch. For the time being, add
|
I was just about to say that I tried this. but now I get
I think for now I just keep the setting at my http client to bind to HTTP version 1.1 . when the next version is released, what changes would I have to make to disable the feature ? |
I have put together #5816, which allows for better configuration of the JaxRSFeature for the Jersey Jackson module. |
Closing as finished. |
in the process of upgrading our code-base to Java21 (from Java17) I had to upgrade our Jersey version from
3.0.1
. I started with the latest one, which currently is:3.0.16
.On the client side I'm using the Java-HTTP-client (inlcuded in Java itself). I'm using Temurin as JDK/JRE.
When the services finally started again, I encountered the time-out for POST requests. Therefore I created a simple Maven project that starts a grizzly-http server, and a corresponding client - see https://github.com/divadpoc/grizzly-test .
In the end, I started downgraded step by step until I met version
3.0.11
, which works as expected..Am I missing anything that's necessary to include in my project to get any later version running as well ?
Thanks and BR
Update w/ errors/trace
On the client side I get:
On the server side I get:
The text was updated successfully, but these errors were encountered: