Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of james.mk.green@gmail.com
 designates 209.85.160.43 as permitted sender)
MIME-Version: 1.0
Date: Thu, 8 Nov 2012 10:01:40 +0000
Message-ID: 
 <CAMH6+ayQJKOZgVyHhMi-Ge33L=TognVVv0MBPtyXysT+O42zzQ@mail.gmail.com>
Subject: Memory usage with large messages
From: James Green <james.mk.green@gmail.com>
To: users <users@activemq.apache.org>
Content-Type: multipart/alternative; boundary=e89a8ff1c12ee98f2c04cdf8eb26

--e89a8ff1c12ee98f2c04cdf8eb26
Content-Type: text/plain; charset=ISO-8859-1

Hi,

We are narrowing down the chaos that we're encounted in recent weeks with
brokers hanging. The trigger point appears to be a large (10M) message
produced by a Stomp client on a hub topic then read by three spoke Stomp
clients. The Stomp transports on the spokes appear to start dieing after
this message is produced.

Between the hub and spokes is a slow ADSL upload link. The hub talks to the
spokes using the ssl:// scheme.

Do the network connectors between hub and spoke read messages sequentially
or in parallel? Also, is the memory for the entire message allocated the
beginning or does it expand as bytes are read off the wire?

I also wonder if the content of the messages is shared across "interested"
components or are duplicates maintained by each? I.e. transport connector
for openwire + kahadb plus topic cursor + stomp transport?

Trying to understand the behaviour here!

Thanks,

James

--e89a8ff1c12ee98f2c04cdf8eb26--