[GLASSFISH-19140] [regression] Exception not printed when startup service fails Created: 09/Oct/12  Updated: 20/Dec/16  Resolved: 09/Oct/12

Status: Resolved
Project: glassfish
Component/s: other
Affects Version/s: 4.0_dev
Fix Version/s: 4.0_dev

Type: Bug Priority: Major
Reporter: Sanjeeb Sahoo Assignee: Sanjeeb Sahoo
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

This bug has been introduced sometime during HK2 2.x integration. I noticed only this much information:

Startup service failed to start SystemDescriptor(
implementation=com.sun.enterprise.v3.services.impl.GrizzlyService
contracts=

{com.sun.enterprise.v3.services.impl.GrizzlyService,org.glassfish.api.container.RequestDispatcher}

scope=org.glassfish.hk2.runlevel.RunLevel
qualifiers={}
descriptorType=CLASS
metadata=runLevelValue=

{10}

rank=0
loader=org.jvnet.hk2.osgiadapter.OsgiPopulatorPostProcessor$1@d68713
id=397
locatorId=0
identityHashCode=4075103
reified=true) due to A MultiException has 2 exceptions. They are:
1. null
2. Unable to create or inject com.sun.enterprise.v3.services.impl.GrizzlyService

Where is the exception stack trace and root cause information?



 Comments   
Comment by Sanjeeb Sahoo [ 09/Oct/12 ]

svn rev #56350

Generated at Thu Apr 27 09:27:01 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.