Thanks everyone. I think this is what I would need to convince the team to
really get out of this. I appreciate the time you put into this and guiding
me appropriately.
Thanks again.
On Fri, Aug 7, 2020 at 10:24 AM Christopher Shannon <
christopher.l.shan...@gmail.com> wrote:
> In terms of
In terms of exporting I am not sure. I personally have never looked at
LevelDB. In terms of the error itself it seems like some of the files got
corrupt so not sure if it's possible to recover. If you want to export the
data you would probably need to write your own export tool to parse the
LevelDB support was removed in large part due to the absence of developers
willing to maintain the code and volunteers willing to provide support for
it on this mailing list. In the 5+ years I've been involved in this mailing
list, I don't recall ever seeing a LevelDB question answered (and I've
Any ideas? Or, is there a way to export these messages so that I can
recreate the broker data directory and import them?
On Fri, Aug 7, 2020 at 6:39 AM Ramesh Venkitaswaran
wrote:
> Understood, that LevelDB is deprecated, and we are trying to get this team
> to move to Artemis. However we still
Understood, that LevelDB is deprecated, and we are trying to get this team
to move to Artemis. However we still need this broker to run while the
migration is going on.
On Fri, Aug 7, 2020 at 5:48 AM Christopher Shannon <
christopher.l.shan...@gmail.com> wrote:
> LevelDB support has been
LevelDB support has been deprecated for many years now and is going to be
removed in the next version of ActiveMQ (5.17.0) so I would suggest trying
to migrate over to KahaDB.
On Fri, Aug 7, 2020 at 4:08 AM Ramesh Venkitaswaran
wrote:
> Hello
> We have a 3 node activemq 5.15 cluster with
Hello
We have a 3 node activemq 5.15 cluster with zookeeper using Level DB. It's
a very old system. However last night we started to get these errors and
the broker did not come up. Any ideas on how to fix this would be
appreciated. I can provide further log messages as needed, if sufficient
