Bug 1223795

Summary:	[MRG 3.1] linearstore raising JERR_LFCR_SEQNUMNOTFOUND after sending many DTX transactions
Product:	Red Hat Enterprise MRG	Reporter:	Pavel Moravec <pmoravec>
Component:	qpid-cpp	Assignee:	messaging-bugs <messaging-bugs>
Status:	CLOSED UPSTREAM	QA Contact:	Messaging QE <messaging-qe-bugs>
Severity:	high	Docs Contact:
Priority:	high
Version:	Development	CC:	jross, messaging-bugs, messaging-qe-bugs
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1223789	Environment:
Last Closed:	2025-02-10 03:47:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1223789, 1224300
Bug Blocks:

Description Pavel Moravec 2015-05-21 12:59:42 UTC

+++ This bug was initially created as a clone of Bug #1223789 +++

Description of problem:
Please backport QPID-6551 to 3.1.*.


Version-Release number of selected component (if applicable):
qpid-cpp-server-linearstore-0.30-8


How reproducible:
100%


Steps to Reproduce:
qpidd --efp-file-size=32 --log-to-file=/tmp/qpidd.log &
# --efp-file-size just for faster reproducer
qpid-txtest --dtx=yes --check=no --init=yes --tx-count=10 --total-messages=1000 --size=1
nohup qpid-txtest --dtx=yes --check=no --init=no --tx-count=200000 --size=1 &

now wait 1-2 hours until the nohup finishes


Actual results:
- Latest command fails
- qpidd logs exception:
jexception 0x0500 LinearFileController::find() threw JERR_LFCR_SEQNUMNOTFOUND: File sequence number not found (fileSeqNumber=0)


followed by various other journal exceptions.


Expected results:
- Latest command succeeds
- qpid-stat -q shows 2M enqueues and 2M dequeues in both queues tx-test-1 and tx-test-2 (just to confirm all transactions were executed)


Additional info:
Backport https://svn.apache.org/r1680861.

Comment 6 Mike McCune 2016-03-28 23:04:30 UTC

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 10 Red Hat Bugzilla 2025-02-10 03:47:38 UTC

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.