You won't see any 'warnings' from the protocol trace output you turned on, it doesn't have levels. You would just see e.g Disposition frames carrying a particular message state. The error log I mentioned would come from the 'regular' logging in the code, depending on configuration for whatever logging framework you are using. That was an example of where the client could send that disposition by itself, it may be there are no such errors:
I see that you are using the "jms.redeliveryPolicy.maxRedeliveries" option - per the docs, the default outcome applied if a message exceeds the limit is to send a modified-failed-undeliverable disposition. If that's whats making the client send such a disposition, it can be changed to something else via the "jms.redeliveryPolicy.outcome" option. Robbie On Sun, 16 Aug 2020 at 08:31, vishnu pk <[email protected]> wrote: > > Hi Robbie, > > Glad for your answers, > As suggested i tried to capture the log but couldn't find any 'Warnings' to > understand the core reason. > To enable log i Set the environment variable (not Java system property) > PN_TRACE_FRM to true. > > Could you suggest, if there is any other way to enable the extra logs in my > situation . As i said im using a 3rd party integration tool , All we are > doing here is, adding Qpid jars to JMS client & feeding .property connection > files with Qpid connection details. > > Qpid.Properties > connectionfactory.myFactoryLookupInbound = > amqps://<<Host>>?jms.username=<<Uname>>&jms.password=<<password>>&jms.prefetchPolicy.queuePrefetch=10&jms.redeliveryPolicy.maxRedeliveries=10&jms.forceAsyncAcks=true&jms.messageIDPolicy.messageIDType=UUID > queue.QUEUE1 = testQuuee > > > Thanks! > > > > > On 2020/07/23 14:08:11, Robbie Gemmell <[email protected]> wrote: > > 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 <[email protected]> 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: [email protected] > > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
