[GLASSFISH-19098] [PERF] Intermittently cannot start new domain Created: 21/Sep/12 Updated: 20/Dec/16 Resolved: 20/Nov/12
|Reporter:||Scott Oaks||Assignee:||Masoud Kalali|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
About 25% of our tests are failing because we are unable to start a domain immediately after creating it.
We execute these two commands in a script:
The start-domain appears to succeed (it doesn't not produce any error output), but the server is not up. In the server log, it also appears to have started, but then there are exceptions:
[#|2012-09-21T15:34:43.300-0700|INFO|44.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=1;_ThreadName=main;|GlassFish Server Open Source Edition 4.0 (55) startup time : Felix (35,390ms), startup services(6,296ms), total(41,686ms)|#]
[#|2012-09-21T15:34:45.259-0700|INFO|44.0|com.sun.enterprise.config.modularity.ConfigModularityUtils|_ThreadID=1;_ThreadName=main;|The provided path is not valid: server[server]
There must be some race condition here, because if we wait, we can always start the server find (and if we just execute another start-domain command, the server also starts fine). Something that the ConfigModularityUtils needs has not finished being create/installed by the time start-domain returns.
I am attaching the full server.log files (server.log_<timestamp> from the first startup, and server.log from the subsequent startup).
|Comment by Masoud Kalali [ 22/Sep/12 ]|
Scott, it seems to be caused by config modularity. I wil investigate and get back to you soon.
|Comment by Masoud Kalali [ 24/Sep/12 ]|
Can you possibly attach the domain.xml of the test server that causes the failure? that is if you are using a custom domain.xml or you are changing something from the defaults.
|Comment by Masoud Kalali [ 20/Nov/12 ]|