The behavior you described is consistent with your networkTTL=1 setting
plus the following sequence of events:
1. Message produced to broker A.
2. Consumer connected to broker B, so A forwards the message to B.
3. Before the consumer can consume the message, it disconnects and
reconnects to A.
4.
Hi,
If you enable DLQ to non-persistent message (it's disabled by default),
then, IMHO, any message stored in DLQ should survive to broker restart
(else it's not really a DLQ).
Again, as non-persistent messages are not supposed to go in DLQ. To send
the non-persistent messages to DLQ, you have to
Can somone help me understand why a non-persistent message is "converted" into
a persistent message on entering DLQ?
It happens in RegionBroker, around line 733:
if (!message.isPersistent()) {
message.setPersistent(true);
message.setPro
Hi,
do you use a proxy (haproxy, ...) between the broker and the clients ?
On the other hand, the EOFException is often due to the clients which
don't connected currectly.
Regards
JB
On 30/01/2020 09:51, bhardwaj wrote:
> Hi team,
> Can anyone help me to resolve the below issue in active MQ.
>
Hi team,
Can anyone help me to resolve the below issue in active MQ.
I am getting this error whenever messages are posted to MQ in bulk about (30
lakhs Messages)
It can be resolved if we restart MQ and KAHA DB,
Please help me is there any way to eradicate this error and what is the
reason for thi
