Skip to content
This repository has been archived by the owner on Aug 29, 2024. It is now read-only.

how to set the receive mode to "RECEIVEANDDELETE" in spring cloud stream service bus binder #511

Closed
vnicers opened this issue Apr 11, 2019 · 4 comments
Assignees
Labels

Comments

@vnicers
Copy link

vnicers commented Apr 11, 2019

I see from the log that the default value of the receiver is PeekLock.
c.m.azure.servicebus.MessageReceiver : Creating MessageReceiver to entity 'xxx-topic/subscriptions/xxx-subscription', ReceiveMode 'PEEKLOCK'
how to set the receiver to "ReceiveMode.RECEIVEANDDELETE" ?

@vnicers vnicers changed the title When using Spring Cloud Stream Service Bus Queue Binder And Topic Binder, how to set the receive mode to "RECEIVEANDDELETE" how to set the receive mode to "RECEIVEANDDELETE" in spring cloud stream service bus binder Apr 11, 2019
@warrenzhu25
Copy link

Currently, setting ReceiveMode.RECEIVEANDDELETE is unsupported. But I want to understand the reason why you want to explicitly set this. From functional point, using this mode might cause message loss.

@vnicers
Copy link
Author

vnicers commented Apr 15, 2019

@warrenzhu25 Our company intends to replace RabbitMQ with Service Bus in the production environment, so we used the Service Bus SDK and Spring Cloud Stream Binder for some performance tests, but using PeekLock mode found that the performance is much worse than RabbitMQ, so I want to try the RECEIVEANDDELETE mode again.

@saragluna saragluna added the azure-spring All azure-spring related issues label Jul 22, 2020
@pablosguajardo
Copy link

hello, could you see how to create the queue in "ReceiveMode.RECEIVEANDDELETE"?
I'm using an azure function developed with .net, from there it can be changed to "ReceiveMode.RECEIVEANDDELETE"?

@saragluna
Copy link
Contributor

@pablosguajardo sorry for the late response. We've deprecated this repo, so I created an issue there.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants