If you receive messages with an AMQP delivery-count value greater than 0, then its likely either the server has incremented it due to some prior behaviour (e.g sent to a client, not consumed, returned to server), or alternatively there is bug in play. Sending a single message though and consuming it immediately with a single active consumer that remains live the entire time could answer which of those it is.
I don't know how, or whether its even possible, to disable the Azure Service Bus server-side 'peek locking'. Perhaps their documentation or support can assist you there. Robbie On 11 May 2017 at 12:14, kapilaArora <[email protected]> wrote: > First Part - Currently we are using Qpid JMS 0.11.1 to connect the Azure > service bus . this connectivity is going on the PEEK_LOCK Mode with Azure > Service bus using Qpid JMS 0.11.1 When we are receiving the messages , We > are receiving the Re-delivered messages with delivery count >0 and many > messages are moving in the deadletterqueue on service bus as well . how we > can make this connectivity without receiving the re-delivered messages and > without data loss.Second part - how we can switch this connectivity from > PEEK_LOCK to Receive and delete mode for azure service bus using JMS Qpid > 0.11.1 , is there any way , we can change it ? > > > > -- > View this message in context: > http://qpid.2158936.n2.nabble.com/Receing-re-delivered-messages-using-Qpid-JMS-0-11-1-with-Azure-Service-Bus-AMQP-Connectivity-tp7663045.html > Sent from the Apache Qpid users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
