SQS Java 客户端异常 - com.amazonaws.SdkClientException：无法执行 HTTP 请求：权限被拒绝：连接

Question

我有一个 java (AWS Java SDK 1.11.313) SQS 消费者每 20 秒轮询一个队列，该队列已经运行了近一周。 在这段时间里，它有两次失败，两次都抛出以下异常：

com.amazonaws.SdkClientException: Unable to execute HTTP request: Permission denied: connect
        at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleRetryableException(AmazonHttpClient.java:1114)
        at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1064)
        at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:743)
        at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:717)
        at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:699)
        at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:667)
        at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:649)
        at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:513)
        at com.amazonaws.services.sqs.AmazonSQSClient.doInvoke(AmazonSQSClient.java:2033)
        at com.amazonaws.services.sqs.AmazonSQSClient.invoke(AmazonSQSClient.java:2009)
        at com.amazonaws.services.sqs.AmazonSQSClient.executeReceiveMessage(AmazonSQSClient.java:1485)
        at com.amazonaws.services.sqs.AmazonSQSClient.receiveMessage(AmazonSQSClient.java:1460)
        at net.myCompany.messageHandlers.QMessageHandler.receiveMsg(QMessageHandler.java:112)
        at net.myCompany.MessageHandler.receiveDirectMsg(MessageHandler.java:23)
        at net.myCompany.commandProcessors.QCommandProcessor.run(QCommandProcessor.java:23)
        at java.lang.Thread.run(Thread.java:748)
Caused by: java.net.SocketException: Permission denied: connect
        at java.net.DualStackPlainSocketImpl.connect0(Native Method)
        at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:83)
        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
        at java.net.Socket.connect(Socket.java:589)
        at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:339)
        at com.amazonaws.http.conn.ssl.SdkTLSSocketFactory.connectSocket(SdkTLSSocketFactory.java:132)
        at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142)
        at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:373)
        at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at com.amazonaws.http.conn.ClientConnectionManagerFactory$Handler.invoke(ClientConnectionManagerFactory.java:76)
        at com.amazonaws.http.conn.$Proxy9.connect(Unknown Source)
        at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:381)
        at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:237)
        at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185)
        at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56)
        at com.amazonaws.http.apache.client.impl.SdkHttpClient.execute(SdkHttpClient.java:72)
        at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1236)
        at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1056)
        ... 14 more 

在这两种情况下，客户端都在大约 15 分钟后恢复了。 下面的方法负责创建和发送接收请求。 异常出现在 for 循环上方的sqs.receiveMessage()方法调用上。 每次发送请求时， com.amazonaws.services.sqs.AmazonSQS创建一个新的com.amazonaws.services.sqs.AmazonSQS实例并将其分配给sqs变量。

List<JSONObject> receiveMsg() {

        List<JSONObject> cmdMsgList = new ArrayList<>();

        try {
            if(sqs != null) {
                System.out.println("Attempting message receive at: " + Instant.now());
                // Receive messages
                ReceiveMessageRequest receiveMessageRequest = new ReceiveMessageRequest(commandQUrl);
                receiveMessageRequest.setWaitTimeSeconds(20);
                receiveMessageRequest.setMaxNumberOfMessages(10);
                List<Message> messages = sqs.receiveMessage(receiveMessageRequest).getMessages();
                for (Message message : messages) {
                    JSONObject msgBody = checkTargetDevice(message);
                    if (msgBody != null) {
                        cmdMsgList.add(msgBody);
                    }
                }
            } else {
                ServiceManager.getInstance().setServerConnection(false);
                ServiceManager.getInstance().setConnectionStatus("Can't receive message - Message channel does not exist");
            }

        } catch (QueueDoesNotExistException mia) {
            ServiceManager.getInstance().setServerConnection(false);
        }catch (AmazonServiceException ase) {
            if(ServiceManager.getInstance().isDebug()) {
                ase.printStackTrace();
                ase.getErrorMessage();
            }
        } catch (AmazonClientException ace) {
            if(ServiceManager.getInstance().isDebug()) {
                ace.printStackTrace();
            }
        }

        return cmdMsgList;
}

我认为可能创建了太多连接并且没有正确关闭，但是在使用 netstat 之后，该程序只有几个 tcp 连接似乎并不过分。 此后，我在 return 语句之前添加了sqs.shutdown()调用，但是我不期望有太大变化，因为AWS 文档指出AmazonSQS接口上的此方法调用是可选方法，并且预计调用者不会调用它。

非常感谢有关此问题的任何见解或建议。 提前致谢。

Answer 1

在从 aws SQS 轮询数据期间，我面临同样的非周期性问题。我添加了延迟调用 aws SQS 的时间，此问题已解决。如下在 JAVA 中。

final ReceiveMessageRequest receiveMessageRequest = 
    new ReceiveMessageRequest(sqsURL)
    .withMaxNumberOfMessages(1)
    .withWaitTimeSeconds(6);

希望这将解决这个问题。