Hi,
I have a java artemis (2.3.0) consumer listening to a "my-topic.#"
if I listen and produce on the same artemis instance, It's working
fine.
However, moving the consumer to another instance in a static configured
cluster, the artmis receiving the messages:
12:01:18,873
WARN [org.apache.activ
Hi,
Try 2.2.0 snapshot.
A few mem issues has been resolved since 2.1.0.
/hw
Sendt fra min iPhone
> Den 25. jul. 2017 kl. 11.06 skrev Deomisr :
>
> Hi,
>
> With my broker Mqtt configuration, it seems a memory leak appears after 3
> days.
> Indeed the memory increase but each full GC and GC not
Hi,
We do dev in prod😉
I actually since posting built the 2.2.0-SN from yesterday and I'll see if it
makes any difference.
I'll add the detection option if needed
Thx.
/hw
Sendt fra min iPhone
> Den 3. jun. 2017 kl. 09.19 skrev Michael André Pearce
> :
>
> If you have the ability (not sure
Hi,
I'm running artemis 2.2.0 as a docker container.
I'm collecting MQTT messages an these are consumed by a JMS consumer
(artemis-jms-client)
It's running fine for a while, but suddenly this appear (docker *-
json.log):
{"log":"19:16:12,338 WARN
[org.apache.activemq.artemis.core.remoting.impl.
