- Bug fix:
SQSMessageConsumer@receiveNoWait()fails to return messages whennumberOfMessagesToPrefetchis 0 - Add log message when a received message can't be converted
- Support receiving message attributes with types of the form "String." or "Number."
Assets
2
- Add support for MessageProducer.setDeliveryDelay() (PR #40)
Assets
2
-
Add support for SQS messages with a "Type" of "Number" (PR #71)
-
Preserve the JMS Correlation ID when sending and receiving messages (PR #63)
-
Fix failure to increment messagesRequested in receive methods. In rare cases this could cause a SQSMessageConsumer with numberOfMessagesToPrefetch set to 0 to get stuck and no longer receive messages.
Assets
2
-
Support for the
JMSReplyToDestinationmessage header field, which now correctly persists through Amazon SQS. Use this field to avoid making extra calls to the Amazon SQSGetQueueUrlAPI action. -
Support for setting the
numberOfMessagesToPrefetchconnection parameter to0. In this mode, messages are retrieved from Amazon SQS only when you make explicitreceive()orreceive(long)calls to message consumers, or when you attach a message listener to a consumer.Note: This mode can result in better performance in cases when handling messages is expensive.
Assets
2
Support for custom AmazonSQS client implementations to be passed in to the SQSConnectionFactory.
This version is compatible with Amazon SQS Extended Client Library (https://github.com/awslabs/amazon-sqs-java-extended-client-lib), which opens up the possibility of sending large messages through the JMS provider.
