Bug 485696 - Messages are not acknowledged
Summary: Messages are not acknowledged
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-java
Version: 1.1
Hardware: All
OS: Linux
high
medium
Target Milestone: 1.1.1
: ---
Assignee: Rafael H. Schloming
QA Contact: Frantisek Reznicek
URL:
Whiteboard: IG Index
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-16 13:40 UTC by Arnaud Simon
Modified: 2015-11-16 00:06 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-06 08:35:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Arnaud Simon 2009-02-16 13:40:25 UTC
Description of problem:
When maxprefetch is greater than 0 then messages are not immediately acknowledged.  

see: https://issues.apache.org/jira/browse/QPID-1665

Comment 1 Gordon Sim 2009-02-17 12:01:44 UTC
Rafi, I believe the issue was resolved in qpid svn. Can you review the change and mark this modified when satisfied? Also is this something we need to consider respinning the 1.1.1 java package for?

Comment 4 Frantisek Reznicek 2011-09-06 08:34:55 UTC
Message acknowledgement works as expected, tested on RHEL 5.7 / 6.1 i[36]86 / x86_64 on packages:
python-qpid-0.10-1.el5.noarch
python-qpid-qmf-0.10-10.el5.i386
qpid-cpp-client-0.10-8.el5.i386
qpid-cpp-client-devel-0.10-8.el5.i386
qpid-cpp-client-devel-docs-0.10-8.el5.i386
qpid-cpp-client-ssl-0.10-8.el5.i386
qpid-cpp-server-0.10-8.el5.i386
qpid-cpp-server-cluster-0.10-8.el5.i386
qpid-cpp-server-devel-0.10-8.el5.i386
qpid-cpp-server-ssl-0.10-8.el5.i386
qpid-cpp-server-store-0.10-8.el5.i386
qpid-cpp-server-xml-0.10-8.el5.i386
qpid-java-client-0.10-6.el5.noarch
qpid-java-common-0.10-6.el5.noarch
qpid-java-example-0.10-6.el5.noarch
qpid-qmf-0.10-10.el5.i386
qpid-qmf-devel-0.10-10.el5.i386
qpid-tools-0.10-6.el5.noarch
rh-qpid-cpp-tests-0.10-8.el5.i386


-> VERIFIED


Note You need to log in before you can comment on or make changes to this bug.