Open rpbrehm opened 8 years ago
Do we have any update here? We also need to send bigger data now.
I also encountered this problem. Any update on this?
+1
Any update?
@alainsahli One hurdle to implementing the Amazon SQS Extended Client Library within Spring Cloud AWS is that there isn't an AsyncClient implementation, and Amazon isn't working on one either.
We could create another module (e.g. spring-cloud-aws-messaging-extended) and duplicate much of the configuration but with a non-async method signature. This obviously isn't elegant.
Do you have any other thoughts on how we can achieve this?
About to start a new implementation using aws-cloud and extended lib, did anyone come up with a solution to this ?
any update on this issue? It would be good to have it fixed.
Still having the issue. Any workaround for this ?
I forked it out to make it work with spring; check this one out; https://github.com/varunmehta/amazon-sqs-java-extended-client-lib
I forked it out to make it work with spring; check this one out; https://github.com/varunmehta/amazon-sqs-java-extended-client-lib
Is this likely to be merged? Looks like a good solution.
ANy update here?
Have implemented support for async as per new version changes fo xtended lib library https://github.com/Harsha-changejar/amazon-sqs-java-extended-client-lib?organization=Harsha-changejar&organization=Harsha-changejar
I have run into the issue with message size > 256mb and Spring AWS Cloud not supporting AWS extended SQS client library.
Error explanation from production log: Service: AmazonSQS; Status Code: 400; Error Code: AWS.SimpleQueueService.BatchRequestTooLong; Request ID: _); nested exception is com.amazonaws.services.sqs.model.BatchRequestTooLongException: Batch requests cannot be longer than 262144 bytes. You have sent 262203 bytes.
This is code in production.
It seems that many users are running into this limitation and support for the extended client library should be provided.