Anuj Khandelwal created AMQ-5375:
------------------------------------

             Summary: java.io.EOFException: Chunk stream does not exist at page 
after broker start
                 Key: AMQ-5375
                 URL: https://issues.apache.org/jira/browse/AMQ-5375
             Project: ActiveMQ
          Issue Type: Bug
          Components: Message Store
    Affects Versions: 5.10.0
            Reporter: Anuj Khandelwal


Hi,

I am continuously seeing this warning in broker logs. This issues does not 
happen immediately when broker starts, it happens after some time and it 
continuously happens after that.

I can see that even after this issue happens, the communication on that 
topic/queues work well. I can send and receive message from that destination.
Can someone tell me what is causing this kahadb corruption? 
I have seen that this is fixed in old version but thn how come it is happening 
in 5.10? 


Error details: 

org.apache.activemq.broker.region.Topic#doBrowse 635 WARN] - Failed to browse 
Topic: 
health.pongerTopic 
java.io.EOFException: Chunk stream does not exist, page: 132 is marked free
        at 
org.apache.activemq.store.kahadb.disk.page.Transaction$2.readPage(Transaction.java:470)
        at 
org.apache.activemq.store.kahadb.disk.page.Transaction$2.<init>(Transaction.java:447)
        at 
org.apache.activemq.store.kahadb.disk.page.Transaction.openInputStream(Transaction.java:444)
        at 
org.apache.activemq.store.kahadb.disk.page.Transaction.load(Transaction.java:420)
        at 
org.apache.activemq.store.kahadb.disk.page.Transaction.load(Transaction.java:377)
        at 
org.apache.activemq.store.kahadb.disk.index.BTreeIndex.loadNode(BTreeIndex.java:262)
        at 
org.apache.activemq.store.kahadb.disk.index.BTreeIndex.getRoot(BTreeIndex.java:174)
        at 
org.apache.activemq.store.kahadb.disk.index.BTreeIndex.iterator(BTreeIndex.java:232)
        at 
org.apache.activemq.store.kahadb.MessageDatabase$MessageOrderIndex$MessageOrderIterator.<init>(MessageDatabase.java:2990)
        at 
org.apache.activemq.store.kahadb.MessageDatabase$MessageOrderIndex.iterator(MessageDatabase.java:2966)
        at 
org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore$3.execute(KahaDBStore.java:543)
        at 
org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
        at 
org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore.recover(KahaDBStore.java:537)
        at 
org.apache.activemq.store.ProxyTopicMessageStore.recover(ProxyTopicMessageStore.java:62)
        at 
org.apache.activemq.store.ProxyTopicMessageStore.recover(ProxyTopicMessageStore.java:62)
        at org.apache.activemq.broker.region.Topic.doBrowse(Topic.java:594)
        at org.apache.activemq.broker.region.Topic.access$100(Topic.java:65)
        at org.apache.activemq.broker.region.Topic$6.run(Topic.java:733)
        at 
org.apache.activemq.thread.SchedulerTimerTask.run(SchedulerTimerTask.java:33)
        at java.util.TimerThread.mainLoop(Timer.java:555)
        at java.util.TimerThread.run(Timer.java:505)


Thanks,
Anuj



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to