Comments on: The Amazon AWS Java SQS Client is *Not* Thread-safe https://www.selikoff.net/2018/02/14/the-amazon-aws-java-sqs-client-not-thread-safe/ Java/J2EE Software Development and Technology Discussion Blog Mon, 30 Apr 2018 13:09:44 +0000 hourly 1 https://wordpress.org/?v=6.9.4 By: Dag https://www.selikoff.net/2018/02/14/the-amazon-aws-java-sqs-client-not-thread-safe/comment-page-1/#comment-197775 Mon, 30 Apr 2018 13:09:44 +0000 https://www.selikoff.net/?p=8576#comment-197775 In general, using dozens of threads to unload the queue isn’t a sensible approach imho. You’d usually use a single threaded queue client to receive messages and hand them off for processing in another thread(pool)

]]> By: Jakub Wojciak https://www.selikoff.net/2018/02/14/the-amazon-aws-java-sqs-client-not-thread-safe/comment-page-1/#comment-195963 Thu, 15 Feb 2018 17:17:43 +0000 https://www.selikoff.net/?p=8576#comment-195963 In the AWS SDK there is a default limit of max http connections allowed. If you exceed this limit, new requests will end up waiting on the http connections to become available again. In your case, the long poll ReceiveMessage requests are ‘drowning out’ your DeleteMessage calls. If you plan to use many threads to call AWS services, make sure to adjust this setting.

You can adjust this setting using the ClientConfiguration class:
https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/ClientConfiguration.html

Here are more details:
https://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/section-client-configuration.html

]]>