qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kyleh <ky...@us.ibm.com>
Subject python driver.py assert
Date Sat, 23 Nov 2013 13:29:58 GMT

I'm running an application that uses the python qpid client.  After a few
days of running I see it taking an exception on an assert.

2013-11-22 10:37:12.366 39246 TRACE root   File
"/usr/lib/python2.6/site-packages/qpid/messaging/driver.py", line 1280, in
2013-11-22 10:37:12.366 39246 TRACE root     assert rcv.received <
rcv.impending, "%s, %s" % (rcv.received, rcv.impending)
2013-11-22 10:37:12.366 39246 TRACE root AssertionError: 314516, 314516

Not being familiar with this code I put in some additional debug just to see
how rcv.received and rcv.impending were behaving.  I can see there is a
steady delta of 25 between them as the numbers grow.

2013-11-23 00:00:07.258 25623 DEBUG qpid.messaging [-] KYLE: imp 10372, rec
10347 do_message_transfer
2013-11-23 00:00:07.388 25623 DEBUG qpid.messaging [-] KYLE: imp 10373, rec
10348 do_message_transfer

I searched around and found this possibly related fix, but patching in the
changes really didn't seem to change the behavior at all. 

So now my questions.  Is it normal for the received and impending to
continuously grow?  What would cause the delta between them to go to zero
and trigger the assert?  And for that matter, what is "impending"?  Would
this assert point to an error in the application or in the qpid driver?


View this message in context: http://qpid.2158936.n2.nabble.com/python-driver-py-assert-tp7601130.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org

View raw message