payara
Bug Report: Port startup domain detection broken since 6.2024.1
Brief Summary
Since Payara Community 6.2024.1 on a Windows machine attempting to use stop-domain fails after start-domain has been called for the 2nd time leaving Payara in an undefined state. Payara does not shutdown cleanly using available commands and/or force options. This same scenario has been experienced running Payara as a service on a Windows 2019 Server in pre-production environment. Payara Community 6.2023.12 works normally.
Expected Outcome
This expected outcome is executed out of the box using Payara 6.2023.12 (no additional deployments)
asadmin start-domain domain1 Waiting for domain1 to start ................................ Successfully started the domain : domain1 domain Location: D:\apps\payara\payara-6.2023.12\glassfish\domains\domain1 Log File: D:\apps\payara\payara-6.2023.12\glassfish\domains\domain1\logs\server.log Admin Port: 4848 Command start-domain executed successfully.
(1 instances of java)
asadmin start-domain domain1 Port 7676 is in use Command start-domain failed.
(still 1 instances of java remain) (http://localhost:4848 is online)
asadmin stop-domain domain1 Waiting for the domain to stop . Command stop-domain executed successfully.
(0 instances of java) (http://localhost:4848 is not accessible)
Current Outcome
The current outcome is executed out of the box using Payara 6.2024.6 (no additional deployments)
asadmin start-domain domain1 Waiting for domain1 to start .................................. Successfully started the domain : domain1 domain Location: D:\apps\payara\payara-6.2024.6\glassfish\domains\domain1 Log File: D:\apps\payara\payara-6.2024.6\glassfish\domains\domain1\logs\server.log Admin Port: 4848 Command start-domain executed successfully
(1 instances of java) (http://localhost:4848 is online)
asadmin start-domain domain1 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.
(2 instances of java) (http://localhost:4848 is online)
asadmin stop-domain domain1 CLI306: Warning - The server located at D:\apps\payara\payara-6.2024.6\glassfish\domains\domain1 is not running. No domains are currently running. Command stop-domain failed.
(2 instances of java remain) (http://localhost:4848 is online)
asadmin stop-all-domains Stopping domain domain1 Stopped domain Command stop-all-domains executed successfully.
(2 instances of java remain) (http://localhost:4848 is online)
asadmin stop-all-domains --force Stopping domain domain1 Stopped domain Command stop-all-domains executed successfully. (2 instances of java remain) (http://localhost:4848 is online)
I have now killed the processes in Task Manager.The current outcome is executed out of the box using Payara 6.2024.6 (no additional deployments)
asadmin start-domain domain1 Waiting for domain1 to start .................................. Successfully started the domain : domain1 domain Location: D:\apps\payara\payara-6.2024.6\glassfish\domains\domain1 Log File: D:\apps\payara\payara-6.2024.6\glassfish\domains\domain1\logs\server.log Admin Port: 4848 Command start-domain executed successfully
(1 instances of java) (http://localhost:4848 is online)
asadmin start-domain domain1 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.
(2 instances of java) (http://localhost:4848 is online)
asadmin stop-domain domain1 CLI306: Warning - The server located at D:\apps\payara\payara-6.2024.6\glassfish\domains\domain1 is not running. No domains are currently running. Command stop-domain failed.
(2 instances of java remain) (http://localhost:4848 is online)
asadmin stop-all-domains Stopping domain domain1 Stopped domain Command stop-all-domains executed successfully.
(2 instances of java remain) (http://localhost:4848 is online)
asadmin stop-all-domains --force Stopping domain domain1 Stopped domain Command stop-all-domains executed successfully. (2 instances of java remain) (http://localhost:4848 is online)
I have now killed the processes in Task Manager.
Reproducer
In the current version of Payara Community Edition. See the current outcome above as it's the same set of commands
- Open a Windows Command Prompt
- run - asadmin start-domain domain1
- Browser to localhost port 4848 (accessible)
- run - asadmin start-domain domain1
- Browser to localhost port 4848 (accessible)
- asadmin stop-domain domain1
- Browser to localhost port 4848 (accessible)
- asadmin stop-all-domains
- Browser to localhost port 4848 (accessible)
- asadmin stop-all-domains --force
- Browser to localhost port 4848 (accessible)
- Go to Task Manager, kill 2 instances of java.
Operating System
Windows 10 Pro
JDK Version
Eclipse Adoptium jdk-21.0.1.12-hotspot
Payara Distribution
Payara Server Full Profile
I was able to reproduce the issue and it has been escalated to our Platform Development team with JIRA task FISH-8922. Thank you for the report.
Is there any status/progress on this issue? We are attempting to upgrade to payara 6 (currently using 6.2024.11 but will be trying 6.2025.1 after the necessary approval paperwork) from payara 5 and are experiencing this same problem on RHEL.
To add the notes from the time in between my activities last year (which was limited due to a personal matter) I very briefly looked at the repository to investigate where the origin of the issue might have arisen, or the decisions behind why the regression may have contributed to this experience. General use does give some indicate the start-up processed was overhauled. Only @artur-mal might be able to summarise the original changes a little better 😊.