If receiveNoWait returns null it means the client didnt have a message locally yet and the server didnt send the client a message when it 'drained' the link to provoke any possible delivery, so it has no message to give you. I suggest running with the protocol trace enabled to see if thats whats happening.
On Tue, 18 Jun 2019 at 17:05, akabhishek1 <[email protected]> wrote: > > Hi Team, > > We need to consume message based on polling duration. So i did testing for > "receive(long timeout)" and "receiveNoWait()". > > So far "receive(long timeout)" is working perfectly but there is an issue in > "receiveNoWait()" operation. > > Issue - "receiveNoWait()" operation not consuming message > > Please find attached class. I am publishing message continuously and > consuming as well. Publishing is working perfectly but i am not able to > receive message. > > If you change operation name from "receiveNoWait()" to "receive(long > timeout)", then we will start receiving message continuously. > > Am i doing any mistake? Could you please take a look on this issue. > > Broker - Azure ServiceBus > Qpid - qpid-jms-client-0.43.0 > Java - JDK8+ > > Regards, > Abhishek Kumar > > TestQpidRcvrNoWait.java > <http://qpid.2158936.n2.nabble.com/file/t396358/TestQpidRcvrNoWait.java> > > > > -- > Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html > > --------------------------------------------------------------------- > 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]
