From: glassfish-dev-bounces@xxxxxxxxxxx <glassfish-dev-bounces@xxxxxxxxxxx> on behalf of Scott Marlow <smarlow@xxxxxxxxxx> Sent: Thursday, June 11, 2020 8:13:18 PM To: glassfish developer discussions <glassfish-dev@xxxxxxxxxxx> Subject: Re: [glassfish-dev] GlassFish status
Hi,
Do you have any idea what it could be? I race condition would be unlikely, since it keeps failing on the same node if repeated. So maybe it's something related to the node, but I'm not sure.
Would port in use errors show in the console? Or do we need to start Glassfish with the --verbose option to see errors like that?
We encountered the same issue with jakartaee-tck platform run too yesterday in couple of the nodes. But it went through in all other >30 nodes.
+ /root/ri/glassfish6/glassfish/bin/asadmin --user admin --passwordfile /root/admin-password.txt start-domain Picked up JAVA_TOOL_OPTIONS: -Xmx6G Waiting for domain1 to start ........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................ No response from the Domain Administration Server (domain1) after 600 seconds. The command is either taking too long to complete or the server has failed. Please see the server log files for command status. Please start with the --verbose option in order to see early messages. Command start-domain failed.
There was a stop-domain failure in glassfish CI some time back which was fixed by correcting the docker image.
Regards,
Alwin
On 11/06/20 10:52 pm, arjan tijms wrote:
Hi,
I just noticed an old issue with the CI has resurfaced.
Seemingly randomly, GlassFish will fail to start up:
12:11:19 ===== TEST RUN - STARTING GLASSFISH AND DB =====
12:21:20 Waiting for domain1 to start .......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
12:21:20 No response from the Domain Administration Server (domain1) after 600 seconds.
12:21:20 The command is either taking too long to complete or the server has failed.
12:21:20 Please see the server log files for command status.
12:21:20 Please start with the --verbose option in order to see early messages.
Repeating the script (within the same test run) never helps. This is automatically done during the test. However the exact same build does start up on other nodes.