It's hard to say an exact time frame. Finished new features would be
the driving force behind a 5.15.0 release as bug fixes are already
backported but right now there hasn't been much done to justify a
5.15.0 release. Most work has been focused on Artemis but I would say
that mid year sounds abou
Thanks christopher for the explanation. This makes sense. What are the
timelines for ActiveMQ v5.15.0 release - mid year? I am asking because I
plan to upgrade to 5.14.3 and if this issue will be handled well in 5.15.0 i
would love to upgrade directly to 5.15.0.
Thanks,
Abhi
--
View this mess
Yes if you have a ton of data on a durable subscription and delete the
durable it tends to write a large temp file because of the kahadb
index. Even though the temp file should be deleted automatically
after deletion this is certainly not ideal.
Right now there isn't really a good way to discard
Hi,
Yes these log messages appeared at the startup only. I had faced an issue
where activemq dumped 7gb file - tx-14693130-1483907222896.tmp in one of
the mkahadb directories when i tried to destroy a durable topic consumer
which was inactive for quite some time and had hit the memory threshold o
Did this happen while replaying the journal? This message means that
an acknowledgement was processed in the journal that doesn't have a
matching message. This log message would typically print out if you
were replaying the journal from the beginning to rebuild the index
because it's possible tha
