Description of problem: When a message is rerouted to the alternate exchange due to the message rejection, the reset of x-amqp-first-acquirer and x-amqp-delivery-count is done, which is not desired. This is only done for rejected message, not for messages rerouted for other reason (e.g. orphaned, or explicit qmf reroute request). So, it is probably needless inconsistency. For more details please see bug 1059786, comment 9. According to gsim comment it affects both amqp1.0 and amqp0-10. Version-Release number of selected component (if applicable): qpid-cpp-*-0.30-5 How reproducible: 100% Steps to Reproduce: 1. create a queue with alternate exchange defined 2. send a message towards the queue 3. subscribe to the alternate exchange 4. acquire and reject the message from the queue 5. list the properties of the message consumed from the alternate exchange: the 'x-amqp-first-acquirer' is set to True (false expected ~ the field shall not be present in the message properties map) the 'x-amqp-delivery-count' is equal to zero ~ not present in the properties map (non-zero value expected) Actual results: x-amqp-first-acquirer, x-amqp-delivery-count message fields reset is done when rejected message is rerouted to the alternate exchange Expected results: x-amqp-first-acquirer, x-amqp-delivery-count message fields reset is _not_ done when rejected message is rerouted to the alternate exchange Additional info:
Created attachment 980900 [details] Reproducer To compile: g++ -lqpidmessaging 1183140.cpp -o 1183140 To run: service qpidd restart ./1183140 Actual results: Message properties: {x-amqp-first-acquirer:True} Expected results: Message properties: {x-amqp-delivery-count:1}
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.