I started configuring my GlassFish server and got interrupted. When I came back to finish the configuration, there must have been something that I missed or mixed up because the server would not restart at all the next time I tried to start it.
How do I undo bad configuration settings for GlassFish?
Check the error logs for GlassFish after you attempt to restart it. If you installed the NetBeans IDE with GlassFish, your log files are located in this directory:
Find the error or errors that identify which configuration settings do not work, and then edit the domain.xml file for the server. Your domain.xml file is located in the following directory:
Netbeans crashed today while I was deploying, and left my domain.xml completely corrupted. Luckily, a few tweaks to a copy of my cow-orker's domain.xml got me running again, but it got me to thinking that it's a good practice to keep a copy of the domain.xml in one's glassfish in case this happens again.
Resolving Errors During GlassFish Configuration
I started configuring my GlassFish server and got interrupted. When I came back to finish the configuration, there must have been something that I missed or mixed up because the server would not restart at all the next time I tried to start it.
How do I undo bad configuration settings for GlassFish?
Check error logs, then edit domain.xml file
Check the error logs for GlassFish after you attempt to restart it. If you installed the NetBeans IDE with GlassFish, your log files are located in this directory:
<NetBeans dir>/<glassfish dir>/domains/domain1/logs
Find the error or errors that identify which configuration settings do not work, and then edit the domain.xml file for the server. Your domain.xml file is located in the following directory:
<NetBeans dir>/<glassfish dir>/domains/domain1/config
Remove the configuration setting from the domain.xml file, then restart GlassFish and configure the server settings again.
Corrupted NetBeans domain.xml file
Netbeans crashed today while I was deploying, and left my domain.xml completely corrupted. Luckily, a few tweaks to a copy of my cow-orker's domain.xml got me running again, but it got me to thinking that it's a good practice to keep a copy of the domain.xml in one's glassfish in case this happens again.