We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This will significantly improve performance, as we won't need one thread per connection anymore.
There's several possible routes, and several issues with some of them:
Directly using Apache's async HttpClient
Using vertx http client as engine through resteasy. This currently results in resteasy not recognising the vertx engine.
Using Apache's async httpcient as engine through resteasy. This latter seems to break the ReadTimeout configuration options, which is essential.
ReadTimeout
seems most straight-forward. 2. might depend on upgrading resteasy. 3. seems closest to a dead-end.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
This will significantly improve performance, as we won't need one thread per connection anymore.
There's several possible routes, and several issues with some of them:
Directly using Apache's async HttpClient
Using vertx http client as engine through resteasy. This currently results in resteasy not recognising the vertx engine.
Using Apache's async httpcient as engine through resteasy. This latter seems to break the
ReadTimeout
configuration options, which is essential.seems most straight-forward. 2. might depend on upgrading resteasy. 3. seems closest to a dead-end.
The text was updated successfully, but these errors were encountered: