sync_ack option in AMQP 0-10 JMS client

[Jakub Scholz <ja...@scholz.cz>]

There used to be a connection URL parameter "sync_ack" which could have
been used to define whether acknowledgments should be sent synchronously or
asynchronously. Is this parameter still supported?

It seems to me that whatever value I give to it, it always syncs after
every acknowledgements. From digging through the code it seems to me that
it is reflected only when I use AUTO_ACKNOWLEDGE mode, but not when I
acknowledge the messages manually.

I also noticed that the "Using the Qpid JMS client (AMQP 0-10)" document on
the website (
https://qpid.apache.org/releases/qpid-0.32/programming/book/QpidJMS.html)
is not updated since 0.32 release. It is missing for the 6.0.x releases -
it looks like it disappeared with the independent Java releases. I guess
that is probably not intentional.

Thanks & Regards
Jakub

Re: sync_ack option in AMQP 0-10 JMS client

[Jakub Scholz <ja...@scholz.cz>]

I will raise a JIRA and have a look whether I can come up with some patch.
I think it would be useful to have this kind of control also over client
acknowledgments.

On Fri, May 13, 2016 at 2:07 PM, Robbie Gemmell <ro...@gmail.com>
wrote:

> Taking a peek, the option only ever affected auto-ack behaviour since
> it was added several years ago, letting you configure the 0-10
> consumers to sync after each message ack. It doesnt affect the sync
> behaviour for client-ack consumers, as Jakub notes.
>

Re: sync_ack option in AMQP 0-10 JMS client

[Robbie Gemmell <ro...@gmail.com>]

I've made some more changes to tidy it up a bit further, update the
release scripts, and pushed an update for the 6.0.2 release pages to
add the new book to the website and also correct some other issues
around links and docs referencing 6.0.3-SNAPSHOT as the version etc.

I merged the changes to the 6.0.x branch now since Robs feedback
suggests 6.0.3 needs a respin, and I've updated the website update
steps on the release process wiki page to account for version issue
and also the site contents moving to git.

On 13 May 2016 at 22:52, Robbie Gemmell <ro...@gmail.com> wrote:
> I've raised https://issues.apache.org/jira/browse/QPID-7265 and made a
> start on doing what I suggested with the existing 0-10 client docs.
>
> On 13 May 2016 at 13:07, Robbie Gemmell <ro...@gmail.com> wrote:
>> Taking a peek, the option only ever affected auto-ack behaviour since
>> it was added several years ago, letting you configure the 0-10
>> consumers to sync after each message ack. It doesnt affect the sync
>> behaviour for client-ack consumers, as Jakub notes.
>>
>> On the docs, the easiest (if ugly) thing to do for now would probably
>> be to just copy the 'programming' book into the java tree, drop all
>> the non-JMS bits, move the 'addresses' section to the end, and leave
>> it otherwise as-is, with the 0-10 and 0-8..0-91 books still seperate.
>> That would allow updating it if needed and avoid confusion of where it
>> is in the immediate term, and any larger changes/consolidation can
>> then be done later as desired/time allows.
>>
>> Robbie
>>
>> On 13 May 2016 at 12:32, Keith W <ke...@gmail.com> wrote:
>>> Jakub,
>>>
>>> The parameter is still supported.
>>>
>>> The Java section of the Programming in Apache Qpid docbook has rather
>>> been orphaned by code re-structurings,   It really ought to move into
>>> the Java components tree and ideally incorporated with the 0-8..0-91
>>> docbook.  Unfortunately this it not as easy at it ought to be as there
>>> are significant behavioural differences when the legacy client is used
>>> with 0-10 vs. the older protocols.  It is on my todo list, but keeps
>>> getting bumped.
>>>
>>> HTH
>>>
>>>
>>> On 12 May 2016 at 21:49, Jakub Scholz <ja...@scholz.cz> wrote:
>>>> There used to be a connection URL parameter "sync_ack" which could have
>>>> been used to define whether acknowledgments should be sent synchronously or
>>>> asynchronously. Is this parameter still supported?
>>>>
>>>> It seems to me that whatever value I give to it, it always syncs after
>>>> every acknowledgements. From digging through the code it seems to me that
>>>> it is reflected only when I use AUTO_ACKNOWLEDGE mode, but not when I
>>>> acknowledge the messages manually.
>>>>
>>>> I also noticed that the "Using the Qpid JMS client (AMQP 0-10)" document on
>>>> the website (
>>>> https://qpid.apache.org/releases/qpid-0.32/programming/book/QpidJMS.html)
>>>> is not updated since 0.32 release. It is missing for the 6.0.x releases -
>>>> it looks like it disappeared with the independent Java releases. I guess
>>>> that is probably not intentional.
>>>>
>>>> Thanks & Regards
>>>> Jakub
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>>> For additional commands, e-mail: users-help@qpid.apache.org
>>>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org

Re: sync_ack option in AMQP 0-10 JMS client

[Robbie Gemmell <ro...@gmail.com>]

I've raised https://issues.apache.org/jira/browse/QPID-7265 and made a
start on doing what I suggested with the existing 0-10 client docs.

On 13 May 2016 at 13:07, Robbie Gemmell <ro...@gmail.com> wrote:
> Taking a peek, the option only ever affected auto-ack behaviour since
> it was added several years ago, letting you configure the 0-10
> consumers to sync after each message ack. It doesnt affect the sync
> behaviour for client-ack consumers, as Jakub notes.
>
> On the docs, the easiest (if ugly) thing to do for now would probably
> be to just copy the 'programming' book into the java tree, drop all
> the non-JMS bits, move the 'addresses' section to the end, and leave
> it otherwise as-is, with the 0-10 and 0-8..0-91 books still seperate.
> That would allow updating it if needed and avoid confusion of where it
> is in the immediate term, and any larger changes/consolidation can
> then be done later as desired/time allows.
>
> Robbie
>
> On 13 May 2016 at 12:32, Keith W <ke...@gmail.com> wrote:
>> Jakub,
>>
>> The parameter is still supported.
>>
>> The Java section of the Programming in Apache Qpid docbook has rather
>> been orphaned by code re-structurings,   It really ought to move into
>> the Java components tree and ideally incorporated with the 0-8..0-91
>> docbook.  Unfortunately this it not as easy at it ought to be as there
>> are significant behavioural differences when the legacy client is used
>> with 0-10 vs. the older protocols.  It is on my todo list, but keeps
>> getting bumped.
>>
>> HTH
>>
>>
>> On 12 May 2016 at 21:49, Jakub Scholz <ja...@scholz.cz> wrote:
>>> There used to be a connection URL parameter "sync_ack" which could have
>>> been used to define whether acknowledgments should be sent synchronously or
>>> asynchronously. Is this parameter still supported?
>>>
>>> It seems to me that whatever value I give to it, it always syncs after
>>> every acknowledgements. From digging through the code it seems to me that
>>> it is reflected only when I use AUTO_ACKNOWLEDGE mode, but not when I
>>> acknowledge the messages manually.
>>>
>>> I also noticed that the "Using the Qpid JMS client (AMQP 0-10)" document on
>>> the website (
>>> https://qpid.apache.org/releases/qpid-0.32/programming/book/QpidJMS.html)
>>> is not updated since 0.32 release. It is missing for the 6.0.x releases -
>>> it looks like it disappeared with the independent Java releases. I guess
>>> that is probably not intentional.
>>>
>>> Thanks & Regards
>>> Jakub
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>> For additional commands, e-mail: users-help@qpid.apache.org
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org

Re: sync_ack option in AMQP 0-10 JMS client

[Robbie Gemmell <ro...@gmail.com>]

Taking a peek, the option only ever affected auto-ack behaviour since
it was added several years ago, letting you configure the 0-10
consumers to sync after each message ack. It doesnt affect the sync
behaviour for client-ack consumers, as Jakub notes.

On the docs, the easiest (if ugly) thing to do for now would probably
be to just copy the 'programming' book into the java tree, drop all
the non-JMS bits, move the 'addresses' section to the end, and leave
it otherwise as-is, with the 0-10 and 0-8..0-91 books still seperate.
That would allow updating it if needed and avoid confusion of where it
is in the immediate term, and any larger changes/consolidation can
then be done later as desired/time allows.

Robbie

On 13 May 2016 at 12:32, Keith W <ke...@gmail.com> wrote:
> Jakub,
>
> The parameter is still supported.
>
> The Java section of the Programming in Apache Qpid docbook has rather
> been orphaned by code re-structurings,   It really ought to move into
> the Java components tree and ideally incorporated with the 0-8..0-91
> docbook.  Unfortunately this it not as easy at it ought to be as there
> are significant behavioural differences when the legacy client is used
> with 0-10 vs. the older protocols.  It is on my todo list, but keeps
> getting bumped.
>
> HTH
>
>
> On 12 May 2016 at 21:49, Jakub Scholz <ja...@scholz.cz> wrote:
>> There used to be a connection URL parameter "sync_ack" which could have
>> been used to define whether acknowledgments should be sent synchronously or
>> asynchronously. Is this parameter still supported?
>>
>> It seems to me that whatever value I give to it, it always syncs after
>> every acknowledgements. From digging through the code it seems to me that
>> it is reflected only when I use AUTO_ACKNOWLEDGE mode, but not when I
>> acknowledge the messages manually.
>>
>> I also noticed that the "Using the Qpid JMS client (AMQP 0-10)" document on
>> the website (
>> https://qpid.apache.org/releases/qpid-0.32/programming/book/QpidJMS.html)
>> is not updated since 0.32 release. It is missing for the 6.0.x releases -
>> it looks like it disappeared with the independent Java releases. I guess
>> that is probably not intentional.
>>
>> Thanks & Regards
>> Jakub
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org

Re: sync_ack option in AMQP 0-10 JMS client

[Keith W <ke...@gmail.com>]

Jakub,

The parameter is still supported.

The Java section of the Programming in Apache Qpid docbook has rather
been orphaned by code re-structurings,   It really ought to move into
the Java components tree and ideally incorporated with the 0-8..0-91
docbook.  Unfortunately this it not as easy at it ought to be as there
are significant behavioural differences when the legacy client is used
with 0-10 vs. the older protocols.  It is on my todo list, but keeps
getting bumped.

HTH


On 12 May 2016 at 21:49, Jakub Scholz <ja...@scholz.cz> wrote:
> There used to be a connection URL parameter "sync_ack" which could have
> been used to define whether acknowledgments should be sent synchronously or
> asynchronously. Is this parameter still supported?
>
> It seems to me that whatever value I give to it, it always syncs after
> every acknowledgements. From digging through the code it seems to me that
> it is reflected only when I use AUTO_ACKNOWLEDGE mode, but not when I
> acknowledge the messages manually.
>
> I also noticed that the "Using the Qpid JMS client (AMQP 0-10)" document on
> the website (
> https://qpid.apache.org/releases/qpid-0.32/programming/book/QpidJMS.html)
> is not updated since 0.32 release. It is missing for the 6.0.x releases -
> it looks like it disappeared with the independent Java releases. I guess
> that is probably not intentional.
>
> Thanks & Regards
> Jakub

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org