blocks|key|1390667|text|您应该捕获Exception1，因为这是抛出的最后一个异常。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1390668|第一次Exception3被抛出并被抓住。捕获它的catch块抛出了Exception2。|1390669|然后Exception2被抓了。捕获块它抛出了Exception1。|1390670|entityMap^0|5|A|0|3|A|Y|A|0|2|A|N|A|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|K|$]]

You should catch <code>Exception1</code>, since that's the last exception that was thrown.

First <code>Exception3</code> was thrown and was caught. The catch block that caught it threw <code>Exception2</code>.

Then <code>Exception2</code> was caught. The catch block the caught it threw <code>Exception1</code>.

blocks|key|1150653|text|如果要对每个异常执行泛型处理，则需要捕获顶级异常(在您的情况下为Exception1+)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1150654|如果您想对每个异常执行特定的操作，则应该单独处理每个异常。|1150655|entityMap^0|W|A|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

You need to catch the top level exception which is <code>Exception1</code> in your case if you want to do generic handling in case of each exception

If you want to do specific stuff for each exception, you should handle each exception individually

blocks|key|2627296|text|解决这个问题的标准方法是捕捉代码导致的每一个异常。最糟糕的方法是捕获通用类Exception。如下所示：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|2627297|try+{
+++++MyObject.doAThingThatCausesAnException();
}+catch+(Exception+ex)+{
+++++//handle+your+exception+here
}|code-block|syntax|javascript|2627298|这是，而不是，您想用代码做什么，因为它是通用的。捕捉每一个异常，它将使用自己的catch块抛出，如.|2627299|try+{
+++++++MyObject.doAThingThatCausesAnException();
++++}+catch+(NullPointerException+ex1)++{
+++++++//handle+that+exception
++++}+catch+(SQLException+ex2)+{
+++++++//handle+that+exception
++++}+
++++//and+so+on...|2627300|我建议采用编程风格(第二种)，因为您不会忘记要处理的任何异常，并且可以在这些异常之间进行特定的划分。|2627301|entityMap^0|P|7|11|9|0|0|2|4|O|Q|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|D]]|E|@]|F|$]]|$1|G|3|H|5|I|7|Y|8|@]|E|@]|F|$J|K]]|$1|L|3|M|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]]|E|@]|F|$]]|$1|N|3|O|5|I|7|14|8|@]|E|@]|F|$J|K]]|$1|P|3|Q|5|6|7|15|8|@]|E|@]|F|$]]|$1|R|3|-4|5|6|7|16|8|@]|E|@]|F|$]]]|S|$]]

The standard way to solve this is to catch every exception that your code causes. The worsest way to do that is to catch the general class <code>Exception</code>. Like this:

<pre><code>try {
 MyObject.doAThingThatCausesAnException();
} catch (Exception ex) {
 //handle your exception here
}
</code></pre>

Thats not what you want to do with your code, because its to general. Catch every exception, that will be thrown with an own catch block like this.

<pre><code>try {
 MyObject.doAThingThatCausesAnException();
 } catch (NullPointerException ex1) {
 //handle that exception
 } catch (SQLException ex2) {
 //handle that exception
 } 
 //and so on...
</code></pre>

I recommend that programming style (second), because you do not forget any exceptions to handle and you can specific divide between the exceptions.

blocks|key|2627315|text|您看到的是在一定级别捕获异常并抛出新异常的良好实践，以便更好地理解异常的上下文。然而，包含来自较低级别例外的信息往往是有用的。这被称为链式例外。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2627316|例如，您可以在侦听套接字时捕获一个IOException，然后抛出一个(自定义)+NetworkException，以进一步区分它，同时将其传递到捕获并可能再次抛出的位置。|style|CODE|2627317|在您的情况下，您必须只捕获Exception1。不过，您可以将其原因用作如何处理异常的提示。|2627318|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.oracle.com/javase/tutorial/essential/exceptions/chained.html^0|1V|4|0|0|H|B|15|G|0|D|A|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@$A|W|B|X|F|G]|$A|Y|B|Z|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|10|8|@$A|11|B|12|F|G]]|9|@]|C|$]]|$1|J|3|-4|5|6|7|13|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]]]

What you see is a good practice to catch exceptions at a certain level and throw a new exception to provide a better understanding of the context of the exception to the one who catches the exceptions. It is however often useful to include the information from lower level exceptions. This is referred to as <a href="https://docs.oracle.com/javase/tutorial/essential/exceptions/chained.html" rel="nofollow">Chained Exceptions</a>.

You can for example catch an <code>IOException</code> while listening to a socket and then throw a (custom) <code>NetworkException</code> to differentiate it further while it is passed along to the point where it is caught and possibly rethrown again.

In your case you have to catch only <code>Exception1</code>. You can use its causes as hints how to handle the exception though.

In my application, I am seeing the logs which show

<pre><code>Exception1
caused by: Exception2
caused by: Exception3
</code></pre>

So, If I want to handle this scenario using try-catch, which exception should I give in my catch block? I'am using JDK 1.6, single catch for multiple exceptions is not my solution. Using multi-catch blocks is my last choice.

Exception caused by other exception

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在我的申请中，我看到的日志显示Exception1caused by: Exception2caused by: Exception3所以，如果我想使用try-catch来处理这个场景，我应该在catch块中给出哪个异常？我使用JDK 1.6，单一捕获多个异常不是我的解决方案。使用多捕捉块是我最后的选择。

问其他异常引起的异常
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问其他异常引起的异常EN