Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of greg.l.robillard@lmco.com
 designates 192.31.106.12 as permitted sender)
Date: Thu, 12 Aug 2010 09:59:51 -0600
From: "Robillard, Greg L" <greg.l.robillard@lmco.com>
Subject: ActiveMQ disconnects producer with large message throughput
To: "users@activemq.apache.org" <users@activemq.apache.org>
Message-id: <6A590AB4AFE3F5499A957AB58AB834BF138A470A0D@HDXMSPA.us.lmco.com>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_T7vqRw+a8bXGMMjCQl86sQ)"
Content-language: en-US
Thread-Topic: ActiveMQ disconnects producer with large message throughput
Thread-Index: Acs6N2TNRNUIxdE2TbKEX9KrJmmlYQ==
Accept-Language: en-US
acceptlanguage: en-US

--Boundary_(ID_T7vqRw+a8bXGMMjCQl86sQ)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Not certain where to begin.

apache-activemq-5.3.2
using non-persistent queues
using openwire jms connections

Problem described:

Normal operation has about 30 clients connected receiving between 300 and 500 messages per minute.  Problem occurs if a single client configures a large amount of data.  This can get a single client to receive up to 10,000 messages per minute.  The message size is small, generally at or under 1K.

Initially producerFlowControl was set to true, but this shut the producer down for everyone.  ProducerFlowControl is now set to false.

The client queue size continues to fill (NotificationQueueSizeExceeded).  This happens primarily on slower networks and client computers.  Faster networks and client computers can often handle this data rate.  What I currently do, is trap this situation, and log the client off since their client cannot keep up with the data rate.

The problem specifically is that sometimes, when a client is bringing in large amounts of data,  activemq sometimes simply runs out of memory and shuts the producer down and all of the clients.

Currently, the only way I have been able to recover from this is to restart activemq and the producer.

I am looking for what needs to be done to keep activemq from running out of memory if these large data rates happen when I am not using producerflowcontrol.   Additionally, how can I recover if this situation happens.

I have attempted to increase the prefetch size, to increase throughput, to no avail.  I was using vmQueueCursor, but am currently attempting fileQueueCursor.

Any suggestions or ideas would be of great help.

Greg

--Boundary_(ID_T7vqRw+a8bXGMMjCQl86sQ)--