|<< Back to previous view|
[GLASSFISH-15437] [UB]Cannot start DAS when custom container has a class called Domain Created: 04/Jan/11 Updated: 15/Mar/13
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|Tags:||3_1-exclude 3_1_1-scrubbed 3_1-next 3_1_2-exclude|
|Participants:||chukmunnlee, Mike Fitch, Nazrul, Paul Davies, scatari and Tom Mueller|
I'm developing a custom container. It was working fine. I rename one of my class to Domain. I repackaged it. I then copied my container's jar to$GF_HOME/glassfish/modules.
When I tried to start GF, I got
Waiting for DAS to start.......
This goes on for a while then GF says it could not start my domain. Anyway I then renamed the Domain class to something else. Rebuild and recopied the file to modules directory and GF started.
|Comment by Nazrul [ 05/Jan/11 09:22 AM ]|
Jerome: Should this be documented?
|Comment by Nazrul [ 10/Jan/11 02:25 PM ]|
Excluding from 3.1 list.
Comment from Jerome:
|Comment by scatari [ 11/Jun/11 06:40 PM ]|
To be considered in the next release.
|Comment by Tom Mueller [ 24/Dec/12 07:56 PM ]|
Changing this to be a docs bug. The section on extending the configuration of the system should be modified to specify that any new config element must have a unique name, i.e., the name of just the class has to be unique, not just the name including the Java package name.
|Comment by Mike Fitch [ 15/Mar/13 09:23 PM ]|
Changed fix version to 4.0 so this issue gets picked up by OSE 4.0 release queries.