You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@servicemix.apache.org by samg <sa...@wellogic.com> on 2007/07/18 20:47:41 UTC

JMS reliability : AUTO_ACKNOWLEDGE vs. CLIENT_ACKNOWLEDGE

Hi folks,
in my ongoing effort to not lose messages I've made another change to
servicemix-jms : It seems to me that three of the four processors
(standard/multiplexing consumer/provider combinations) can be trivially
switched to CLIENT_ACKNOWLEDGE without any performance hit at all (they can
all do the receive() and acknowledge() in one synchronous flow), so I've
done so.  I'm not using the MultiplexingConsumerProcessor, and it is the one
complex case.
This Issue :
https://issues.apache.org/activemq/browse/SM-555
 requests that it be added as an option, but perhaps it makes sense in these
cases to just switch over to CLIENT_ACKNOWLEDGE?  Let me know what you
think.
-Sam
-- 
View this message in context: http://www.nabble.com/JMS-reliability-%3A-AUTO_ACKNOWLEDGE-vs.-CLIENT_ACKNOWLEDGE-tf4105152s12049.html#a11674691
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.

Re: JMS reliability : AUTO_ACKNOWLEDGE vs. CLIENT_ACKNOWLEDGE

Posted by Bruce Snyder <br...@gmail.com>.

On 7/18/07, samg <sa...@wellogic.com> wrote:
>
> Hi folks,
> in my ongoing effort to not lose messages I've made another change to
> servicemix-jms : It seems to me that three of the four processors
> (standard/multiplexing consumer/provider combinations) can be trivially
> switched to CLIENT_ACKNOWLEDGE without any performance hit at all (they can
> all do the receive() and acknowledge() in one synchronous flow), so I've
> done so.  I'm not using the MultiplexingConsumerProcessor, and it is the one
> complex case.
> This Issue :
> https://issues.apache.org/activemq/browse/SM-555
>  requests that it be added as an option, but perhaps it makes sense in these
> cases to just switch over to CLIENT_ACKNOWLEDGE?  Let me know what you
> think.

Thanks for pointing this out, Sam. This is actually fixed in the trunk
(3.2-SNAPSHOT) in the new JmsConsumerEndpoint class as a configurable
option via the setSessionAcknowledgeMode() method.

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

Apache Geronimo - http://geronimo.apache.org/
Apache ActiveMQ - http://activemq.org/
Apache ServiceMix - http://servicemix.org/
Castor - http://castor.org/