Hi,
It's been quite some time now and I just wanted to follow up for
archiving purposes. Since we updated everything to 5.13, we don't see
the issue any more. I am convinced it had been caused by the 5.7
client library.
Best regards,
Martin
On Sat, Jan 9, 2016 at 6:24 AM, Tim Bain wrote:
> Grea
Great, thanks for reporting back.
Tim
On Fri, Jan 8, 2016 at 1:04 PM, Martin C. wrote:
> Hello,
>
> sorry for the late response, missed the message. We are currently very
> confident that the issue was triggered because one of the client
> applications was still using a very old 5.7 library to
Hello,
sorry for the late response, missed the message. We are currently very
confident that the issue was triggered because one of the client
applications was still using a very old 5.7 library to connect to the
5.12 broker. Once we updated the client library in that particular
application, thing
Martin, did you ever resolve this issue?
If not, I'd recommend looking at the messages that expire to see if there
is a pattern to them.
Also, do you have a single broker, or a network of brokers? If the latter,
what is your networkTTL set to?
Tim
On Dec 2, 2015 9:50 AM, "Martin Carpella" wrot
Hi,
We've ran into some problems since we updated to Activemq 5.12.1. Our
most busy queue has stuck messages which also do NOT expire.
The queue has around 200 producers (each producer has it's own message
group, making sure messages of a producer do not overtake each other)
which send non-persist
Hi,
We've ran into some problems since we updated to Activemq 5.12.1. Our
most busy queue has stuck messages which also do NOT expire.
The queue has around 200 producers (each producer has it's own message
group, making sure messages of a producer do not overtake each other)
which send non-persist
