You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2007/12/14 11:31:42 UTC
[jira] Created: (QPID-707) DupsOk doesn't acknowledge enough
DupsOk doesn't acknowledge enough
---------------------------------
Key: QPID-707
URL: https://issues.apache.org/jira/browse/QPID-707
Project: Qpid
Issue Type: Bug
Components: Java Client
Affects Versions: M2, M2.1
Reporter: Martin Ritchie
Assignee: Martin Ritchie
Fix For: M2.1
There are a number of problems:
1) Client only acknowledges when prefetch fills in DupsOK mode i.e. every 5000 msgs.
2) When setting a single prefetch value the high and low are set to this value.
- Not a major problem but would be better to use the high and low.
3) As a result of 2 and an assumption that high != low prefetch an ack is only sent when there are more outstanding msgs to ack that high prefetch. Which can't occur as the broker will flow control the client before then.
4) When the consumer closes it doesn't make any attempt to ack the messages it has successfully processed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (QPID-707) DupsOk doesn't acknowledge enough
Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aidan Skinner resolved QPID-707.
--------------------------------
Resolution: Fixed
DupsOK is now equal to AutoAck
> DupsOk doesn't acknowledge enough
> ---------------------------------
>
> Key: QPID-707
> URL: https://issues.apache.org/jira/browse/QPID-707
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: M2, M2.1
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Fix For: M3
>
>
> There are a number of problems:
> 1) Client only acknowledges when prefetch fills in DupsOK mode i.e. every 5000 msgs.
> 2) When setting a single prefetch value the high and low are set to this value.
> - Not a major problem but would be better to use the high and low.
> 3) As a result of 2 and an assumption that high != low prefetch an ack is only sent when there are more outstanding msgs to ack that high prefetch. Which can't occur as the broker will flow control the client before then.
> 4) When the consumer closes it doesn't make any attempt to ack the messages it has successfully processed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-707) DupsOk doesn't acknowledge enough
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-707:
--------------------------------
Fix Version/s: (was: M2.1)
M3
> DupsOk doesn't acknowledge enough
> ---------------------------------
>
> Key: QPID-707
> URL: https://issues.apache.org/jira/browse/QPID-707
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: M2, M2.1
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Fix For: M3
>
>
> There are a number of problems:
> 1) Client only acknowledges when prefetch fills in DupsOK mode i.e. every 5000 msgs.
> 2) When setting a single prefetch value the high and low are set to this value.
> - Not a major problem but would be better to use the high and low.
> 3) As a result of 2 and an assumption that high != low prefetch an ack is only sent when there are more outstanding msgs to ack that high prefetch. Which can't occur as the broker will flow control the client before then.
> 4) When the consumer closes it doesn't make any attempt to ack the messages it has successfully processed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.