Shulou(Shulou.com)06/02 Report--

Today, the editor will share with you the relevant knowledge points of coping strategies when JVM anomalies occur. The content is detailed and the logic is clear. I believe most people still know too much about this knowledge, so share this article for your reference. I hope you can get something after reading this article. Let's take a look at it.

Several situations of JVM exception catch

JVM exceptions, called Error (errors) or Exception (JVM exceptions) in Java, are subclasses of the Throwable class and are caused by runtime errors in the program, such as a reference to a null pointer. The program uses throw statements.

When a JVM exception occurs, the Java virtual machine takes the following actions:

1. Check the catch clause table associated with the current method. Each catch clause contains its valid instruction scope, the type of JVM exception that can be handled, and the address of the code block that handles the JVM exception.

2. The catch clause that matches the JVM exception should meet the following conditions: the instruction that caused the JVM exception is within the scope of its instruction, and the type of JVM exception that occurs is a subtype of the type of JVM exception it can handle. If a matching catch clause is found, the system moves to the specified JVM exception handling block for execution; if no JVM exception handling block is found, the process of finding a matching catch clause is repeated until all nested catch clauses of the current method are checked.

3. Since the virtual machine continues to execute from * matching catch clauses, the order in the catch clause table is important. Because the Java code is structured, you can always arrange all the JVM exception handlers of a method into a table in order, and for the values of any possible program counter, you can find the appropriate JVM exception handling block in linear order to handle JVM exceptions that occur under the program counter value.

4. If no matching catch clause is found, the current method gets a result of "unintercepted JVM exception" and returns it to the caller of the current method as if the JVM exception had just occurred in its caller. If the corresponding JVM exception handling block is still not found in the caller, the error will be propagated. If the error is propagated to the top level, a default JVM exception handling block is invoked.

These are all the contents of this article entitled "what are the strategies for dealing with JVM anomalies?" Thank you for reading! I believe you will gain a lot after reading this article. The editor will update different knowledge for you every day. If you want to learn more knowledge, please pay attention to the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.