You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org> on 2009/03/16 17:03:50 UTC

[jira] Commented: (QPID-1692) Set the sync bit periodically to force the broker to send completions

    [ https://issues.apache.org/jira/browse/QPID-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682345#action_12682345 ] 

Rajith Attapattu commented on QPID-1692:
----------------------------------------

A fix has been commited to Qpid trunk at rev 748197.
The current solution does set the sync bit on message accepts every x milisecs defined by qpid.session.max_ack_delay (default 1000 msecs)
I agree that if you happen to publish durable messages on the same session (as the one you are consuming) then there would definitely be a performance issue.
(Note that a message accept is only sent if there are unacked messages)

This is not the ideal solution and it is reusing the timer that is used for sending message acks periodically.

> Set the sync bit periodically to force the broker to send completions
> ---------------------------------------------------------------------
>
>                 Key: QPID-1692
>                 URL: https://issues.apache.org/jira/browse/QPID-1692
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Client
>    Affects Versions: M4
>            Reporter: Rajith Attapattu
>            Assignee: Rajith Attapattu
>
> It would be good if the JMS client could periodically set the sync bit to force the broker to send completion of commands.
> This would prevent messages being duplicated unnessacerily during a failover and also as means to clear it's replay buffer.
> (Note that we also have -Dqpid.session.command_limit and -Dqpid.session.byte_limit that will send a sessionFlush whenever one of the limits are reached)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org