跳至主要内容

JVM Startup and Inheritance

This blog is the follow up blog to answer this question:

Why is the main method in superclass executed by JVM?

class A
{
    public static void main(String[] args)
    {
        System.out.println("A.main");
    }
}

class B extends A{ }

If you execute

java B

you will see the console output:

A.main

Before going on, we can take a minute to think why it is works.


java B is to call main via JNI by JVM. So, yy viewing the process JVM load the class, we can see why it works clearly:

When JVM start up, it will load and initiate your class and invoke LauncherHelper#checkAndLoadMain which will validate if B has main memthod:

validateMainClass(mainClass);

And continue in validateMainClass, it invokes the Class#getMethod:

static void validateMainClass(Class<?> mainClass) {
    Method mainMethod;
    try {
        mainMethod = mainClass.getMethod("main", String[].class);
    } catch (NoSuchMethodException nsme) {
        // invalid main or not FX application, abort with an error
        abort(null, "java.launcher.cls.error4", mainClass.getName(),
              FXHelper.JAVAFX_APPLICATION_CLASS_NAME);
        return; // Avoid compiler issues
    }
...
}

Now, we can view the doc of getMethod:

Let C be the class or interface represented by this object:
C is searched for a matching method, as defined below. If a matching method is found, it is reflected.
If no matching method is found by step 1 then:
If C is a class other than Object, then this algorithm is invoked recursively on the superclass of C.
If C is the class Object, or if C is an interface, then the superinterfaces of C (if any) are searched for a matching method. If any such method is found, it is reflected.

It is clear that getMethod will invoke recusively up to the root of inheritance tree to find if there exist this method. In this case, it will first check whether B has main, not found; then check its superclass – A. This time, it find main then invoke it.

Ref

Written with StackEdit.

评论

此博客中的热门博文

Spring Boot: Customize Environment

Spring Boot: Customize Environment Environment variable is a very commonly used feature in daily programming: used in init script used in startup configuration used by logging etc In Spring Boot, all environment variables are a part of properties in Spring context and managed by Environment abstraction. Because Spring Boot can handle the parse of configuration files, when we want to implement a project which uses yml file as a separate config file, we choose the Spring Boot. The following is the problems we met when we implementing the parse of yml file and it is recorded for future reader. Bind to Class Property values can be injected directly into your beans using the @Value annotation, accessed via Spring’s Environment abstraction or bound to structured objects via @ConfigurationProperties. As the document says, there exists three ways to access properties in *.properties or *.yml : @Value : access single value Environment : can access multi...

LevelDB Source Reading (4): Concurrent Access

In this thread, we come to the issue of concurrent access of LevelDB. As a database, it can be concurrently accessed by users. But, it wouldn’t be easy to provide high throughput under product load. What effort does LevelDB make to achieve this goal both in design and implementation? Goal of Design From this github issue , we can see LevelDB is designed for not allowing multi-process access. this (supporting multiple processes) doesn’t seem like a good feature for LevelDB to implement. They believe let multiple process running would be impossible to share memory/buffer/cache, which may affect the performance of LevelDB. In the case of multiple read-only readers without altering the code base, you could simply copy the file for each reader. Yes, it will be inefficient (though not on file systems that dedupe data), but then again, so would having multiple leveldb processes running as they wouldn’t be able to share their memory/buffer/etc. They achieve it by adding a l...

LevelDB Source Reading (3): Compaction

LevelDB Source Reading (3): Compaction In the last blog that analyzes read/write process of Leveldb, we can see writing only happens to log file and memory table, then it relies on the compaction process to move the new updates into persistent sorted table for future use. So the compaction is a crucial part for the design, and we will dive into it in this blog. Compaction LevelDB compacts its underlying storage data in the background to improve read performance. The upper sentence is cited from the document of Leveldb , and we will see how it is implemented via code review. Background compaction // db_impl.cc void DBImpl :: MaybeScheduleCompaction ( ) { // use background thread to run compaction env_ - > Schedule ( & DBImpl :: BGWork , this ) ; } Two main aspects // arrange background compaction when Get, Open, Write void DBImpl :: BackgroundCompaction ( ) { // compact memtable CompactMemTable ( ) ; // compact ...