[GLASSFISH-18635] Early initialization of jms-core module Created: 16/Apr/12  Updated: 19/Sep/14  Resolved: 19/Jun/13

Status: Resolved
Project: glassfish
Component/s: jms
Affects Version/s: None
Fix Version/s: 4.1

Type: Bug Priority: Critical
Reporter: Sanjeeb Sahoo Assignee: David Zhao
Resolution: Works as designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: spo

 Description   

There is a PostStartup service in jms-core which is causing this to be activated early...



 Comments   
Comment by David Zhao [ 16/Apr/12 ]

Hi Sanjeeb,

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?


David Zhao

Comment by Sanjeeb Sahoo [ 16/Apr/12 ]

We want as much lazy initialization as possible to avoid any impact on footprint.

Comment by David Zhao [ 19/Jun/13 ]

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.

Generated at Sun Jul 24 13:47:26 UTC 2016 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.