Bug 761023 - Message loss when broker is killed while txtest client is rotating messages in queues
Summary: Message loss when broker is killed while txtest client is rotating messages i...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: Development
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Kim van der Riet
QA Contact: Frantisek Reznicek
URL:
Whiteboard:
: 814734 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-07 15:32 UTC by Petr Matousek
Modified: 2015-09-10 07:31 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-10 07:31:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 814734 0 high CLOSED qpidd qpid-txtest transaction integrity problems 2021-02-22 00:41:40 UTC

Internal Links: 814734

Description Petr Matousek 2011-12-07 15:32:31 UTC
Description of problem:

By executing MRG/M testsuite on qpid-cpp-0.12-6.el6 packages, I've discovered some data loss in two of our tests. 

The issues found by these two tests seems to be the same:
Message loss when broker is killed while txtest client is rotating messages in queues

1.) /distribution/MRG/Messaging/qpid_test_transaction_integrity:

  The exact testing scenario is described here:
    https://tcms.engineering.redhat.com/case/122768/?from_plan=4988
    txtest client receives at final check stage less messages than expected
    there were multiple cases detected
  Test run data can be found here (search for 'ERROR:'):
    http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2011/12/1663/166310/348907/3859056/TESTOUT.log

some older test runs containing the same failures:
http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2011/10/1488/148859/310252/3401666/
http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2011/10/1482/148209/309029/3388674/
http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2011/10/1488/148858/310251/3401609/

This issue was also seen on 0.10-8 packages:
http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2011/10/1435/143567/298673/3291961/

note: From unknown reason this issue occurs more often on first beaker run, it is harder but possible to reproduce it by rerunning the test.

2.) Occasionally the message loss can be seen also by executing /distribution/MRG/Messaging/qpid_test_transaction_integrity test:

  The exact testing scenario is described here:
    https://tcms.engineering.redhat.com/case/122736/?from_plan=4986
    there were multiple cases detected
  Test run data can be found here (search for 'ERROR:'):
    http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2011/12/1653/165361/346696/3837792/
    http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2011/10/1488/148858/310251/3401608/

Version-Release number of selected component (if applicable):
python-qpid-0.12-1.el6.noarch
python-qpid-qmf-0.12-6.el6.x86_64
qpid-cpp-client-0.12-6.el6.x86_64
qpid-cpp-client-devel-0.12-6.el6.x86_64
qpid-cpp-client-devel-docs-0.12-6.el6.noarch
qpid-cpp-server-0.12-6.el6.x86_64
qpid-cpp-server-devel-0.12-6.el6.x86_64
qpid-cpp-server-store-0.12-6.el6.x86_64
qpid-cpp-server-xml-0.12-6.el6.x86_64
qpid-java-client-0.10-11.el6.noarch
qpid-java-common-0.10-11.el6.noarch
qpid-java-example-0.10-11.el6.noarch
qpid-qmf-0.12-6.el6.x86_64
qpid-qmf-debuginfo-0.12-6.el6.x86_64
qpid-qmf-devel-0.12-6.el6.x86_64
qpid-tests-0.12-1.el6.noarch
qpid-tools-0.12-2.el6.noarch
rh-qpid-cpp-tests-0.12-6.el6.x86_64
ruby-qpid-0.7.946106-2.el6.x86_64

How reproducible:
0.5%

Steps to Reproduce:
1. run the tests
2. check results
  
Actual results:
messages loss 

Expected results:
no messages loss 

Additional info:

Comment 1 Justin Ross 2012-12-07 14:37:46 UTC
*** Bug 814734 has been marked as a duplicate of this bug. ***

Comment 7 Frantisek Reznicek 2015-07-30 10:15:48 UTC
Raising reproducibility to 3%, issue is very likely dependent on machine specs.

Comment 8 Frantisek Reznicek 2015-09-10 07:31:59 UTC
This defect is in fact same as bug 1248460 on tracked on MRG/M 2.x line.

Effort in bug 1248460 showed the test bug fixed by bug 1248460 comment 13 commits.

It is very likely this defect has same test bug rootcause and thus no engineering content. This defect was partially tested by bug 1248460 beaker suite executions.

-> CLOSED (NOT-A-BUG)

Note: If we find out that problem persists then this defect is going to be reopened.


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