>From the protocol trace I dont see anything suggesting that you are missing something, it appears to be a bug in Service Bus. It doesnt send the consumer a message, therefore the consumer cant give you one.
The trace shows a repeating pattern of 3 messages being sent synchronously, the application logging it has sent a message, the client issuing a 'draining' flow with 1 message credit for the zero-prefetch consumer, and the server reacting by responding that it has consumed the credit, without sending a message. If there are messages available it would be expected it instead sent a message using the credit, and not a 'response flow' indicating some or all credit was consumed/drained without transferring messages (which happens if there aren't enough messages to consume/drain it all by sending them). Robbie On Wed, 19 Jun 2019 at 10:56, akabhishek1 <mailbox.abhishek.ku...@gmail.com> wrote: > > Hi Robbie, > > Please find the attached log. I kept the application idle for 9m, but > consumer doesn't receive any message. > > As i am consuming message on demand, so client should receive message if > message available on broker. I checked broker and i can confirm that, > messages are avalaible on queue. > > Please suggest me if i am missing anything or is this a defect? > > Regards, > Abhishek Kumar > > ReceiveNoWaitLogs.txt > <http://qpid.2158936.n2.nabble.com/file/t396358/ReceiveNoWaitLogs.txt> > > > > -- > 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 > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
