-
Notifications
You must be signed in to change notification settings - Fork 37.9k
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
Add HTTP 1.0 support on Reactor Netty [SPR-14964] #19531
Comments
Rossen Stoyanchev commented hi Yevhenii Melnyk thanks for logging this. It looks like a duplicate of #19510. |
Yevhenii Melnyk commented
|
Yevhenii Melnyk commented Still cannot handle handle multiple requests at the same time using Netty |
Rossen Stoyanchev commented What version of Reactor Netty are you using? You have to use 0.6.0.BUILD-SNAPSHOT snapshots (to be released tomorrow) and also make sure you don't have stale snapshots in your local repository. Sébastien Deleuze would you mind taking a look if it is still an issue since you worked on #19510? |
Yevhenii Melnyk commented I tried to run benchmark again on totally clean Ubuntu. It doesn't end, but if I make logging level Debug, I see that all requests are successful. Maybe something's wrong with the "ab" tool. |
Sébastien Deleuze commented I am going to test again with latest snapshots. |
Sébastien Deleuze commented Indeed the tests with multiple connection using |
Sébastien Deleuze commented After a lot of tests, it seems the issue observed come from the fact than I manage to reproduce it with a simple I have created issue for HTTP 1.0 support on both Reactor Netty and RxNetty bugtrackers. |
Sébastien Deleuze commented I move this issue to the 5.X backlog since it has been postponed to Reactor Netty 0.8. |
Superseded by reactor/reactor-netty#21 |
Yevhenii Melnyk opened SPR-14964 and commented
Scenario
Flux<Item>
, serialized as JSONResults
Web app based on Jetty,Tomcat and Undertow returns result in a reasonable amount of time.
Web app that runs using Reactor Netty or RxNetty doesn't finish. After benchmark timeouts server can't handle requests any more, even single ones from browser.
The following test was performed from localhost as well as from another computer in the same local network. The debug console output is attached.
Affects: 5.0 M3
Reference URL: reactor/reactor-netty#21
Attachments:
Issue Links:
The text was updated successfully, but these errors were encountered: