activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "SebastianR." <Sebastian.Rie...@de-gmbh.com>
Subject Re: Why don't Commit() and Receive() throw exceptions ? (NMS)
Date Thu, 21 Aug 2008 11:34:41 GMT

I found out that what i called a local store is in ActiveMQ called
prefetching. This prefetching is controlled via the variable prefetchSize
(which in NMS is set in the session.cs to a fixed value of 1000). Do I have
influence on this value in some way ? It would even better if, there would 
be a possibilty to disable the whole prefetching process. 
I searched the forum already, and found the that method sendPullCommand() in
the ActiveMQMessageConsumer class together with a prefetchSize of zero
achieves this. However this method doesn't exist in NMS. 

The reason I want to disable prefetching is the following:
As stated in the first post the Commit() method doesn't throw an exception
if there is a connection failure. But still messages are received and
processed correctly, because they are fetched from the local cache. This
leads to multiple message processing, because the processed messages aren't
acknowledged and so the broker dispatches them again, if the connection is
re-established.

How can I avoid this "multiple message processing", if I can't disable
prefetching ?

Regards, Sebastian




-- 
View this message in context: http://www.nabble.com/Why-don%27t-Commit%28%29-and-Receive%28%29-throw-exceptions---%28NMS%29-tp19048072p19086911.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message