You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After sending successfully a message to redis using RqueueMessageEnqueuer.enqueue(queueName, message), I'm consuming a messeage using @RqueueListener(value = "my-queue") annotation and while debugging i can see that while processing a message rqueue is updating the message status(message metaData) and its using a lockKey for the setNX command as plain messageId without the lockKey prefix ("__rq::lock::").
I saw there is a getLockKeyPrefix(String key) method in RqueueConfig class but its not being used through this process.
Is this behavior is normal and intended?
Is there a way to override/configure a lockKey prefix default or custom instead only a messageId, to use through a simple message consuming process I mentioned above?
Rqueue Version: 2.13.0-RELEASE
Spring Boot Version: 2.7.5
Thank you.
The text was updated successfully, but these errors were encountered:
Hi,
After sending successfully a message to redis using RqueueMessageEnqueuer.enqueue(queueName, message), I'm consuming a messeage using @RqueueListener(value = "my-queue") annotation and while debugging i can see that while processing a message rqueue is updating the message status(message metaData) and its using a lockKey for the setNX command as plain messageId without the lockKey prefix ("__rq::lock::").
I saw there is a getLockKeyPrefix(String key) method in RqueueConfig class but its not being used through this process.
Is this behavior is normal and intended?
Is there a way to override/configure a lockKey prefix default or custom instead only a messageId, to use through a simple message consuming process I mentioned above?
Thank you.
The text was updated successfully, but these errors were encountered: