activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From E White <>
Subject Re: Topic Memory Increases until broker dies
Date Tue, 04 May 2010 14:43:58 GMT

This must be a very difficult problem.  
Nobody here has any ideas they would like to share.
The people at SpringSource, whom we pay for support, can't figure it out.

Are we implementing this incorrectly?
Is it folly to use a topic to send updates to a swing client?

One of our developers locks up his topic easily by pausing his client while
running in his IDE, turning his client into a slow consumer.  It blocks the
whole broker. No other client can receive updates.

ActiveMQ is such a pleasure to get working, and such pain in the ass to keep

E White wrote:
> We have a java swing client that gets its data updates by subscribing to
> an ActiveMQ topic.  All clients (about a hundred at any given time)
> subscribe to the same topic.  Subscribers vary and are not durable, but
> the messages are persistent.
> I have seen the "inflight count" slowly, but steadily increase and then
> the "memory percent used" value spike, leaving the broker deadlocked and
> no longer processing messages, but not failing.  The whole scenario takes
> about a week.  And this makes our client application look like it is hung
> after it occurs.
> How do I keep messages from getting orphaned when a user closes their
> client?  I think that is where most of my "inflight" number is coming
> from.  Users close the client right as it has received a message but
> before it can send the ack. 
> How do I make "inflight" messages expire?  I've played around with setting
> "timetolive" in my test environment, but it does not seem to affect
> messages that are stuck "inflight".
> We are using ActiveMQ 5.3.0.

View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message