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

Document the async use case with VertxHttpClientHTTPConduit #1619

Closed
ppalaga opened this issue Nov 27, 2024 · 0 comments · Fixed by #1715
Closed

Document the async use case with VertxHttpClientHTTPConduit #1619

ppalaga opened this issue Nov 27, 2024 · 0 comments · Fixed by #1715
Labels
documentation Improvements or additions to documentation

Comments

@ppalaga
Copy link
Contributor

ppalaga commented Nov 27, 2024

the lazy client initialization on first use may block if the WSDL URL is set via quarkus.cxf.client."client-name".wsdl. In that case the even loop would be blocked and the best practice is to suspend to a worker thread strainght away, e.g. by annotating the REST endpoint by @io.smallrye.common.annotation.Blocking
Edit: this is not needed anymore. We always dispatch the client to a worker thread (unless it is on a worker thread already) to solve #1685

Another general VertxHttpClientHTTPConduit topic: VertxHttpClientHTTPConduit does not honor default SunJSSE truststore - see #1665. Once we have quarkusio/quarkus#45175 it will be easier to set a CXT client to use $JAVA_HOME/lib/security/cacerts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant