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

FiFo listener not pulling message again which was not processed #383

Open
Rajneesh-Testsigma opened this issue Jul 28, 2022 · 1 comment

Comments

@Rajneesh-Testsigma
Copy link

Hi, first of all thanks for the great library.

I am trying to use FIfoQueuelistener.As from FIFO sqs if any message was processed and deleted from queue, it would visible for other consumer after the expiry of messageVisiblityTimeout.... but in my case it is not appearing.

Do I need to configure anything else.

@JaidenAshmore
Copy link
Owner

No, it should work as-is. This does sound like a potential problem with your SQS configuration.

You can see an example FIFO message listener here: MessageListeners.java#L54 where we have examples of it randomly failing to process a message which eventually get picked up again after the timeout.

In this example above we set it up using a local elasticmq server and we set up the receive count and DLQ like so:

attributes.put(
      QueueAttributeName.REDRIVE_POLICY,
      String.format(
          "{\"deadLetterTargetArn\":\"%s\",\"maxReceiveCount\":\"%d\"}",
          deadLetterQueueArn,
          maxReceiveCount
      )
  )

see LocalSqsAsyncClientImpl.java#L21.

Do you have something similar set up in your SQS queue?

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

No branches or pull requests

2 participants