Some more info about it here https://netty.io/wiki/tcp-fast-open.html
Given that Netty can makes use of it and Artemis can as well: if it's not
present in the doc it means we need to expose it in the acceptor
configuration (for epoll) and...we love contributions :)
But I suggest first to give it a
Hi Francesco,
I don't find anything in the Artemis docs about TCP_FAST_OPEN. It must not
be an exposed configuration on Artemis? Where do I find more on this?
Thanks,
Ben
On Fri, Jun 3, 2022 at 4:08 PM Francesco Nigro wrote:
> Are coming, not commenting: typo introduced by the the phone, sorr
Are coming, not commenting: typo introduced by the the phone, sorry!
Il ven 3 giu 2022, 22:07 Francesco Nigro ha scritto:
> Hi Ben,
>
> You can use TCP_FAST_OPEN on Artemis acceptors in case connections are
> commenting from the came clients (I don't remember if is an exposes Netty
> configurati
Hi Ben,
You can use TCP_FAST_OPEN on Artemis acceptors in case connections are
commenting from the came clients (I don't remember if is an exposes Netty
configuration) or...submit a PR to let Artemis separate (multiple) threads
to accept connections but, as you said, this is just an anti-pattern a
I'm running Artemis 2.14, and one of the systems publishing to it creates a
lot of separate tasks -- from its perspective. I can see on Artemis that
the Total connection count vs Total messages acknowledged is pretty close,
so it's apparent that the client system is making use of the anti-pattern
o
