This is the way KahaDB currently works. There is no way to keep around the durable subscriptions (other than the index) because then KahaDB would never be able to GC any files. The main way I can think of to fix this would be to do some sort of compaction, as Tim pointed out in the comments of AMQ-4212. However, compaction would not be a trivial thing to implement.
On Fri, Dec 25, 2015 at 10:00 AM, Tim Bain <tb...@alumni.duke.edu> wrote: > Chris, > > Sorry no one responded to you before now, but this certainly does sound > like AMQ-4212 didn't fix all causes of the problem. Can you submit a bug > in JIRA and attach a set of data files and the corresponding index that > will demonstrate the problem? > > Thanks, > Tim > On Sep 4, 2015 7:03 AM, "ChristianWander" <ch...@piffedeckel.de> wrote: > > > Hi, > > > > I'm using ActiveMQ 5.10.2 and the included example code > > (jms-example-durable-sub) to play around with durable subscriptions. > > > > The examples work fine and the broker remembers the durable subscriptions > > when the consumer goes offline and the broker is restarted. > > > > However, if I stop the broker and delete the files db.data and db.redo to > > enforce a rebuild of the kahadb index according to here > > <https://access.redhat.com/solutions/276323> , the broker forgets about > > the > > offline durable subscriptions. > > > > Shouldn't this be fixed with [AMQ4212] > > <https://issues.apache.org/jira/browse/AMQ-4212> or am I doing > something > > wrong here? > > > > Chris > > > > > > > > -- > > View this message in context: > > > http://activemq.2283324.n4.nabble.com/Offline-durable-subscriptions-lost-when-rebuilding-kahadb-index-tp4701701.html > > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
