2017-10-19 138 views
4

我遇到一个奇怪的问题,其中org.apache.http.NoHttpResponseException作为未经检查的异常抛出,即使是已检查的异常,因为它延伸java.io.IOException ...从以下内容可以看出发布stacktrace我收到一个异常,应该在编译时检查为未经检查的运行时异常。作为运行时异常抛出的NoHttpResponseException即使是已检查的异常

,我得到的是如下异常的堆栈跟踪(我的课是在包:com.example.staticsite):

org.apache.http.NoHttpResponseException: sqs.eu-west-1.amazonaws.com failed to respond 
    at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:143) 
    at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:57) 
    at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:260) 
    at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:283) 
    at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:251) 
    at org.apache.http.impl.conn.ManagedClientConnectionImpl.receiveResponseHeader(ManagedClientConnectionImpl.java:197) 
    at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:271) 
    at com.amazonaws.http.protocol.SdkHttpRequestExecutor.doReceiveResponse(SdkHttpRequestExecutor.java:66) 
    at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:123) 
    at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:685) 
    at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:487) 
    at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863) 
    at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) 
    at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57) 
    at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:728) 
    at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:489) 
    at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:310) 
    at com.amazonaws.services.sqs.AmazonSQSClient.invoke(AmazonSQSClient.java:2419) 
    at com.amazonaws.services.sqs.AmazonSQSClient.receiveMessage(AmazonSQSClient.java:1130) 
    at com.example.staticsite.aws.SqsReceiverImpl.receiveReceipt(SqsReceiverImpl.java:57) 
    at com.example.staticsite.core.processsite.ProcessSiteImpl.runOneTime(ProcessSiteImpl.java:59) 
    at com.example.staticsite.core.processsite.ProcessSiteImpl.run(ProcessSiteImpl.java:44) 
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:473) 
    at java.util.concurrent.FutureTask.run(FutureTask.java:262) 
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152) 
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622) 
    at java.lang.Thread.run(Thread.java:748) 

被扔我的代码里面异常的方法是:

public class SqsReceiverImpl implements SqsReceiver { 
    private AmazonSQS client; 
    private String queueUrl; 

    @Inject 
    public SqsReceiverImpl(AmazonSQS client,@Assisted String queueUrl) {   
     this.client = client; 
     this.queueUrl = queueUrl; 
    } 

    public List<String> receiveReceipt() throws SqsReceiverException { 
     if(queueUrl == null) 
      throw new SqsReceiverException(SqsReceiverException.MESSAGE_NO_QUEURURL); 
     ReceiveMessageRequest request = new ReceiveMessageRequest(); 
     request.setMaxNumberOfMessages(10); 
     request.setQueueUrl(queueUrl); 
     request.setWaitTimeSeconds(20); 

     ReceiveMessageResult results = null; 
     try { 
      results = client.receiveMessage(request); 
     } 
     catch(OverLimitException oe){ 
      throw new SqsReceiverException("OverLimitException thrown"); 
     } 
     catch(AmazonServiceException oe){ 
      throw new SqsReceiverException("AmazonServiceException thrown"); 
     } 
     catch(AmazonClientException oe){ 
      throw new SqsReceiverException("AmazonClientException thrown"); 
     } 

SqsReceiverException定义如下:

public class SqsReceiverException extends Exception{ 

    public SqsReceiverException(String messageNoQueururl) { 
     super(messageNoQueururl); 
    } 
    public static final String MESSAGE_NO_QUEURURL = "Queue url not found. Se the queue url"; 
} 

只POM的文件依赖条件的声明如下:

<dependencies> 
     <dependency> 
     <groupId>junit</groupId> 
     <artifactId>junit</artifactId> 
     <version>4.11</version> 
     <scope>test</scope> 
    </dependency> 
    <dependency> 
    <groupId>log4j</groupId> 
    <artifactId>log4j</artifactId> 
    <version>1.2.17</version> 
</dependency> 
<dependency> 
    <groupId>com.amazonaws</groupId> 
    <artifactId>aws-java-sdk-sqs</artifactId> 
    <version>1.10.12</version> 
</dependency> 
<dependency> 
    <groupId>org.mockito</groupId> 
    <artifactId>mockito-core</artifactId> 
    <version>1.10.19</version> 
    <scope>test</scope> 
</dependency> 
<dependency> 
    <groupId>com.google.inject</groupId> 
    <artifactId>guice</artifactId> 
    <version>4.0</version> 
</dependency> 
<dependency> 
    <groupId>com.google.inject.extensions</groupId> 
    <artifactId>guice-assistedinject</artifactId> 
    <version>4.0</version> 
</dependency> 
<dependency> 
    <groupId>org.apache.commons</groupId> 
    <artifactId>commons-lang3</artifactId> 
    <version>3.4</version> 
</dependency> 
</dependencies> 

生产这种结果:

Maven dependencies tree

怎么可能,这个异常threated为未选中,同时应检查? 有什么我在这里失踪?

异常并不总是重复性,因为它只发生在生产时,有来自亚马逊的服务缺失的响应。

更新

我验证下来的堆栈跟踪,直到到达AmazonHttpClient类,而有这个代码是捕捉`IOException异常”:

catch (IOException ioe) { 
       if (log.isInfoEnabled()) { 
        log.info("Unable to execute HTTP request: " + ioe.getMessage(), ioe); 
       } 
       captureExceptionMetrics(ioe, awsRequestMetrics); 
       awsRequestMetrics.addProperty(AWSRequestID, null); 
       AmazonClientException ace = new AmazonClientException(
         "Unable to execute HTTP request: " + ioe.getMessage(), 
         ioe); 
       if (!shouldRetry(request.getOriginalRequest(), 
           p.apacheRequest, 
           ace, 
           p.requestCount, 
           config.getRetryPolicy())) { 
        throw lastReset(ace, request); 
       } 
       // Cache the retryable exception 
       p.retriedException = ace; 
      } 

而且lastReset应该是负责抛出的异常,我不明白的是如何记录异常可能是org.apache.http.NoHttpResponseException ...

堆栈跟踪之前的行总是s:

2017-09-15 07:41:39 INFO AmazonHttpClient:496 - Unable to execute HTTP request: sqs.eu-west-1.amazonaws.com failed to respond 
+0

您使用的是哪种AmazonSqs客户端?异步版本? –

+0

奇怪的确是因为异常类型也没有改变,它确实只是一个IOException。这在客户端运行到亚马逊方? –

+0

它运行在亚马逊EC2实例上,亚马逊红帽子linux AMI – aleroot

回答

2

我的猜测是你是堆栈跟踪格式化的受害者。

我认为你是对的,当你用手指lastReset()作为罪魁祸首。这是您看到throws IOException从堆栈轨迹中消失的位置。这种方法显然抛出了一个AmazonClientException(运行时异常),其中原始的NoHttpResponseException“内部”。

你可以像这样用一个片段模拟这个:

throw new AmazonClientException("Oh no!", new NoHttpResponseException("The AWS server doesn't like you")); 

如果我插入这行代码到现有的Java应用程序(春季启动,在这种情况下),这是我在Eclipse中看到控制台:

No sign of the runtime exception

AmazonClientException的标志!直到,我向右滚动:

There it is

亚马逊的决定去与unchecked异常,并documented it here

因此,他们确实(我敢肯定)将您的IOException包装在运行时异常中,通过给予您“对您处理的错误的精细控制”来“帮助”您,尽管这并不总是很明显。

所有这一切说,我可能是错的。如果我是对的,我希望看到您的自定义SqsReceiverException位于堆栈顶部,因为您确实抓到了AmazonClientException

在堆栈跟踪之前很难确定没有标准的最后几行。如果我不符合标准,你可以发布它们吗?

更新

你更新了(AmazonHttpClient:496)问题上的线是打印栈跟踪行。当您通过Throwablelog.info()时,将会打印堆栈跟踪。此痕迹正在记录之前您的异常被包装并重新抛出。

因此,此位被看似“吞噬”:

com.amazonaws.AmazonClientException: Unable to execute HTTP request: sqs.us-east-1.amazonaws.com failed to respond 
    at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:500) 
    at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:310) 
    at com.amazonaws.services.sqs.AmazonSQSClient.invoke(AmazonSQSClient.java:2419) 
    at com.amazonaws.services.sqs.AmazonSQSClient.receiveMessage(AmazonSQSClient.java:1130) 
    at httptest.Main.main(Main.java:32) 
Caused by: 

,我可以不丢失SqsReceiverException说话。但我不认为DefaultRequestDirector.execute()的签名是谎言,我不认为我们正在处理编译器错误。

也许您可以将oe.printStackTrace()添加到您的catch (AmazonClientException oe)区块?

最后,我建议通过调试器来完成这一步。为了模拟您的生产问题,只需在DefaultHttpResponseParser:140处设置一个断点,在此行执行后,将i更改为-1。然后将堆栈退回到您的代码。

我还在AmazonHttpClient:971设置了一个断点,所以我可以更改retries并避免四次循环。

+1

在最后使用始终在堆栈跟踪之前的行更新了问题,在其之前或之后没有其他相关行。我在日志文件中根本没有'SqsReceiverException'。这是最奇怪的事情。 – aleroot

+0

@aleroot感谢您更新问题。我相应地更新了我的答案。 –