Bug 623653 – resize and store_chk tools do not correctly analyze some transactional records

Bug 623653 - resize and store_chk tools do not correctly analyze some transactional records

Summary:	resize and store_chk tools do not correctly analyze some transactional records

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Enterprise MRG
Classification:	Red Hat
Component:	qpid-cpp (Show other bugs)
Sub Component:
Version:	Development
Hardware:	All Linux

Priority	high Severity high
Target Milestone:	1.3
Target Release:	---
Assigned To:	Kim van der Riet
QA Contact:	MRG Quality Engineering
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2010-08-12 08:50 EDT by Kim van der Riet
Modified:	2013-02-25 06:03 EST (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2013-02-25 06:03:09 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Kim van der Riet 2010-08-12 08:50:34 EDT

When using store_chk on a store in which records are both enqueued and dequeued under the same transaction (this occurs in the TPL), the dequeue operation is ignored, and the tool incorrectly reports that the enqueue records remain.

This is a logic error in the janal.py lib.

Comment 1 Kim van der Riet 2010-08-12 11:03:12 EDT

Fixed in r.4204

QE: This can be checked by running a transactional qpid-perftest, eg.

./qpid-perftest --summary --count 10 --qt 1 --nsubs 1 --npubs 1 --size 100 --tx 1 --durable 1

Then use store_chk to look at the TPL (in directory rhn/tpl), remembering to set the basename to "tpl", ie

./store_chk /path/to/rhm/tpl -b tpl

Before the fix, the TPL shows undequeued records. After the fix, the TPL is empty.

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