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

WebClient fails on empty JSON array response [SPR-15794] #20349

Closed
spring-projects-issues opened this issue Jul 19, 2017 · 2 comments
Closed

WebClient fails on empty JSON array response [SPR-15794] #20349

spring-projects-issues opened this issue Jul 19, 2017 · 2 comments
Assignees
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

@spring-projects-issues spring-projects-issues commented Jul 19, 2017

Arnaud Cogoluègnes opened SPR-15794 and commented

Failure is org.springframework.core.codec.DecodingException: JSON decoding error: No content to map due to end-of-input.


Affects: 5.0 RC2

Issue Links:

  • #19097 Leverage Jackson non-blocking JSON parsing (and remove netty-buffer dependency)

Referenced from: commits spring-projects/spring-framework-issues@c55a3c7, spring-projects/spring-framework-issues@bd1edbc

@spring-projects-issues
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Jul 19, 2017

Arnaud Cogoluègnes commented

I created a PR with a repro project. Just start the server and then the client application.

@spring-projects-issues
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Jul 19, 2017

Rossen Stoyanchev commented

I can confirm the failure with Boot 2.0 RC2 (and Spring Framework 5.0 RC2). Upgrading to the latest Boot 2.0 snapshot (and hence picking up the latest Spring Framework 5.0 snapshot) works as expected.

The big change in this area since RC2 that probably explains the fix is #19097.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants