Services are not initialized in a concurrent way at GlassFish startup

[tnagao7]

Environment Details

• GlassFish Version (and build number): GlassFish 7.0.19
• JDK version: OpenJDK 21.0.4
• OS: Red Hat Enterprise Linux 8.6
• Database: none

Problem Description

At the GlassFish startup, HK2 services (classes annotated with org.jvnet.hk2.annotations.Service) are not initialized in a concurrent way.
The expected behavior is that services are initialized by four RunLevelControllerThreads, as in GlassFish 7.0.0-M7 or earlier.

Steps to reproduce

Start the DAS by asadmin start-domain and see the server log.
Then log records with _ThreadName=main can be found as below, which indicates the service initialization is executed on the main thread instead of RunLevelControllerThread.

$ cat /opt/glassfish-7.0.19/glassfish7/glassfish/domains/domain1/logs/server.log | grep -1 "Running GlassFish Version"
[2024-11-15T21:02:24.922661+09:00] [GF 7.0.19] [INFO] [NCLS-LOGGING-00009] [com.sun.enterprise.server.logging.LogManagerService] [tid: _ThreadID=1 _ThreadName=main] [levelValue: 800] [[
  Running GlassFish Version: Eclipse GlassFish 7.0.19 (commit: 7a897e5df2919f40b5d2ac281c440f80f96d37dc)]]

In GlassFish 7.0.0-M7 or earlier, this was done in RunLevelControllerThread:

$ cat /opt/glassfish-7.0.0-M7/glassfish7/glassfish/domains/domain1/logs/server.log | grep -1 "Running GlassFish Version"
[2024-06-05T18:28:35.983+0900] [glassfish 7.0] [INFO] [NCLS-LOGGING-00009] [jakarta.enterprise.logging] [tid: _ThreadID=26 _ThreadName=RunLevelControllerThread-1717579393004] [timeMillis: 1717579715983] [levelValue: 800] [[
  Running GlassFish Version: Eclipse GlassFish  7.0.0  (build master-b765-ged63b16 2022-07-10T19:56:16+0000)]]

Impact of Issue

Startup may take more time than GlassFish 7.0.0-M7 or earlier.