You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by Bruce Snyder <br...@gmail.com> on 2009/05/11 21:02:37 UTC
Re: [jira] Resolved: (AMQ-2087) Redelivery after rollback does not
seem to work well
On Wed, Jan 28, 2009 at 12:38 PM, Gary Tully (JIRA) <ji...@apache.org> wrote:
> There are a bunch of related open issues on this behavior, with the wire format change
> in 6.0 it will be possible to address this. A subscription remove command needs to
> indicate to the broker the last delivered ack that it has produced. An alternative is that
> the subscription trys to keep track of this information (which may be simpler).
To what changes are you referring regarding the wire format change in
ActiveMQ 6.0? I've not heard of anything related to this?
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
ActiveMQ in Action: http://bit.ly/2je6cQ
Blog: http://bruceblog.org/
Twitter: http://twitter.com/brucesnyder
Re: [jira] Resolved: (AMQ-2087) Redelivery after rollback does not
seem to work well
Posted by Bruce Snyder <br...@gmail.com>.
On Tue, May 12, 2009 at 3:10 AM, Gary Tully <ga...@gmail.com> wrote:
> The change to version 5 that is currently on trunk. The details are
> contained in https://issues.apache.org/activemq/browse/AMQ-2087
> RemoveInfo has an additional attribute that tracks the last delivered
> message so that the redelivery count can remain accurate after a
> repeat prefetch dispatch.
Ah, that change is labeled v5 of openwire so I thought that there were
more changes beyond that afoot.
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
ActiveMQ in Action: http://bit.ly/2je6cQ
Blog: http://bruceblog.org/
Twitter: http://twitter.com/brucesnyder
Re: [jira] Resolved: (AMQ-2087) Redelivery after rollback does not
seem to work well
Posted by Gary Tully <ga...@gmail.com>.
The change to version 5 that is currently on trunk. The details are
contained in https://issues.apache.org/activemq/browse/AMQ-2087
RemoveInfo has an additional attribute that tracks the last delivered
message so that the redelivery count can remain accurate after a
repeat prefetch dispatch.
2009/5/11 Bruce Snyder <br...@gmail.com>:
> On Wed, Jan 28, 2009 at 12:38 PM, Gary Tully (JIRA) <ji...@apache.org> wrote:
>
>> There are a bunch of related open issues on this behavior, with the wire format change
>> in 6.0 it will be possible to address this. A subscription remove command needs to
>> indicate to the broker the last delivered ack that it has produced. An alternative is that
>> the subscription trys to keep track of this information (which may be simpler).
>
> To what changes are you referring regarding the wire format change in
> ActiveMQ 6.0? I've not heard of anything related to this?
>
> Bruce
> --
> perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
>
> ActiveMQ in Action: http://bit.ly/2je6cQ
> Blog: http://bruceblog.org/
> Twitter: http://twitter.com/brucesnyder
>
--
http://blog.garytully.com
Open Source SOA
http://FUSESource.com