When is the static block of a class executed?

Question

I have 2 jars, let's call them a.jar and b.jar.

b.jar depends on a.jar.

In a.jar, I defined a class, let's call it StaticClass. In the StaticClass, I defined a static block, calling a method named "init" :

public class StaticClass {
  static {
    init();
  } 

  public void static init () {
    // do some initialization here
  }
}

in b.jar, I have a main, so in the main, I expect that the init() method has been called, but actually not. I suspect that is because the StaticClass has not been loaded by the jvm, could anyone tell me

Is my conclusion correct?
What triggers the jvm to load a class?
How can I get the static block executed automatically?

Thanks

You would have to use your StaticClass somwhere so it will be loaded and initialized. — Kris, Feb 03 '12 at 14:47
It looks like [this](http://stackoverflow.com/questions/3499214/java-static-class-initialization) might answer your question. — Andreas Baus, Feb 03 '12 at 14:49
possible duplicate of: http://stackoverflow.com/questions/2007666/in-what-order-do-static-initializer-blocks-in-java-run — Ciro Santilli OurBigBook.com, Feb 12 '15 at 12:11

score 95 · Accepted Answer · edited Nov 16 '15 at 20:02

95

Yes, you are right. Static initialization blocks are run when the JVM (class loader - to be specific) loads StaticClass (which occurs the first time it is referenced in code).

You could force this method to be invoked by explicitly calling StaticClass.init() which is preferable to relying on the JVM.

You could also try using Class.forName(String) to force the JVM to load the class and invoke its static blocks.

edited Nov 16 '15 at 20:02

Jeff

12,555
5
33
60

answered Feb 03 '12 at 14:52

ŁukaszBachman

33,595
11
64
74

1

"which occurs the first time it is referenced in code" - not always. Accessing a static primitive type doesn't seem to be triggering the static blocks. – Aug 07 '16 at 21:00
9

"static initialization blocks are run when the JVM loads StaticClass` --- incorrect, class loading is distinct from class initialization. – Marko Topolnik Sep 15 '16 at 07:35
4

"which occurs the first time it is referenced in code" --- incorrect, implementation is free to decide when to load the class. Referencing the class is only the _deadline_ when it definitely must be loaded. – Marko Topolnik Sep 15 '16 at 07:36
1

@MarkoTopolnik is right. "Static initialization blocks are run when the JVM loads StaticClass" is a wrong statement. static blocks executes during class initialization. " which is preferable to relying on the JVM" is another confusing statement, there is nothing to do with 'relying' in the case of StaticClass.init() , its simply a static method call. – Shafin Mahmud Nov 09 '16 at 05:20
@hthserhs Public static final primitive types and string are inlined during `javac`. Therefore, there isn't really an "access" from the stand point of JVM. As a result, the behavior is understandable. I just want to add some context. What you said is certainly correct. – Haozhun Sep 17 '20 at 22:44
The statement "which occurs the first time it is referenced in code" is completely wrong. The first time a class is referenced is often already at the `import` statement. Does importing a class trigger class loading? No. You can even write code like `Class cls = MyClass.class;` and `Supplier s = () -> new MyClass()` in your main method and as long as you don't call the suppliers `get` method, the class is not initialized and, therefore, the static block is **not** executed! (unless, ofc, the initialization happens by other means) – Alex R Dec 30 '21 at 13:17
"explicitly calling `StaticClass.init()` which is preferable to relying on the JVM":no it isn't. If you execute that statement the JVM will already have executed it, so you are executing it twice. There is nothing wrong with relying on the specified semantics of Java. – user207421 May 09 '23 at 10:16

score 7 · Answer 2 · edited May 23 '17 at 12:02

7

Yes you are right, since you are not using your StaticClass it is not loaded by the vm and therefore init() is never executed.

For your second question, you probably have to go the hard way and scan all available classes and load them.

https://stackoverflow.com/a/3223019/393657

edited May 23 '17 at 12:02

Community

1
1

answered Feb 03 '12 at 14:51

stryba

1,979
13
19

+1 for the hint on scanning all classes and automatically initializing those. It might be helpful to use a marker interface/annotation on the classes whose static initializer should automatically be executed (or any other defined static method). As said in the linked thread: Google Reflections might be a way to do that without much hassle. – Thomas Feb 03 '12 at 14:55

score 6 · Answer 3 · answered Jul 19 '19 at 04:12

First of all class loading is different than class initialization. For anyone looking for explanation from Java Language Specification, when is static block executed - here it is.

The JLS §8.7 says that :

A static initializer declared in a class is executed when the class is initialized (§12.4.2).

So what does the initialization mean? Let's refer to JLS §12.4.2. This describes detailed initialization procedure. However point JLS §12.4.1 might be more appropriate here. It says that :

A class or interface type T will be initialized immediately before the first occurrence of any one of the following:
T is a class and an instance of T is created.
T is a class and a static method declared by T is invoked.
A static field declared by T is assigned.
A static field declared by T is used and the field is not a constant variable (§4.12.4).
T is a top level class (§7.6), and an assert statement (§14.10) lexically nested within T (§8.1.3) is executed.

So to make the static initializer block to be executed automatically, you have to force one of those options to happen.

I wonder if we can assume that: class is initialized when is referenced by name in a code that is already running. — Pawel Dubiel, Sep 27 '19 at 13:38

score 4 · Answer 4 · answered Nov 09 '16 at 05:30

4

Static block is executed when a loaded class is initialized or referenced first. Loading class doesnt mean that class is to initialized. JVM Class Loading is separate things to concern.

answered Nov 09 '16 at 05:30

Shafin Mahmud

3,831
1
23
35

score 4 · Answer 5 · edited Oct 26 '18 at 09:19

4

You are right, the easiest way is to access the class, for instance do a

StaticClass.class.newInstance();

Or something to that respect in your main method. This will ensure the class is loaded by the classloader.

edited Oct 26 '18 at 09:19

zython

1,176
4
22
50

answered Feb 03 '12 at 14:50

Hiery Nomus

17,429
2
41
37

C.Champagne · Answer 6 · 2014-04-23T08:19:58.233

3

The static code is executed when your class (StaticClass I guess) is referenced.

Thus, it should be executed if you create a new instance of StaticClass or if you call one of its static methods.

edited Apr 23 '14 at 08:19

answered Feb 03 '12 at 14:51

C.Champagne

5,381
2
23
35

score 0 · Answer 7 · answered Mar 18 '13 at 12:48

0

in b.jar main method class should extend that StaticClass then automatically that static block and init() will be invoked

answered Mar 18 '13 at 12:48

santoshbharat

1

score 0 · Answer 8 · answered Feb 03 '12 at 14:51

0

Yes, the static initializer will be executed when the class is loaded. This normally occurs when you access the class in the class loading context for the first time.

answered Feb 03 '12 at 14:51

Thomas

87,414
12
119
157

AhsanAli Nandoliya · Answer 9 · 2013-05-20T09:17:00.197

-2

Adding some more:

static block will be executed when jvm load class.

Here in your example you can call init() method of your StaticClass by intantiating class

like StaticClass staticClass=new StaticClass();

or

StaticClass.class.newInstance(); this is more preferebal

edited May 20 '13 at 09:17

answered May 20 '13 at 07:31

AhsanAli Nandoliya

7
2

3

'This is more preferable' why? – user207421 Jan 29 '17 at 13:58

When is the static block of a class executed?

9 Answers9

Linked

Related