jimbogithub

> for building the client in the reactive version, is there any reason for not using `ClientBuilder.newClient().register(new ClientRequestLogger()).register(new ClientResponseLogger());` to create the client? In my case no. I simply point...

> > for building the client in the reactive version, is there any reason for not using `ClientBuilder.newClient().register(new ClientRequestLogger()).register(new ClientResponseLogger());` to create the client? > > In my case no....

Another issue with the **SSE Client Reactive** is that it does not propagate the entity in the WebApplicationException. I think this is a known issue as there are comments in...

FYI, I switched to Mutiny SSE as SSE Client Reactive started rapidly leaking memory (from 2.9.x?) - appears Buffers not being closed.

> Do you have a memory dump or a sample project that exhibits this behavior? See this branch of the reproducer: https://github.com/jimbogithub/sse/tree/mem-leak Start the sse-server-reactive then the sse-client-reactive. 2.7.x was...

@geoand Did you use the branch I indicated?

What process are you monitoring? That loaded class count does not look plausible to me.  

@geoand I've re-tested my assertion that it was related to the Jackson/JSON integration - it isn't. Reproducer works with server sending PLAIN_TEXT and client doing simple `event.readData()`. So no need...

@lunarfs Like #707 I'm a +1 for adding `3.0.1` support (`3.1.0` doesn't have the bug fix I need). Could you add that as well?

@lunarfs I'm testing this out in my local environment. Looks pretty good except for a couple of issues if I have `KAFKA_CREATE_TOPICS` enabled: 1. `KAFKA_PORT` is used by `create-topics.sh` in...