Closed sultanfariz closed 1 year ago
I'd like to inform that this issue is no longer valid. It turns out that the issue occurred because I forgot to put the main thread blocking code, which caused the consumer to exit immediately after consuming the first message. Thanks :).
I have implemented a consumer that's supposed to fetch many messages. However, the consumer connection seems to be always closed even before i ack/nack the message. For my case, I expect it to be always idle. The code for the RabbitMQ consumer looks like this:
I need to make the consumer connection always idle and fetch as many messages as possible without closing the connection. Please suggest a solution to this issue.