activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roelof Naude (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-2962) Hanging at startup
Date Fri, 15 Oct 2010 14:10:40 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62613#action_62613
] 

Roelof Naude commented on AMQ-2962:
-----------------------------------

KahaDBStore::recover locks itself:

2010-10-15 16:02:33,580 DEBUG [org.apache.activemq.store.kahadb.KahaDBStore] recover - lock[java.util.concurrent.locks.ReentrantReadWriteLock@26e7c832[Write
locks = 0, Read locks = 0]]
2010-10-15 16:02:33,620 DEBUG [org.apache.activemq.broker.region.Queue] message expired: Message
ID:segfault-52137-1287150445562-2:6:1:1:1 dropped=false acked=false locked=false
2010-10-15 16:02:33,620 DEBUG [org.apache.activemq.broker.region.RegionBroker] Message expired
Message ID:segfault-52137-1287150445562-2:6:1:1:1 dropped=false acked=false locked=false
2010-10-15 16:02:33,624 DEBUG [org.apache.activemq.broker.region.AbstractRegion] localhost
adding destination: topic://ActiveMQ.Advisory.MessageDLQd.Topic.VirtualTopic.ALARM
2010-10-15 16:02:33,648 DEBUG [org.apache.activemq.broker.region.AbstractRegion] localhost
adding destination: topic://ActiveMQ.Advisory.Expired.Topic.VirtualTopic.ALARM
2010-10-15 16:02:33,664 DEBUG [org.apache.activemq.store.kahadb.MessageDatabase] process remove
- lock[java.util.concurrent.locks.ReentrantReadWriteLock@26e7c832[Write locks = 0, Read locks
= 1]]
java.lang.Exception: STACKTRACE
        at org.apache.activemq.store.kahadb.MessageDatabase.process(MessageDatabase.java:902)
        at org.apache.activemq.store.kahadb.MessageDatabase$13.visit(MessageDatabase.java:847)
        at org.apache.activemq.store.kahadb.data.KahaRemoveMessageCommand.visit(KahaRemoveMessageCommand.java:220)
        at org.apache.activemq.store.kahadb.MessageDatabase.process(MessageDatabase.java:839)
        at org.apache.activemq.store.kahadb.MessageDatabase.store(MessageDatabase.java:763)
        at org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore.removeMessage(KahaDBStore.java:378)
        at org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore.removeAsyncMessage(KahaDBStore.java:350)
        at org.apache.activemq.store.kahadb.KahaDBTransactionStore.removeAsyncMessage(KahaDBTransactionStore.java:457)
        at org.apache.activemq.store.kahadb.KahaDBTransactionStore$1.removeAsyncMessage(KahaDBTransactionStore.java:171)
        at org.apache.activemq.broker.region.Queue.acknowledge(Queue.java:803)
        at org.apache.activemq.broker.region.Queue.removeMessage(Queue.java:1534)
        at org.apache.activemq.broker.region.Queue.removeMessage(Queue.java:1526)
        at org.apache.activemq.broker.region.Queue.messageExpired(Queue.java:1591)
        at org.apache.activemq.broker.region.Queue.messageExpired(Queue.java:1581)
        at org.apache.activemq.broker.region.Queue$5.recoverMessage(Queue.java:292)
        at org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore$4.execute(KahaDBStore.java:479)
        at org.apache.kahadb.page.Transaction.execute(Transaction.java:728)
        at org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore.recover(KahaDBStore.java:471)


> Hanging at startup
> ------------------
>
>                 Key: AMQ-2962
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2962
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Message Store
>    Affects Versions: 5.4.1
>         Environment: Fedora Core 12
>            Reporter: Roelof Naude
>            Priority: Minor
>         Attachments: amq.ra.threads.txt, debug_traces_hanging.log, debug_traces_startup.log,
thread_dump_during_hang.txt
>
>
> Noticed today the activemq was hanging during startup. Investigation revealed that it
is tied to expiration of messages at startup. The only way to recover from this was to kill
-9 the VM and delete the kahadb message store.
> Further testing was done whereby message expiry time was set to longer period. AMQ started
up just fine. Another test was performed whereby:
> 1. subscribe for messages
> 2. send a few messages
> 3. disconnect consumer
> 4. send more messages (1 or 2 will do)
> 5. shutdown AMQ
> 6. wait for a time period exceeded the expiration time of the messages
> 7. start AMQ. at this time it should be hanging
> Logs and thread dumps attached.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message