Spring cloud AWS SQS侦听器常量发送请求

我已经使用SpringCloudAWSAPI实现了注释驱动的队列侦听器

<aws-messaging:annotation-driven-queue-listener   max-number-of-messages="10" task-executor="messagingTaskExecutor" wait-time-out="20"
                                                          visibility-timeout="100" amazon-sqs="sqsClient" region="us-west-1"  />

在下面的日志文件中，我可以看到请求不断发送到us-east-1区域，尽管我已经提供了us-west-1区域。请求发送间隔为每秒3个请求，这太多了

amz-sdk-invocation-id:4865f324-322f-53f2-9f4d-f989e106e96c
amz-sdk-retry:0/0/500
**host:sqs.us-east-1.amazonaws.com**
user-agent:aws-sdk-java/1.11.18 Mac_OS_X/10.11.6 Java_HotSpot(TM)_64-Bit_Server_VM/25.111-b14/1.8.0_111 AmazonSQSBufferedAsyncClient/1.11.18
x-amz-date:20170210T030639Z

amz-sdk-invocation-id;amz-sdk-retry;host;user-agent;x-amz-date
937d63370e14d7439a711514a14d0d371c3f6fc73208e1a9d54bd99f194e42a7"
2017-02-10 08:36:39 DEBUG AWS4Signer:33 - AWS4 String to Sign: '"AWS4-HMAC-SHA256
20170210T030639Z
20170210/us-east-1/sqs/aws4_request
07187f106ed69b4b3ad36be48ba53811adc903a39388c5b0a1677ad2af93f38b"
2017-02-10 08:36:39 DEBUG RequestAddCookies:122 - CookieSpec selected: default
2017-02-10 08:36:39 DEBUG RequestAuthCache:76 - Auth cache not set in the context
2017-02-10 08:36:39 DEBUG PoolingHttpClientConnectionManager:249 - Connection request: [route: {s}->https://sqs.us-east-1.amazonaws.com:443][total kept alive: 1; route allocated: 1 of 50; total allocated: 1 of 50]
2017-02-10 08:36:39 DEBUG PoolingHttpClientConnectionManager:282 - Connection leased: [id: 23][route: {s}->https://sqs.us-east-1.amazonaws.com:443][total kept alive: 0; route allocated: 1 of 50; total allocated: 1 of 50]
2017-02-10 08:36:39 DEBUG MainClientExec:207 - Stale connection check
2017-02-10 08:36:39 DEBUG wire:86 - http-outgoing-23 << "[read] I/O error: Read timed out"
2017-02-10 08:36:39 DEBUG DefaultManagedHttpClientConnection:90 - http-outgoing-23: set socket timeout to 50000
2017-02-10 08:36:39 DEBUG MainClientExec:255 - Executing request POST /189178718836/CMR HTTP/1.1
2017-02-10 08:36:39 DEBUG MainClientExec:266 - Proxy auth state: UNCHALLENGED
2017-02-10 08:36:39 DEBUG headers:135 - http-outgoing-23 >> POST /189178718836/CMR HTTP/1.1
2017-02-10 08:36:39 DEBUG headers:138 - http-outgoing-23 >> Host: sqs.us-east-1.amazonaws.com
2017-02-10 08:36:39 DEBUG headers:138 - http-outgoing-23 >> Authorization: AWS4-HMAC-SHA256 Credential=something/20170210/us-east-1/sqs/aws4_request, SignedHeaders=amz-sdk-invocation-id;amz-sdk-retry;host;user-agent;x-amz-date, Signature=0d110d904500fd10a5262c5beea63df72eff28627801d0c00f74d499d4750092
2017-02-10 08:36:39 DEBUG headers:138 - http-outgoing-23 >> X-Amz-Date: 20170210T030639Z
2017-02-10 08:36:39 DEBUG headers:138 - http-outgoing-23 >> User-Agent: aws-sdk-java/1.11.18 Mac_OS_X/10.11.6 Java_HotSpot(TM)_64-Bit_Server_VM/25.111-b14/1.8.0_111 AmazonSQSBufferedAsyncClient/1.11.18
2017-02-10 08:36:39 DEBUG headers:138 - http-outgoing-23 >> amz-sdk-invocation-id: 4865f324-322f-53f2-9f4d-f989e106e96c
2017-02-10 08:36:39 DEBUG headers:138 - http-outgoing-23 >> amz-sdk-retry: 0/0/500
2017-02-10 08:36:39 DEBUG headers:138 - http-outgoing-23 >> Content-Type: application/x-www-form-urlencoded; charset=utf-8
2017-02-10 08:36:39 DEBUG headers:138 - http-outgoing-23 >> Content-Length: 110
2017-02-10 08:36:39 DEBUG headers:138 - http-outgoing-23 >> Connection: Keep-Alive
2017-02-10 08:36:39 DEBUG wire:72 - http-outgoing-23 >> "POST /189178718836/CMR HTTP/1.1[\r][\n]"
2017-02-10 08:36:39 DEBUG wire:72 - http-outgoing-23 >> "Host: sqs.us-east-1.amazonaws.com[\r][\n]"
2017-02-10 08:36:39 DEBUG wire:72 - http-outgoing-23 >> "Authorization: AWS4-HMAC-SHA256 Credential=AKIAJRLXVVM5WJ5X7CFA/20170210/us-east-1/sqs/aws4_request, SignedHeaders=amz-sdk-invocation-id;amz-sdk-retry;host;user-agent;x-amz-date, Signature=0d110d904500fd10a5262c5beea63df72eff28627801d0c00f74d499d4750092[\r][\n]"
2017-02-10 08:36:39 DEBUG wire:72 - http-outgoing-23 >> "X-Amz-Date: 20170210T030639Z[\r][\n]"
2017-02-10 08:36:39 DEBUG wire:72 - http-outgoing-23 >> "User-Agent: aws-sdk-java/1.11.18 Mac_OS_X/10.11.6 Java_HotSpot(TM)_64-Bit_Server_VM/25.111-b14/1.8.0_111 AmazonSQSBufferedAsyncClient/1.11.18[\r][\n]"
2017-02-10 08:36:39 DEBUG wire:72 - http-outgoing-23 >> "amz-sdk-invocation-id: 4865f324-322f-53f2-9f4d-f989e106e96c[\r][\n]"
2017-02-10 08:36:39 DEBUG wire:72 - http-outgoing-23 >> "amz-sdk-retry: 0/0/500[\r][\n]"
2017-02-10 08:36:39 DEBUG wire:72 - http-outgoing-23 >> "Content-Type: application/x-www-form-urlencoded; charset=utf-8[\r][\n]"
2017-02-10 08:36:39 DEBUG wire:72 - http-outgoing-23 >> "Content-Length: 110[\r][\n]"
2017-02-10 08:36:39 DEBUG wire:72 - http-outgoing-23 >> "Connection: Keep-Alive[\r][\n]"
2017-02-10 08:36:39 DEBUG wire:72 - http-outgoing-23 >> "[\r][\n]"
2017-02-10 08:36:39 DEBUG wire:86 - http-outgoing-23 >> "Action=ReceiveMessage&Version=2012-11-05&AttributeName.1=All&MessageAttributeName.1=All&MaxNumberOfMessages=10"

amz sdk调用id:4865f324-322f-53f2-9f4d-f989e106e96c
amz sdk重试：0/0/500
**主持人：sqs.us-east-1.amazonaws.com**
用户代理：aws sdk java/1.11.18 Mac_OS_X/10.11.6 java_HotSpot（TM）_64位_Server_VM/25.111-b14/1.8.0_111 AmazonSQSBufferedAsyncClient/1.11.18
x-amz-日期：20170210T030639Z
amzsdk调用id；amz-sdk重试；主办用户代理；x-amz-date
937D63370E14D7439A7111514A14D0D371C3F6FC73208E1A9D54BD99F194E42A7“
2017-02-10 08:36:39调试AWS4签名者：33-要签名的AWS4字符串：“”AWS4-HMAC-SHA256
20170210T030639Z
20170210/us-east-1/sqs/aws4_请求
07187F106ED69B4B3AD36BE48BA53811ADC903A3838C5B0A1677AD2AF93F38B“
2017-02-10 08:36:39调试请求AddCookies:122-CookieSpec selected:默认
2017-02-10 08:36:39调试请求验证缓存：76-未在上下文中设置验证缓存
2017-02-10 08:36:39调试池客户端连接管理器：249-连接请求：[路由：{s}->https://sqs.us-east-1.amazonaws.com:443][保持活动状态的总数：1；分配的路由：1/50；分配的总数：1/50]
2017-02-10 08:36:39调试池客户端连接管理器：282-租用的连接：[id:23][路由：{s}->https://sqs.us-east-1.amazonaws.com:443][保持活动状态的总数：0；分配的路由：1/50；分配的总数：1/50]
2017-02-10 08:36:39调试主客户端XEC:207-陈旧连接检查
2017-02-10 08:36:39调试连线：86-http-outing-23>POST/189178718836/CMR http/1.1
2017-02-10 08:36:39调试头：138-http-outgoing-23>>主机：sqs.us-east-1.amazonaws.com
2017-02-10 08:36:39调试头：138-http-outgoing-23>>授权：AWS4-HMAC-SHA256凭证=something/20170210/us-east-1/sqs/AWS4_请求，SignedHeaders=amz sdk调用id；amz sdk重试；主机；用户代理；x-amz-date，签名=0D110D904500FD10A5262C5BEEA63DF72EFF2627801D0C0074D99D475092
2017-02-10 08:36:39调试头：138-http-outgoing-23>>X-Amz-Date:20170210T030639Z
2017-02-10 08:36:39调试头：138-http-outgoing-23>>用户代理：aws sdk java/1.11.18 Mac_OS_X/10.11.6 java_热点（TM）_64位_服务器_VM/25.111-b14/1.8.0_111 AmazonSQSBufferedAsyncClient/1.11.18
2017-02-10 08:36:39调试头：138-http-outgoing-23>>amz sdk调用id:4865f324-322f-53f2-9f4d-f989e106e96c
2017-02-10 08:36:39调试头：138-http-outgoing-23>>amz sdk重试：0/0/500
2017-02-10 08:36:39调试标题：138-http-outgoing-23>>内容类型：application/x-www-form-urlencoded；charset=utf-8
2017-02-10 08:36:39调试头：138-http-outing-23>>内容长度：110
2017-02-10 08:36:39调试头：138-http-outgoing-23>>连接：保持活动状态
2017-02-10 08:36:39调试连线：72-http-OUTING-23>>“POST/189178718836/CMR http/1.1[\r][\n]”
2017-02-10 08:36:39调试连线：72-http-outing-23>>“主机：sqs.us-east-1.amazonaws.com[\r][\n]”
2017-02-10 08:36:39调试连线：72-http-OUTING-23>>“授权：AWS4-HMAC-SHA256凭证=AKIAJRLXVVM5WJ5X7CFA/20170210/us-east-1/sqs/AWS4_请求，签名头=amz sdk调用id；amz-sdk重试；主办用户代理；x-amz-date，签名=0D110D904500FD10A5262C5BEEA63DF72EFF2862701D0C000F74D499D475092[\r][\n]”
2017-02-10 08:36:39调试连线：72-http-OUTING-23>>“X-Amz-Date:20170210T030639Z[\r][\n]”
2017-02-10 08:36:39调试连线：72-http-outgoing-23>>“用户代理：aws sdk java/1.11.18 Mac_OS_X/10.11.6 java_HotSpot（TM）64位_Server_VM/25.111-b14/1.8.0_111 AmazonSQSBufferedAsyncClient/1.11.18[\r][\n]”
2017-02-10 08:36:39调试连线：72-http-OUTING-23>>“amz sdk调用id:4865f324-322f-53f2-9f4d-f989e106e96c[\r][\n]”
2017-02-10 08:36:39调试连线：72-http-outing-23>>“amz sdk重试：0/0/500[\r][\n]”
2017-02-10 08:36:39调试连线：72-http-outing-23>>“内容类型：application/x-www-form-urlencoded；字符集=utf-8[\r][\n]“
2017-02-10 08:36:39调试连线：72-http-outing-23>>“内容长度：110[\r][\n]”
2017-02-10 08:36:39调试连线：72-http-outing-23>>“连接：保持活动[\r][\n]”
2017-02-10 08:36:39调试连线：72-http-outing-23>>“[\r][\n]”
2017-02-10 08:36:39调试连线：86-http-OUTING-23>>“操作=接收消息&版本=2012-11-05&AttributeName.1=All&MessageAttributeName.1=All&MaxNumberOfMessages=10”

有人能告诉我为什么spring cloud aws api本身不断地向us-east-1地区发送此请求吗？

等待超时=“20”

显示在配置中，但与正在发送的HTTP请求中的内容没有对应关系。这可能是

等待时间秒=“20”吗“

是否改为？在这里，我根据实际的SQSAPI参数名进行猜测。