activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Newman (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-2009) Problem with message dispatch after a while
Date Wed, 31 Mar 2010 16:05:08 GMT

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

John Newman commented on AMQ-2009:
----------------------------------

Is anyone using activemq in a very high volume situation and NOT running into this after a
couple days?  It seems like there should be a great amount of 'outrage' over this one, as
it is quite disruptive.   Wouldn't this be affecting just about everyone?  

We are using activemq 5.2 in production.  3 sites have lower volume and we don't really have
any problems.  One site has high volume, and after 2 or 3 days at most, it will just fall
asleep.  No errors, no out of memory or anything, logs remain totally healthy.  The messages
continue to make it into the activemq DB without problems, it grows and grows, but yet messages
just stop going from activemq to the subscriber.

because this is happening so regularly, the root problem isn't even understood, a fix is a
long way away, and we can't "just restart" the broker in production without going through
a bunch of hoops, we've deemed it not fit for production and now have to figure out a different
queuing solution.  =(

> Problem with message dispatch after a while
> -------------------------------------------
>
>                 Key: AMQ-2009
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2009
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.1.0, 5.2.0
>            Reporter: Rajani Chennamaneni
>            Assignee: Rob Davies
>             Fix For: 5.4.0
>
>         Attachments: AMQ-2009Testcase2.zip, consumertest.zip, DispatchMultipleConsumersTest.java,
JConsole-screenshot.jpg, testcase.zip
>
>
> Messages are not getting dispatched after a while (although it accepts new incoming messages)
until restart of the broker. This problem is described in several posts.
> http://www.nabble.com/Pending-Messages-are-shown-in-ActiveMQ-td20241332.html
> http://www.nabble.com/Consumer-Listener-stop-receving-message-until-ActiveMQ-restart-td20355247.html
> http://www.nabble.com/Stuck-messages---Dispatch-issues-td20467949.html
> There was also an issue opened in Spring project for this thinking it was Spring problem.
> http://jira.springframework.org/browse/SPR-5110
> I am not able to reproduce with Junit test case having BrokerService started with in
the test case. I guess I am not hitting the right stress conditions this way. But when I run
the test case against an externally running ActiveMQ instance backed with oracle database
persistence, it is reproducible most of the times. This is not a every time failure situation,
it takes more time once than the other.
> I was able to hit this situation of stuck messages on queue using following scenario
most of the times:
> 1) Start 2 concurrent consumers for the queue using Spring's DefaultMessageListenerContainer
using cacheLevelName as CACHE_CONSUMER
> 2) Send messages using JMETER 2.3.2 to the queue on ActiveMQ stand alone broker instance
with 50 threads looping 20 times.
> 3) After a while, you will notice that Spring logs that no messages are being received
but the messages are shown jconsole of ActiveMQ and the database backing it for persistence.
> But in 5.2 RC3, the problem is that it dispatches duplicate messages and does not remove
them from broker's database after acknowledge properly.
> Attached test case might help to reproduce when run against externally running stand
alone ActiveMQ broker. Another way to see the problem is that try to load test using JMETER
by sending messages to a queue with a camel route that moves messages from this queue to another
and you will notice that it stops moving after while or copied duplicates in case of 5.2 RC3.
> Sorry about such a huge description but it is a real problem! A different team at our
company are having this issue in production with 5.1. They are using it as an embedded broker
with derby for persistence.

-- 
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