Bug 451049 - Suspected failure when command id wraps around
Suspected failure when command id wraps around
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp (Show other bugs)
beta
All Linux
urgent Severity high
: ---
: ---
Assigned To: Alan Conway
Kim van der Riet
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-12 11:44 EDT by Gordon Sim
Modified: 2009-05-07 16:09 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-12-02 11:06:31 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)

  None (edit)
Description Gordon Sim 2008-06-12 11:44:53 EDT
Left './src/tests/perftest --count 1000000 --iterations 5000 --size 64' running,
it got through 2147 iterations then exited:

  Sending start 1 times to pub_start
  Processing 1 messages from pub_done .SubscribeThread exception: Closed:
Comment 1 Gordon Sim 2008-06-12 11:45:46 EDT
Could also be the client (can't seem to mark more than one component).
Comment 2 Gordon Sim 2008-06-13 06:31:01 EDT
Same thing happened again at the same point, caught the broker output this time:

lt-qpidd: qpid/SessionState.cpp:132: virtual void
qpid::SessionState::senderRecordFlush(): Assertion `sender.flushPoint <=
sender.sendPoint' failed.

Comment 3 Alan Conway 2008-06-13 08:31:15 EDT
Comitted probable fix in revision 667503. gsim, please re run your long test,
I'll do the same and try to find some faster tricks for testing wrap-around.
Comment 4 Alan Conway 2008-06-13 13:38:57 EDT
Comitted fix for broker issues in Revision 667603.
Comment 5 Mike Bonnet 2008-06-19 23:53:39 EDT
qpidc-0.2.667603-1.el5, qpidc-perftest-0.2.667603-1.el5, qpidd-0.2.667603-1.el5, and rhm-0.2.2153-1.el5 have been pushed to the staging repo for testing

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