Return
-
Title
Stat Central Agent Status shows Not Responding but a Java process is alive on the server. -
Description
Debugging User issues. Bounced the Central agent and apparently did something in err with JAVA. default.war.failed stat-config.war.failed stat-agent.ear.failed
Debugging the issue and discovered that, although the STAT client indicated that the Central Agent was down, there was an active STAT process running on the host server.Therefore there was conflict with the ports. I terminated that backup process, and the startup now has different messages.
Sign In Required
You need to be signed in and under a current maintenance contract to view premium knowledge articles.