Their documentation suggests they apply this 'deferred' state when a message has the 'modified' disposition set indicating the delivery-failed and undeliverable-here flags. I believe the client only does this in one place by itself, when it is unable to decode an arriving delivery and create a JMS Message from it. It emits a warning log message if that happens.
On Wed, 22 Jul 2020 at 19:54, vishnu pk <pkvishn...@gmail.com> wrote: > > Hi Team, > > I have a scenario where we are fetching records in Azure service bus with the > help of Qpid library in a 3rd party integration tool. It is noticed that > while fetching a large pile up of records from the Azue queue , many of the > records are not fetched but changed the status to 'deferred' in Azure > bus.Once changed the status to deferred it is never been picked up. > > As per Microsoft it is due to some modification/rejection of records from > clients who fetch messages from the queue. > > Does applying any Qpid property could change this behaviour?.. Appreciate > your advice on this . > > Expectation: The messages should not be changed to deferred state , rather it > can be redelivered or send to dead letter queue. > > Thanks a lot! > > Regards > Vishnu > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
