Receiver stops processing messages after sometime automatically

In our project, we have have few exchanges on which messages are transferred. I created one connection to qpid using rhea-promise. With the same connection I have created two different receivers listening to different exchanges. For some reason, after couple of hours(this time varies for different systems) receiver stops processing messages completely. However if I start a new receiver with exact same options after original receiver stops, new receiver works fine for same amount of time and same thing is repeated. Same thing happens for a topic as well, so I am guessing it is something todo with receiver.

The whole time checked, before and after processing messages, receiver had credit.

Receiver options are as follows:

source: { 
   address: Name of topic or exchange
},
credit_window: 1,
rcv_settle_mode: 1,
autoaccept: false

Is there a limit to number of messages a receiver can process? If so, can that be reset or made infinite?

P.S. This issue is show stopper for us.

[grs]

No, it is connection level only. My guess is that it is a different issue from your original report (which was due to the rcv_settle_mode). One suggestion would be to try and isolate the difference between the queue on which you have a problem and others and try to get a reproducer of some kind.

[GaikwadPratik]

@grs, @amarzavery ,

Is there a way to collect the logs from a particular queue, exchange or sender and receiver nodes? Because we are getting this issue in Production only for a particular queue. Restarting the consumer service which restarts(recreates) sender and receiver on that queue seems to work.