[
https://issues.apache.org/jira/browse/QPID-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992521#comment-12992521
]
Rajith Attapattu commented on QPID-3047:
----------------------------------------
In AMQSession_0_10.java, when using AUTO_ACK or DUPS_OK the acknowledgements
are batched to improve performance.
The ack are flushed based one of the following conditions (which ever happens
first).
1. When the ack timer fires. The ack-time is configure via
qpid.session.max_ack_delay
2. if un_acked_msg_count > max_prefetch/2.
For the test case you could force it to ack more frequently by having a smaller
prefetch.
(Please note as per the JMS spec AUTO_ACK should ack each message before it
serves up the next message. However by default our AUTO_ACK acts the same as
DUPS_OK.)
> The QueueDepthWithSelectorTest fails on 0-10 profiles
> -----------------------------------------------------
>
> Key: QPID-3047
> URL: https://issues.apache.org/jira/browse/QPID-3047
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.9
> Reporter: Andrew Kennedy
> Assignee: Andrew Kennedy
> Fix For: 0.9
>
>
> The QueueDepthWithSelector needs refactored to use QpidBrokerTestCase rather
> than being hardcoded simply the 0-8 iVM broker. Once this is done, the test
> fails on 0-10 profiles, as the session is not flushing acks correctly.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
