[
https://issues.apache.org/jira/browse/AMQ-4573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677578#comment-13677578
]
Karen Morrissey commented on AMQ-4573:
--------------------------------------
I thought it was odd, too, that there would be a relationship between the
heartbeat and the message store. What I need to do, but I won't be able to get
to right away, is to turn on the heartbeat and restart AMQ to capture in the
log why AMQ is not coming up successfully. That failure to come up is what this
ticket is about, not the message store error I noted.
> AMQ not starting when using default heart beat
> ----------------------------------------------
>
> Key: AMQ-4573
> URL: https://issues.apache.org/jira/browse/AMQ-4573
> Project: ActiveMQ
> Issue Type: Bug
> Components: Message Store, stomp, Transport
> Affects Versions: 5.8.0
> Environment: 5.8.0 on CentOS 5.8 32-bit
> Reporter: Karen Morrissey
> Labels: heartbeat, inactivity, index, kahadb, stomp
> Attachments: activemq.log, activemq.xml
>
>
> AMQ is not starting successfully when I enable a default heart beat for STOMP
> using
> {code:xml}
> <transportConnector name="stomp_local"
> uri="stomp://0.0.0.0:3037?transport.defaultHeartBeat=300000,0"/>
> {code}
> Looking at the log I get repeated messages like the following:
> {code}
> 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)
> {code}
> I'm listing this as major, because not setting a default heart beat is not an
> acceptable workaround for us.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
