Lipika (the OP) responded directly to me with the following content:
We didn't clean start activemq during upgrade. So messages were already
there in the queue when we just upgraded the activemq jar version and
restart the Tomcat server without following any of the migration steps. I
tried to reco
I was referencing the "Pure static networks" section near the bottom of
https://activemq.apache.org/networks-of-brokers. That ensures that messages
are propagated off the 5.3 broker and onto the 5.16 broker even if no
consumer for those destinations is currently connected to the 5.16 broker.
Also,
What does "include all destinations in the 5.3 -> 5.16 direction, to force
all messages to be transferred" entail?
On Fri, Jun 4, 2021, 5:45 AM Tim Bain wrote:
> One option would be to load the 5.3 data file into a new temporary 5.3
> broker and configure it to make a network of brokers with you
One option would be to load the 5.3 data file into a new temporary 5.3
broker and configure it to make a network of brokers with your 5.16.0
broker. You'll likely want to statically include all destinations in the
5.3 -> 5.16 direction, to force all messages to be transferred to the
5.16.0 broker.
Hello,
We are using activemq embedded with Tomcat v9.0.26. Recently we upgraded
activemq jar from v5.3.0 to 5.16.0 without realizing that messages stopped
processing for a month in one of the nodes. We are trying to recover data
from 2 journal log files. Usually this happens automatically after re
