[
https://issues.apache.org/activemq/browse/AMQ-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43234#action_43234
]
Aaron Riekenberg commented on AMQ-1769:
---------------------------------------
After doing more testing, it appears this problem is triggered by use of the
setTimeToLive call on the MessageProducer setting the TTL to 10 seconds.
If I remove the setTimeToLive call, or do setTimeToLive(0), I can run the test
multiple times with no hangs. The Kaha Store message still comes out, but the
MDB keeps processing all the messages.
Also if I make the TTL time sufficiently large it does not hang. 100 seconds
works.
I suspect there is a problem here with removing timed out messages from the
queue.
I also tried deploying ActiveMQ 4.1.2 into my JBoss setup and it hung in the
same way with a 10 second TTL.
If anybody has suggestions of other things to try or wants more data please I'm
happy to try nearly anything.
> ActiveMQ broker in JBoss hangs when receiving > 25k messages
> ------------------------------------------------------------
>
> Key: AMQ-1769
> URL: https://issues.apache.org/activemq/browse/AMQ-1769
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.1.0
> Environment: RHEL 5 AMD64, Sun JDK 1.5.0_14, ActiveMQ 5.1.0 running
> in JBoss 4.2.2
> Reporter: Aaron Riekenberg
> Priority: Blocker
> Attachments: dump.txt, TerminalTrackConsumerMDB.java, Test.java
>
>
> Wrote a Java program to send 100000 TextMessage's to a JMS queue. An EJB3
> MDB in JBoss is listening to the queue and does a System.out.println when
> messages are received.
> After ~25k messages are processed by the MDB, the following message is
> printed to the screen, and messages stop being processed by the MDB:
> 16:57:33,391 INFO [KahaStore] Kaha Store using data directory
> activemq-data/jboss.activemq/tmp_storage
> It appears activemq is hanging just after the "KahaStore" message is output.
> No such problems have been observed using JBossMQ.
> Attached is the output of kill -3 <pid of jboss> showing stack traces of all
> threads just after the hang happens (dump.txt), the client program that sends
> lots of messages (Test.java), and the MDB (TerminalTrackConsumerMDB.java).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
