title: Messages stuck in AWS SQS queue
body: <p>First, some context:</p>
  
  <p>I've implemented a async listener in Java for a SQS traditional queue (not FIFO), that triggers a callback each time a new message arrives at the queue. This listener is achieved using SQS JMS Library (as explained <a href="https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/getting-started.html#receive-messages-asynchronously" rel="nofollow noreferrer">here</a>). I'm also using the <a href="https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-s3-messages.html" rel="nofollow noreferrer">SQS Extended Client Library</a> to manage large messages (> 256KB) trough S3.</p>
  
  <p>Using the SQS JMS along with the SQS Extended Client Library presents a problem: each time a large message gets into the queue and then received in the callback I've to manually get the bucket id and key to retrieve the message itself (since in the queue there's only a pointer to the S3 file with the large message).</p>
  
  <p>The problem i'm facing right now is that some messages are not getting to the callback even tough they are in the queue and the receive count keeps incrementing. I really don't know what could be the problem. The only hint I have is that this messages are the one's with a pointer to a S3 file (this is not happening to all of the S3 messages, just to some of them).</p>
  
  <p>What is going on?
  Is it the problem that I'm using SQS JMS along with the SQS Extended Library? (Haven't found an example of this two working together in the documentation)</p>