Bug 1029440 - durable messages cannot be dequeued after being paged out
Summary: durable messages cannot be dequeued after being paged out
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: 3.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: 3.0
: ---
Assignee: Gordon Sim
QA Contact: Eric Sammons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-12 11:53 UTC by Gordon Sim
Modified: 2015-01-21 12:54 UTC (History)
3 users (show)

Fixed In Version: qpid-cpp-0.22-26
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-21 12:54:48 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Apache JIRA QPID-5315 0 None None None Never

Description Gordon Sim 2013-11-12 11:53:37 UTC
Description of problem:

The persistence id of durable messages is not included in the paging file, so durable messages paged back into memory lose that crucial information preventing successful dequeue.  

Version-Release number of selected component (if applicable):

Early Access

How reproducible:

100%

Steps to Reproduce:
1. create a durable paged queue
2. send 100,000 durable 1024 byte messages to it
3. consume all messages

Actual results:

Get an exception about the lack of persistence id

Expected results:

All messages are successfully consumed and queue is empty at the end of test
Additional info:

Comment 1 Gordon Sim 2013-11-12 11:55:00 UTC
Fixed upstream: https://svn.apache.org/r1540138

Comment 2 Valiantsina Hubeika 2014-01-31 14:13:01 UTC
checked & verified

qpid-cpp-server-0.22-33.el6
qpid-cpp-client-ssl-0.22-33.el6
qpid-cpp-server-ssl-0.22-33.el6
qpid-cpp-client-0.22-33.el6
qpid-cpp-client-devel-0.22-33.el6
qpid-cpp-server-devel-0.22-33.el6
qpid-cpp-server-xml-0.22-33.el6
qpid-cpp-server-store-0.22-33.el6
qpid-cpp-server-ha-0.22-33.el6


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