[GLASSFISH-15437] [UB]Cannot start DAS when custom container has a class called Domain Created: 04/Jan/11  Updated: 15/Mar/13

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 4.0
Fix Version/s: 4.0

Type: Bug Priority: Major
Reporter: chukmunnlee Assignee: Paul Davies
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Ubuntu 10.04,
java version "1.6.0_23"
Java(TM) SE Runtime Environment (build 1.6.0_23-b05)
Java HotSpot(TM) Server VM (build 19.0-b09, mixed mode)

Tags: 3_1-exclude, 3_1-next, 3_1_1-scrubbed, 3_1_2-exclude


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 ]

Jerome: Should this be documented?

Comment by Nazrul [ 10/Jan/11 ]

Excluding from 3.1 list.

Comment from Jerome:
Looks like folks should not use any of our [GlassFish] configuration names or should use a @configured(name="myspecialname") annotations to disambiguate.

Comment by scatari [ 11/Jun/11 ]

To be considered in the next release.

Comment by Tom Mueller [ 24/Dec/12 ]

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 ]

Changed fix version to 4.0 so this issue gets picked up by OSE 4.0 release queries.

Generated at Wed Nov 25 09:43:59 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.