Comments (4)
thanks I am not sure this is achievable unless as you said you set an exception handler on the connection.
The pool itself does not interact with the connection exception handler, since the connection exists outside of the pool and one could set an exception handler on it and the pool would overwrite it.
as a facility, you can set a connect handler on the HttpClientBuilder that would facilitate the setup of such strategy instead of melting that in your request/response code
from vert.x.
Thanks for looking at this, but can't we update the connection's exceptionHandler
when it goes back to its pool, or as soon as the response is 100% read ?
Such exception handler could log the disconnection as warning instead of error since there will be no immediate issue with the connection being lost.
from vert.x.
thing is that a connection can be partially in the pool like HTTP/2
from vert.x.
I saw that HTTP/1.1 and HTTP/2 connections both have a notion of active stream, so I guess we could hook something here and update the connection exception handler as soon as this active stream count reaches 0.
What do you think ?
from vert.x.
Related Issues (20)
- Configurable socket keep alive interval HOT 3
- Hash based load balancing policy
- ver.4.5.6 HttpServerRequest.isExpectMultipart wrong results returned.
- Vertx pooled allocator should be the same as Netty
- Fix for CVE-2024-29025
- Fix for CVE-2024-29025
- BlockedThreadChecker does not check a parking event loop virtual thread HOT 8
- Websocket batch processing / read completion event HOT 3
- webSocketHandler does not accept incoming websocket connection since vertx-core version 4.5.6 and later HOT 1
- Jackson's Hybrid pool should avoid using predicates to verify Thread::isVirtual HOT 1
- Provide an option to wait for all currently-being-processed / currently-queued requests / events to complete before closing vertx HOT 1
- JsonObject: The equals method fails when comparing integers with floats. HOT 1
- Request .send method invocation starts failing from 4.5.5 onward HOT 11
- route BodyHandler before ProxyHandler, response [ERROR] [2024-04-17 18:57:27] ?.?(?) | Connection was closed HOT 2
- Vertx eventbus not working even after cluster formation
- Getting HttpClosedException: Connection was closed for alternate HTTP API calls HOT 1
- Previously clustered instances incorrectly cached
- Vert.x does not respond appropriately for HTTP/1.1 request containing no Host header HOT 3
- Vertx Compatibility issue HOT 1
- HttpRequestImpl#connectTimeout does not support Fluent
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from vert.x.