I'm confused about the nature of your use-case. You originally said that
you were using ActiveMQ 5.16.3, but in this latest email you mention
intercepting things like ClusterTopologyChangeMessage_V4,
CreateSessionMessage_V2, CreateSessionResponseMessage, etc. which are used
exclusively by ActiveMQ
Thank you very much for the possible solutions.
I finally was able to try the approach with the interceptor and it works great
for intercepting messages send to the broker using SessionSendMessage to filter
the messages I want to intercept.
Unfortunately, it does not intercept messages sent from
Hi Karl-
You are welcome! Let us know how it goes, I would not expect any issues for an
upgrade between those versions.
-Matt Pavlovich
> On Nov 18, 2021, at 1:07 PM, Nordstrom, Karl wrote:
>
> Hello Matt,
>
> Thanks for the reply. Yes, I meant 5.15.12 and 5.16.3. I doubt I'll be able
> to
Hi Karl,
It's possible to setup a master/slave or NoB between the "old" version
and the "new" one, in order to do a "live" update.
Regards
JB
On 18/11/2021 17:12, Nordstrom, Karl wrote:
Is there documentation on how to upgrade ActiveMQ classic?
I want to upgrade our test cluster from 1.15.12
Tim,
Thanks for pointing out that only one broker accesses the data at a time.
I will do the upgrade in dev, then acceptance, before doing it in the
production environment.
---
Karl Nordström
Systems Administrator
Penn State IT | Application Platforms
From:
Only one ActiveMQ broker accesses the data store at a time. The passive
node is simply waiting to acquire the lock but will not access the data
store until the lock is acquired.
Yes, it's possible to do a rolling upgrade as you described,. The downtime
incurred will be minimal (just a standard fai
