Closed argenstijn closed 1 day ago
Same for me.
Thanks for the workaround:
quarkus.cxf.http-conduit-factory=URLConnectionHTTPConduitFactory
Thanks for the report @argenstijn! Yes, we switched the default to VertxHttpClientHTTPConduit in 3.16. I'll have a look.
I can confirm both the issue and the workaround that it helps.
@argenstijn could you please provide a bit more context to those stack traces?
(1) Did you expect those calls going through $Proxy262.addUpdateParties()
to succeed because you were sure that the remote service was up and running? Could it not be that it was still starting or down for other reasons and the client was properly reporting that the service is not available?
(2) The warning about vert.x-eventloop-thread being blocked is very useful and points at a wrong implementation in Quarkus CXF: the eventloop is pumping the data from the response into a pipe with limited buffer that blocks when the consumer running on a worker thread is not fast enough to swallow the data. We need to fix it.
I wonder whether you have any hints that (1) and (2) have (not) the same root cause?
(2) The warning about vert.x-eventloop-thread being blocked is very useful and points at a wrong implementation in Quarkus CXF: the eventloop is pumping the data from the response into a pipe with limited buffer that blocks when the consumer running on a worker thread is not fast enough to swallow the data. We need to fix it.
I created a separate issue https://github.com/quarkiverse/quarkus-cxf/issues/1613 for this part and I have fixed it already.
@argenstijn, I am keeping this issue open, because it is not clear to me whether the fixes for #1613 and https://github.com/quarkiverse/quarkus-cxf/issues/1599 solve all your issues. Unless you provide more feedback I am going to release 3.17.0 in the coming days and let you check whether anything is left unresolved.
@ppalaga Sorry for my late response, i was gone for a week or so.
I think you solved the issue. I will check right now if it is fixed in the new version
@argenstijn no worries at all. It would still be great to hear whether 3.17.0, that is out since yesterday, has solved all your issues.
tested and issue is solved :)
I experience some problem using 3.16.X version when using the default http-conduit-factory. When using the 'quarkus.cxf.http-conduit-factory=URLConnectionHTTPConduitFactory' all seems to work again.
Edit by @ppalaga: I created a separate issue https://github.com/quarkiverse/quarkus-cxf/issues/1599 for the above