That is a known bug, documented in http://community.jboss.org/wiki/WhydoIgetasocketconnectionerrorwhenusingremoteJBossAS and the solution presented on that document is to use a cron job as the root user to fix the file when it gets broken.
+That is a known bug, documented in https://developer.jboss.org/docs/DOC-16380, and the solution presented on that document is to use a cron job as the root user to fix the file when it gets broken.
First, create the correct version of /etc/hosts and save it somewhere, such as /etc/hosts.fixed, and populate it with the following contents (replace myhost with the hostname of your computer, as reported by the hostname command, and the correct IP assignment, as reported by ipconfig):
GlassFish 6.x and remote deployment
-The GlassFish 6.x container doesn't have any remote deployers yet, as GlassFish 6.0 lacks JSR-88 support and it is unclear whether this will be included in a future release.
-Until then, please follow the remote deployment instructions for GlassFish 6.x.
-Remote deployment to recent Payara versions
-Recent versions of Payara might have issues getting deployables uploaded via JSR-88, resulting in errors such as:
-Distributing failed: Action failed Deploying application to target server failed; File not found-
If you encounter such errors, please follow the remote deployment instructions for recent Payara versions.
+The GlassFish 6.x container doesn't have any remote deployers yet, as GlassFish 6.0 lacks JSR-88 support and it is unclear whether this will be included in a future release. Until then, please follow the remote deployment instructions for GlassFish 6.x.
+Recent versions of Payara might have issues getting deployables uploaded via JSR-88, resulting in errors such as:
+Distributing failed: Action failed Deploying application to target server failed; File not found
If you encounter such errors, please follow the remote deployment instructions for recent Payara versions.
+The GlassFish 3.x, GlassFish 4.x, GlassFish 5.x and Payara remote containers use the JSR-88 API. For the connection to succeed, the following JARs need to be in the container classpath or in the current Java Thread's context classloader: