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 bruce.snyder@gmail.com
 designates 209.85.162.176 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=kYN/UKsG6lUoDa9jSgg/TzkgGKdqsWqAg+ICHX8s2IogfdJdUJwm4MgoQLO2AOGyBAAgWVIdks27lMgsxWgUFTfu9ZbEo1hvz/Ra4PGcEyFLGJ7pwhQHIcqUesI8S/nMYUHqhaWewNto5x8S2DXV8Osetc4J98/SosAx45Ix3AU=
Message-ID: <7b3355cb0805011409v5f17318bw2d39f0da163b6886@mail.gmail.com>
Date: Thu, 1 May 2008 15:09:06 -0600
From: "Bruce Snyder" <bruce.snyder@gmail.com>
To: users@activemq.apache.org
Subject: Re: Publisher can't publish after a certain number of messages are
 sent
In-Reply-To: <16995039.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <16995039.post@talk.nabble.com>

On Thu, May 1, 2008 at 2:16 PM, seven_ephors <ching.kong@aero.org> wrote:
>
>  I am using the TopicPublisher.java code in the 5.0.0\example\src directory,
>  with slight modifications.  It seem to work pretty well, but when I have
>  large number of messages, it always stop working after certain number of
>  messages are published.  For a BytesMessage with data size of 256X128, I can
>  only send up to 743 message.  After that, the publisher can't send any more
>  message to the broker.  In order to get it to work again, I need to ctrl-C
>  on the ActiveMQ DOS window, and restart the broker.  Since I need to publish
>  topic continuously, I need to find solution to the problem.
>
>  My questions are, 1, anyone have similar problem with a publisher?  2, What
>  am I doing wrong?  3, What solution is there?

Most typically this is an issue with the consumer side processing
being much slower than the broker side, so the messages back up on the
broker. One solution to such slow consumer situations is to use the
consumer prefetch prefetch policy. See the following for more info:

http://activemq.apache.org/what-is-the-prefetch-limit-for.html

Please read through that and see if it describes your situation and if
it does, give the prefetch policy a try.

Bruce
-- 
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'

Apache ActiveMQ - http://activemq.org/
Apache Camel - http://activemq.org/camel/
Apache ServiceMix - http://servicemix.org/
Apache Geronimo - http://geronimo.apache.org/

Blog: http://bruceblog.org/