Hi Tim and Christopher,
Thanks both for your very quick response. For now I decided to just stop
ActiveMQ, remove the store, and start ActiveMQ again. I believe that this is a
very acceptable solution in our case, but I will check with the team before we
update our production systems.
Thanks
Between those 2 versions the open OpenWire version used was upgraded as you
saw. This is not an issue when starting with a fresh store but as you are
seeing, when you upgrade from an existing store you will have old journal
files with messages laying around that were written using the older
OpenWi
Is doesn't resolve the question of why the index rebuild doesn't work, but
one path forward is to stand up a new broker with an empty KahaDB store and
then stand up this one with a networkConnector to the new one. Have all
clients connect to the new (empty) broker, which will be using the new
mess
Dear ActiveMQ users,
I just upgraded our ActiveMQ deployment from release 5.11.1 to 5.13.4 (I'm on
Ubuntu 14.04.5), which went pretty smooth. On this server ActiveMQ has been
updated many times so I was not surprised to get this in the logs during
startup:
WARN | Existing Store uses a differe
