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. Once that's complete, you can tear down the 5.3 broker.
Tim On Thu, Jun 3, 2021, 1:50 PM Lipika Rout <lipikar...@gmail.com> wrote: > 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 restart, > but this time this didn't happen. > > Below are the statistics for one of the journal files. > > Destination statistics: > - Topics: 0. > - Queues: 0. > > Commands without destination: > + CmdType: KAHA_TRACE_COMMAND (Count: 51407, TotalSize: 31.5 MB (33034964), > ~AvrgSize: 642 Byte(s) (642), LastBigSize: 2.39 KB (2448), LastSize: 79 > Byte(s) (79)) > All commands: 51407 (Total size: 31.5 MB (33034964). > ----------------------------------------------------------- > Command statistics: > - Topics: 0 (messages: 0, +subscriptions: 0, -subscription: 0). > - Queues: 0 (messages: 0). > - Other messages: 51407. > > Commands: > + CmdType: KAHA_TRACE_COMMAND (Count: 51407, TotalSize: 31.5 MB (33034964), > ~AvrgSize: 642 Byte(s) (642), LastBigSize: 2.39 KB (2448), LastSize: 79 > Byte(s) (79)) > All commands: 51407 (Total size: 31.5 MB (33034964). > > Looking for a solution to replay these messages. > > Thanks > Lipika Rout >
