[AMQ-4573] AMQ not starting when using default heart beat

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Cannot Reproduce
• Affects Version/s: 5.8.0
• Component/s: Message Store, STOMP, Transport
• Labels: heartbeat inactivity index kahadb stomp

Environment

5.8.0 on CentOS 5.8 32-bit

• Assignee: Unassigned
• Reporter: Karen Morrissey
• Created: 04/Jun/13 18:03
• Updated: 02/Jul/13 23:30
• Resolved: 02/Jul/13 23:30

Description

AMQ is not starting successfully when I enable a default heart beat for STOMP using

<transportConnector name="stomp_local" uri="stomp://0.0.0.0:3037?transport.defaultHeartBeat=300000,0"/>

Looking at the log I get repeated messages like the following:

2013-06-04 16:46:04,256 | WARN  | Failed to browse Topic: decoded_wwas | org.apache.activemq.broker.region.Topic | ActiveMQ Broker[10.0.3.32] Scheduler
java.io.EOFException: Chunk stream does not exist, page: 58 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:2757)
        at org.apache.activemq.store.kahadb.MessageDatabase$MessageOrderIndex.iterator(MessageDatabase.java:2739)
        at org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore$3.execute(KahaDBStore.java:526)
        at org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
        at org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore.recover(KahaDBStore.java:522)
        at org.apache.activemq.store.ProxyTopicMessageStore.recover(ProxyTopicMessageStore.java:62)
        at org.apache.activemq.broker.region.Topic.doBrowse(Topic.java:578)
        at org.apache.activemq.broker.region.Topic.access$100(Topic.java:65)
        at org.apache.activemq.broker.region.Topic$6.run(Topic.java:703)
        at org.apache.activemq.thread.SchedulerTimerTask.run(SchedulerTimerTask.java:33)
        at java.util.TimerThread.mainLoop(Timer.java:534)
        at java.util.TimerThread.run(Timer.java:484)

I'm listing this as major, because not setting a default heart beat is not an acceptable workaround for us.

Issue Links

• is related to: AMQ-3982 Overlapping PList iterators can read wrong data or throw exceptions about chunk streams not existing.
• is related to: AMQ-4118 Index page overflow (when a value does not fit in a page) can lead to duplicate calls to free
• is related to: AMQ-3906 repeated error message regarding chunk stream logged
• is related to: AMQ-4259 ClassCastException on Durable topic