Re: Anyone using SmallRye Reactive Messaging with TomEE?

--0000000000004325760645878d7f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I've run Netty inside TomEE in the past without problems. As much as
possible, try to let TomEE manage thread pools seems to be a good practice.

On Tue, Dec 9, 2025 at 10:08=E2=80=AFAM Skander <skander.soltane@protonmail=
.com>
wrote:

> Hi everyone,
>
> I'm considering integrating SmallRye Reactive Messaging 4.31.0 (with
> either JMS or Kafka connectors) into a TomEE-based application and would
> like to hear from anyone who has already tried this.
> Has anyone successfully deployed SmallRye Reactive Messaging on TomEE in
> production? Did you encounter any issues or notice regressions with other
> TomEE features?
>
> I'm particularly concerned about the dependencies this brings in - mainly
> the Vert.x, Mutiny, and Netty stack:
>
> - vertx-core: 4.5.21
> - smallrye-mutiny-vertx-core: 3.19.1
> - mutiny: 2.9.3
> - netty-*: 4.1.125.Final (10+ netty modules)
>
> Plus the connector-specific JARs (kafka-clients 4.1.0 for Kafka, or the
> JMS connector).
>
> Before OpenLiberty integrated Vert.x, they documented some concerns about
> threading and resource management conflicts between Vert.x's event-loop
> model and servlet container threading [1] [2].
> I'm wondering if anyone has run into similar issues in TomEE - threading
> conflicts, classloader problems with Netty/Vert.x, performance impacts, o=
r
> anything else unexpected?
>
> Any feedback from real-world deployments would be really helpful.
>
> Thanks!
>
> Skander
>
> [1] https://github.com/OpenLiberty/open-liberty/issues/8962[2]
> https://github.com/OpenLiberty/open-liberty/issues/12472



--=20
Jonathan | [email protected]
Pessimists, see a jar as half empty. Optimists, in contrast, see it as half
full.
Engineers, of course, understand the glass is twice as big as it needs to
be.

--0000000000004325760645878d7f--