; is a retained message published before the broker restart:
>
> "test 25 for a retained message 20170110"
>
> And this is exactly how clients get it before the broker restart.
>
> Instead, after broker restart, the same retained message is received by
> clients i
Did this happen while replaying the journal? This message means that
an acknowledgement was processed in the journal that doesn't have a
matching message. This log message would typically print out if you
were replaying the journal from the beginning to rebuild the index
because it's possible tha
es (before the
broker restart) are sent all with these weird characters. E.g., the following
is a retained message published before the broker restart:
"test 25 for a retained message 20170110"
And this is exactly how clients get it before the broker restart.
Instead, after broker restar
Hello,
have you found any solution for this ? we are facing a similar error, the
broker goes down and we have observed this message in the logs and are
unable to proceed further as the network team says there are no issues in
the network itself and everything is clean. the storage is also relative
Not sure if below is possible and couldn't find any options in the
documentation.
Is there a way to have the authentication part of a client connecting to
ActiveMQ be secured through PKI encryption and then the Data sent insecurely
over a normal http session.
One of the reasons being is to allow
