qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From et3w503 <et3w...@yahoo.com>
Subject Why not earse unacked DeliveryRecords?
Date Tue, 09 Aug 2011 07:10:24 GMT
Dear all:

My qpidd server crashed because consumer's behavior.

My consumer program(client) always released message if something could not
be done in Subscribe callback.

But some things are interesting when I looked for the reason why qpidd will

I found if consumer release message in Subscribe callback, the qpidd server
will not earse unacked DeliveryRecords.


line 695. 

The size of unacked  DeliveryRecords will increase continually until qpidd
server crashes.

Why not earse unacked DeliveryRecords in SemanticState::release ? or any
other idea to prevent this situation?

View this message in context: http://apache-qpid-developers.2158895.n2.nabble.com/Why-not-earse-unacked-DeliveryRecords-tp6667136p6667136.html
Sent from the Apache Qpid developers mailing list archive at Nabble.com.

Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org

View raw message