There is a PostStartup service in jms-core which is causing this to be activated early...
Yes, jms core has a PostStartup class for the lazy initialization. Can you elaborate what is the matter of jms PostStartup service? Does it break any feature in GlassFish?
We want as much lazy initialization as possible to avoid any impact on footprint.
Regarding to JMS module, the PostStartup service is necessary to start HTTP service for tunneling inbound jms requests to the backend MQ server and the MQ server was already lazily started in EMBEDDED mode, except eager startup in LOCAL mode according to the design of GlassFish JMS service.