You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by khandelwalanuj <kh...@gmail.com> on 2014/12/16 08:10:06 UTC
LevelDB: Invalid log position WARN after destroying durable
subscriber
Hi,
Using ActiveMQ 5.10.
We are getting below warning messages after durable subscription gets
destroyed because it's "offlineDurableSubscriberTimeout" expired.
*From the logs: *
20141215 23:28:42.279 EST (ActiveMQ Durable Subscriber Cleanup Timer)
org.apache.activemq.broker.region.TopicRegion#doCleanup 92 INFO] -
*Destroying durable subscriber due to inactivity:*
DurableTopicSubscription-jelineCompletionMessageListenerClient-GPL-QA-cmuser:JelineCompletion,
id=ID:geneva14.dr.com-52563-1418475439565-5:1:1:1, active=false,
destinations=1, total=0, pending=0, dispatched=0, inflight=0,
prefetchExtension=0
[20141215 23:28:42.281 EST (Thread-2)
org.apache.activemq.leveldb.util.Log$class*#warn 75 WARN] - Invalid log
position: 14 *
[20141215 23:28:42.283 EST (ActiveMQ Durable Subscriber Cleanup Timer)
org.apache.activemq.broker.region.TopicRegion#doCleanup 92 INFO] -
Destroying durable subscriber due to inactivity:
DurableTopicSubscription-geneva-sync-munshi-listener-QA-cmuser:munshi.geneva.business.listener.ISFMessageListener,
id=ID:geneva14.dr.com-52563-1418475439565-1:1:1:1, active=false,
destinations=1, total=0, pending=0, dispatched=0, inflight=0,
prefetchExtension=0
[20141215 23:28:42.284 EST (Thread-2)
org.apache.activemq.leveldb.util.Log$class#warn 75 WARN] - Invalid log
position: 0
[20141215 23:28:42.285 EST (ActiveMQ Durable Subscriber Cleanup Timer)
org.apache.activemq.broker.region.TopicRegion#doCleanup 92 INFO] -
Destroying durable subscriber due to inactivity:
DurableTopicSubscription-post-tdp-bundle-listener-QA-cmuser:munshi.geneva.gear.sync.listener.PostTdpMessageListener,
id=ID:geneva14.dr.com-52563-1418475439565-13:1:1:1, active=false,
destinations=1, total=73, pending=0, dispatched=73, inflight=0,
prefetchExtension=0
[20141215 23:28:42.285 EST (Thread-2)
org.apache.activemq.leveldb.util.Log$class#warn 75 WARN] - Invalid log
position: 73
Thanks,
Anuj
--
View this message in context: http://activemq.2283324.n4.nabble.com/LevelDB-Invalid-log-position-WARN-after-destroying-durable-subscriber-tp4688904.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: LevelDB: Invalid log position WARN after destroying durable subscriber
Posted by Kevin Burton <bu...@spinn3r.com>.
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.anuj90@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>
Re: LevelDB: Invalid log position WARN after destroying durable
subscriber
Posted by khandelwalanuj <kh...@gmail.com>.
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.
Re: LevelDB: Invalid log position WARN after destroying durable subscriber
Posted by Kevin Burton <bu...@spinn3r.com>.
I’ve started another thread for this. IE the Invalid log position thing.
I suspect it’s not a WARN but an ERROR.
Kevin
On Mon, Dec 15, 2014 at 11:10 PM, khandelwalanuj <
khandelwal.anuj90@gmail.com> wrote:
>
> Hi,
>
> Using ActiveMQ 5.10.
> We are getting below warning messages after durable subscription gets
> destroyed because it's "offlineDurableSubscriberTimeout" expired.
>
> *From the logs: *
>
> 20141215 23:28:42.279 EST (ActiveMQ Durable Subscriber Cleanup Timer)
> org.apache.activemq.broker.region.TopicRegion#doCleanup 92 INFO] -
> *Destroying durable subscriber due to inactivity:*
>
> DurableTopicSubscription-jelineCompletionMessageListenerClient-GPL-QA-cmuser:JelineCompletion,
> id=ID:geneva14.dr.com-52563-1418475439565-5:1:1:1, active=false,
> destinations=1, total=0, pending=0, dispatched=0, inflight=0,
> prefetchExtension=0
> [20141215 23:28:42.281 EST (Thread-2)
> org.apache.activemq.leveldb.util.Log$class*#warn 75 WARN] - Invalid log
> position: 14 *
>
> [20141215 23:28:42.283 EST (ActiveMQ Durable Subscriber Cleanup Timer)
> org.apache.activemq.broker.region.TopicRegion#doCleanup 92 INFO] -
> Destroying durable subscriber due to inactivity:
>
> DurableTopicSubscription-geneva-sync-munshi-listener-QA-cmuser:munshi.geneva.business.listener.ISFMessageListener,
> id=ID:geneva14.dr.com-52563-1418475439565-1:1:1:1, active=false,
> destinations=1, total=0, pending=0, dispatched=0, inflight=0,
> prefetchExtension=0
> [20141215 23:28:42.284 EST (Thread-2)
> org.apache.activemq.leveldb.util.Log$class#warn 75 WARN] - Invalid log
> position: 0
>
> [20141215 23:28:42.285 EST (ActiveMQ Durable Subscriber Cleanup Timer)
> org.apache.activemq.broker.region.TopicRegion#doCleanup 92 INFO] -
> Destroying durable subscriber due to inactivity:
>
> DurableTopicSubscription-post-tdp-bundle-listener-QA-cmuser:munshi.geneva.gear.sync.listener.PostTdpMessageListener,
> id=ID:geneva14.dr.com-52563-1418475439565-13:1:1:1, active=false,
> destinations=1, total=73, pending=0, dispatched=73, inflight=0,
> prefetchExtension=0
> [20141215 23:28:42.285 EST (Thread-2)
> org.apache.activemq.leveldb.util.Log$class#warn 75 WARN] - Invalid log
> position: 73
>
>
> Thanks,
> Anuj
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/LevelDB-Invalid-log-position-WARN-after-destroying-durable-subscriber-tp4688904.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>