Georgios Andrianakis comments

Results 773 comments of


                                            Georgios Andrianakis

"IOException: Connection was closed" when retrying non-WebApplicationExceptions

> I'm having similar issues with a container health check implementation utilizing a number of resteasy reactive rest clients. Just to make sure I understand, you are using the REST...

"IOException: Connection was closed" when retrying non-WebApplicationExceptions

@vietj @cescoffier I assume the Vert.x HTTP client should remove closed connections from the pool, right?

"IOException: Connection was closed" when retrying non-WebApplicationExceptions

Thanks @vietj

"IOException: Connection was closed" when retrying non-WebApplicationExceptions

It's unclear and needs further investigation

"IOException: Connection was closed" when retrying non-WebApplicationExceptions

That's the plan

Kubernetes client native integration test OOMs (GC overhead limit reached) with -Xmx5g

cc @manusa

[RestEasy Reactive Client] Use AsyncInputStream for Posting InputStream

Very nice. This will take some time to review, more that the few minutes I currently have on my phone 😎

[RestEasy Reactive Client] Use AsyncInputStream for Posting InputStream

I remember @vietj saying we should use `pipe` instead of `pump` :)

[RestEasy Reactive Client] Use AsyncInputStream for Posting InputStream

@vietj can you have a look at this as it very intense on the Vert.x side? Thanks

[RestEasy Reactive Client] Use AsyncInputStream for Posting InputStream

Hi @fredericBregier Those commits are already part of Quarkus 3.8.3. I am sorry that I had not realized my PR was essentially doing the same thing as yours.