Bug Report: Port startup domain detection broken since 6.2024.1 #6783
Labels
Status: Accepted
Confirmed defect or accepted improvement to implement, issue has been escalated to Platform Dev
Type: Bug
Label issue as a bug defect
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)
(1 instances of java)
(still 1 instances of java remain)
(http://localhost:4848 is online)
(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)
(1 instances of java)
(http://localhost:4848 is online)
(2 instances of java)
(http://localhost:4848 is online)
(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)
(1 instances of java)
(http://localhost:4848 is online)
(2 instances of java)
(http://localhost:4848 is online)
(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)
Reproducer
In the current version of Payara Community Edition. See the current outcome above as it's the same set of commands
Operating System
Windows 10 Pro
JDK Version
Eclipse Adoptium jdk-21.0.1.12-hotspot
Payara Distribution
Payara Server Full Profile
The text was updated successfully, but these errors were encountered: