you will want my customized atomix cluster manager, copied straight from this code, because i know how to make it perform fast, faster than hazelcast, whose default configuration also needs to be changed
suffice it to say this stuff is really complicated
i don't know who uses hazelcast with async servers in javaland
i also needed more clustering features
Wow that looks good!
So, the configuration is from a runner class, is there a way to configure with an archive or resource?
i'm confident that is supported
but i really wanted to avoid the XML properties file rabbit holes
if you wanna run the test you'll need mongo
but yeah you get it
K well is that I've a multimodule pom
How could I instantiate it?
@vietj Responding to your question about keep alive timeout. Some of our target servers are called very infrequently, i.e. 3 calls per hour. Target server is configured to close idle connections after 500s. Due to poor network, cost of creating SSL connection is extremely high in our case. Therefore we decided to keep connection alive in the pool by scheduling ping to target server every 6 minutes. Do you think connection pool could have similar mechanism inbuilt to prevent target server closing connection?
@kziomek that's interesting, I think it is better you have your own external ping because how you will ping depend on your server
i.e you could use an healthcheck endpoint to ping the server at
do you also create such connections eagerly ?
has anyone used resilience4j bulkheads in vertx?
@vietj Short answer is yes, in some cases, where network is very poor, we benefit from connection created eagerly and kept alive to reduce number of timeouts.
Which tool do you recommend for advanced tests with containers and reactive extensions? JUnit 4, 5 or Vert.x test library?
junit + vertx async library for testing
also I recommend the library for runnning containers from java
Testcontainers is awesome. I use it for all my e2e tests that involve elasticsearch, keycloak or even my own application. I even build a testcontainer which builds the container from the classes of my workspace. That way I can directly run cluster tests of my own application in my IDE. Crazy but good stuff ;)
Wow very thanks, I'll use it 😀
I've got a weird problem that I can't seem to get past. I've got several projects that have the same setup and Vert.x jar files (3.6.3), but this one will not return anything to the HTTP client if it's >= 128 bytes.
response.setStatusCode(200).end(responseBody.substring(0, 128)); hangs on the client. response.setStatusCode(200).end(responseBody.substring(0, 127)); will send. Any idea? The environment is the same, the router setup is the same, the call is the same. The data returned doesn't seem to make a difference other than the size of it.
The end() method in the HttpServerResponseImpl.class appears to complete when I step through it. (it gets past the this.conn.responseComplete(); method call)
It is a legit cursed project. I copied the pom.xml, renamed the module and re-imported and everything works. Kill me in the face.