It was one of my recent replies. To be fair there isn’t much discussion on this.. but it’s happening more and more on our install and our AMQ is being VERY prone to data loss in production so I really need to track this down.
I’ve started a wiki page where I’m trying to take notes in public: https://github.com/spinn3r/apache-activemq-5.10.0/wiki/Apache-ActiveMQ-%22No-reader-available-for-position%22-bug I’m just starting to spend more time on this. Basically, AMQ works fine for a few weeks and then has catastrophic data loss, losing nearly all data. This is on LevelDB .. I don’t think KahaDB is impacted. I’m also trying to mitigate it by making it super easy to rebuild a queue with all our messages. This way if we lose everything it only takes 5 minutes to re-enqueue everything again. On Thu, Dec 18, 2014 at 11:09 PM, khandelwalanuj < khandelwal.anu...@gmail.com> wrote: > > Can you point to to that thread ? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/LevelDB-Invalid-log-position-WARN-after-destroying-durable-subscriber-tp4688904p4689114.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- Founder/CEO Spinn3r.com Location: *San Francisco, CA* blog: http://burtonator.wordpress.com … or check out my Google+ profile <https://plus.google.com/102718274791889610666/posts> <http://spinn3r.com>
