◎위챗 : speedseoul
https://airbrake.io/blog/java/exceptionininitializererror
Moving along through our in-depth Java Exception Handling series, today we’ll dive into the ExceptionInInitializerError, which is thrown when an error occurs within the static initializer
of a class or object. Since an ExceptionInInitializerError
isn’t ever the cause of a thrown error, catching such an exception provides an underlying causal exception
that indicates what the actual source of the issue was.
Throughout this article we’ll examine the ExceptionInInitializerError
by looking at where it resides in the overall Java Exception Hierarchy. We’ll then explore a simple and fully-functional code sample that illustrates how a static initializer works, and what might lead to a thrown ExceptionInInitializerError
in such an initializer, so let’s get to it!
All Java errors implement the java.lang.Throwable
interface, or are extended from another inherited class therein. The full exception hierarchy of this error is:
java.lang.Object
java.lang.Throwable
java.lang.Error
java.lang.LinkageError
ExceptionInInitializerError
Below is the full code sample we’ll be using in this article. It can be copied and pasted if you’d like to play with the code yourself and see how everything works.
Since the appearance of an ExceptionInInitializerError
indicates a problem within a static initializer
, we should briefly examine what a static initializer is and how they’re typically used. Put simply, a static initializer block is a normal code block that is executed when the class is loaded.
A static initializer is created by enclosing code anywhere inside a class definition surrounded by braces ({
& }
) and also preceded by the static
keyword. For example:
As you can see in the code above, there can be as many static initializer blocks as desired within a class definition. Each will be executed in a top-down manner when the class is first loaded.
Static initializers are not to be confused with instance initializers
(or instance members
), which are executed when the class is instantiated (i.e. a new object of that class type
is created). Instance initializers are also executed just before the constructor
method.
An instance initializer is written inside a class definition using two braces ({
& }
), but without a preceding static
keyword:
Just as with static versions, multiple instance initializers can be defined and will be executed from top to bottom.
The purpose of a static initializer is typically to execute any initialization code that must occur before a class can be used. Critically, static initializers are only executed once ever, the first time that class is loaded. Thus, they are great for classes that are frequently used throughout the application, but only need some basic configuration code to be executed once before multiple instances are used elsewhere, such as a database connection class.
To test a static initializer in “real” code we’ve added a simple snippet and field to our trusty Book
class: