Troubleshooting: The TEXTML Server crashed and the CMS Application Server cannot be restarted
In some cases, if the TEXTML Server crashes while the Web Author is in use, the CMS Application Server component cannot be restarted properly.
- Stop the CMS Application Server:
On Windows: Click the Start button and select. On Linux: Enter the following command:
/sbin/service glassfish.cmsappserver stop
- Try to rename the %glassfish%\domains\cmsappserver\logs\CMSAppServer.log
If you cannot rename the file, then the process is still running and must be killed manually.
The solution is to kill the process. Unfortunately, determining which process to kill is not straightforward.
- Download and install Windows Sysinternals Suite (available at http://technet.microsoft.com/en-ca/sysinternals/bb842062.aspx).
- Double-click the procexp.exe program in the Sysinternals Suite.
- From the Process Explorer menu, select .
- In the Process Explorer search window, enter the name of the log file (i.e.,
CMSAppServer.log) and click Search.
The java.exe process to kill is displayed in the window.
- In the Process Explorer window, right-click the process and select Kill Process.
- Enter the following
ps -ef | grep glassfishThis will return the process that is running the GlassFish service.
- Enter the following command to kill the
Where <process_number> is the GlassFish process.
You can then restart the Web Author components as described in Restarting the Web Author components.