activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "james strachan (JIRA)" <>
Subject [jira] Commented: (AMQ-674) Composite Destination persisted messages never get cleaned up, halt message producers
Date Tue, 04 Apr 2006 08:37:00 GMT
    [ ] 

james strachan commented on AMQ-674:


The issue isn't with Composite Destinations per se - they are pretty trivial things, just
a 1-many relationship of destinations. The issue is when you run out of RAM due to too many
messages stuck on some queue, things kinda lock up until messages get consumed.

So I definitely recommend you upgrade to 4.0-RC2...

which has all these issues fixed.

Note I'm a little confused when you talk about Index1.Foo and Index2.Foo and machines index1/index2.
Index1.Foo is a queue which will exist on the broker your producer talks to right? Are you
networking 2 brokers together in a store/forward network?

BTW one other benefit of 4.x is you can use JMX to view all the queues & their queue depths
to easily grok whats going on...

> Composite Destination persisted messages never get cleaned up, halt message producers
> -------------------------------------------------------------------------------------
>          Key: AMQ-674
>          URL:
>      Project: ActiveMQ
>         Type: Bug

>   Components: Broker, Message Store
>     Versions: 3.2.1
>     Reporter: Paul Smith
>     Priority: Blocker
>      Fix For: 4.0 RC1

> well, we've just got bit by something huge.  
> Previously we have been shipping messages from producer to consumer via a named Queue
'Index2.EntityIncrementalIndexer', where the machine index2 has a consumer called "EntityIncrementalIndexer"
using persisted messages.
> The design used Composite destinations so that the destination could be:
> "Index1.EntityIncrementalIndexer,Index2.EntityIncrementalIndexer" 
> and have the 2 hosts get sent the same message simply, and if one goes down, it'll catch
up later.  This gave us the ability to have a mirrored configuration, and go tertiary later
if we want simply by adding a new name in the composite destation.
> With a single name, this works great, been working fine for months.  Yesterday we activated
the _true_ composite destination, and both machines started getting their messages fine. 

> no problems so far, BUT, 12 hours later we have noticed that the broker has now stopped
accepting messages, and a look at the activemq_msgs table shows 33228 messages 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message