I don't think there's any current fallback option for SQL right now.
Contributions are welcome though so if you wanted to take a shot at adding
a property for that you could create a PR.
We might give it a shot - should we follow
https://activemq.apache.org/contributing.html and create a patch
I don't think there's any current fallback option for SQL right now.
Contributions are welcome though so if you wanted to take a shot at adding
a property for that you could create a PR.
On Wed, Apr 17, 2019 at 4:28 PM mikmela wrote:
> We seems to experience the same issue upgrading from 5.6.0 t
We seems to experience the same issue upgrading from 5.6.0 to 515.8, but in
our case we use SQL database as a message store. As it was mentioned and
confirmed by us KahaDB has a fallback capability when it encounter older
(Version 6) of OpenWire.
Unfortunately, it looks like for SQL databases there
The issue we have is that we have a number of scheduled tasks in the old
queue. What I ended up doing was writing a program to read out of the
old queue and then manually enqueue the tasks in the new queue. It was a
little awkward, but it got the job done.
On Mon, Jun 5, 2017, at 10:04 PM, Tim Bai
What Chris described is how to load the existing messages into your new
broker. That has always seemed clunky to me because there is no way to
store messages in multiple OpenWire formats (which means your new broker's
store is stuck forever on the old broker's OpenWire version), so the option
that
What kind of errors are you getting? If it's related to data marshalling
then it could be because there was an Openwire upgrade (Openwire is the
format the messages are stored in) done in the KahaDB store between those
versions which could be causing your issue. I think there was also some
schedul
Good Day,
I've been working on migrating servers and upgrading from 5.10.0
to 5.14.5.
We have a number of scheduled tasks and I want to preserve those along
with other items in the queue. I tried moving the files in kahadb to the
new server (after shutting down both servers), but have run into
mul
