Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@RabbitSubscribe noAck, how to???? #513

Open
gvillela7 opened this issue Oct 11, 2022 · 3 comments
Open

@RabbitSubscribe noAck, how to???? #513

gvillela7 opened this issue Oct 11, 2022 · 3 comments
Labels
bug Something isn't working rabbitmq

Comments

@gvillela7
Copy link

Hello,
How to use noack false parameter, forcing use of ack=true only after message processing?
My consumption is simple, I'm doing it like this:
@RabbitSubscribe({
exchange: 'exchange',
routingKey: 'create_payment_key',
queue: 'payment_queue',
})

public async consumer(msg: {}) {
const content = JSON.stringify(msg);
console.log(content);
}

Thanks.

@tamvo
Copy link

tamvo commented Nov 1, 2023

I have same issue. return new Nack() doesn't behave like noAck setting.

@underfisk underfisk added bug Something isn't working rabbitmq labels Jan 16, 2024
@huantaoliu
Copy link
Contributor

huantaoliu commented Jan 28, 2024

@gvillela7 so you want manually control ack? Currently ack it done automatically by the lib.

@kasir-barati
Copy link

Since it is not provided we can always reject a message and send it back to the queue. This way it'll be re-queued and not lost. I believe this solution works or am I forgetting something?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working rabbitmq
Projects
None yet
Development

No branches or pull requests

5 participants