[
https://issues.apache.org/activemq/browse/AMQ-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62577#action_62577
]
Roelof Naude commented on AMQ-2962:
-----------------------------------
have tried the latest sun jdk:
java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)
the "hang" is not happening after changing to the AMQ resource adapter as
mentioned the the previous comment. BUT: the broker does not start when
expiring messages during startup. The following can be seen in the logs:
2010-10-14 15:23:55,531 INFO
[org.apache.activemq.store.kahadb.MessageDatabase] KahaDB is version 2
2010-10-14 15:23:55,573 INFO
[org.apache.activemq.store.kahadb.MessageDatabase] Recovering from the journal
...
2010-10-14 15:23:55,573 INFO
[org.apache.activemq.store.kahadb.MessageDatabase] Recovery replayed 1
operations from the journal in 0.019 seconds.
2010-10-14 15:23:55,592 INFO [org.apache.activemq.broker.BrokerService]
ActiveMQ 5.4.1 JMS Message Broker (localhost) is starting
2010-10-14 15:23:55,592 INFO [org.apache.activemq.broker.BrokerService] For
help or more information please see: http://activemq.apache.org/
2010-10-14 15:23:55,754 DEBUG
[org.apache.activemq.broker.region.AbstractRegion] localhost adding
destination: queue://Consumer.superuser.VirtualTopic.ALARM
2010-10-14 15:23:55,806 DEBUG [org.apache.activemq.broker.region.Queue] message
expired: Message ID:segfault-48347-1287061987558-2:4:1:1:1 dropped=false
acked=false locked=false
2010-10-14 15:23:55,806 DEBUG [org.apache.activemq.broker.region.RegionBroker]
Message expired Message ID:segfault-48347-1287061987558-2:4:1:1:1 dropped=false
acked=false locked=false
2010-10-14 15:23:55,809 DEBUG
[org.apache.activemq.broker.region.AbstractRegion] localhost adding
destination: topic://ActiveMQ.Advisory.MessageDLQd.Topic.VirtualTopic.ALARM
2010-10-14 15:23:55,835 DEBUG
[org.apache.activemq.broker.region.AbstractRegion] localhost adding
destination: topic://ActiveMQ.Advisory.Expired.Topic.VirtualTopic.ALARM
note the "message expired:"
thereafter the broker never started properly. every component trying to
establish a connection to the broker results in:
2010-10-14 15:24:12,614 DEBUG [org.apache.activemq.ra.ActiveMQEndpointWorker]
Failed to connect: Could not create Transport. Reason:
javax.management.InstanceAlreadyExistsException:
org.apache.activemq:BrokerName=localhost,Type=Broker already registered.
javax.jms.JMSException: Could not create Transport. Reason:
javax.management.InstanceAlreadyExistsException:
org.apache.activemq:BrokerName=localhost,Type=Broker already registered.
at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:35)
at
org.apache.activemq.ActiveMQConnectionFactory.createTransport(ActiveMQConnectionFactory.java:245)
at
org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:258)
at
org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:185)
at
org.apache.activemq.ra.ActiveMQResourceAdapter.makeConnection(ActiveMQResourceAdapter.java:133)
at
org.apache.activemq.ra.ActiveMQEndpointWorker$1.run(ActiveMQEndpointWorker.java:106)
at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
at
org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:756)
at java.lang.Thread.run(Thread.java:619)
the broker is indeed already registered with the mbean server, but it is not
really functioning.
anything else that i can try from my side?
> 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: 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.
