Hey Robbie, Thanks a lot for details !!
Yes messages are sending back to ServiceBus and Delivery Count is also increasing at first time. I was worried that why client is not reciving message again and how we will identify them. You pointed correctlly about deposition, I looked again bad messages in ServiceBus explorer and realized that all the bad messages are in Defferred state, So Client will not receive those messages due to Defferred state and will stay idle on broker. We need your input on below open questions to handle defer scenarion - 1. We are getting exception directly on 'onException' method where we don't have any details of JMS Message. Can you please guide us - how can we extract Message details of bad messages like - Message ID, Sequence NO, queue name ? Can we get hold of JMSMessage object? It will be so great if we can get hold it, so we can reject/abandon message. 2. As per microsoft (https://docs.microsoft.com/en-us/azure/service-bus-messaging/message-deferral), we can receive deferred message with the use of only Sequence Number. Do we have any option to receive deferred message with Qpid Client? It will be great for reconciliation. 3. Do we have any option to control Disposition? So for example we can specify deadletter rather than defer. 4. What is the disposition/delivery state set by qpid, that causes it to appear as deferred in Azure Service Bus? Regards, Abhishek Kumar -- Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
