Server Monitoring service Interfering with engines

This happened on a Sunday morning at 5:30 AM where no one was working or on the system at all.

Even, no one is working at that time, if any schedulers or automated processes may run at that time. But mostly process Analytics engine shut down occurs due to heavy load or improper logic from Appian point of view.

Yet, it may also cause if any other applications are running on the on that same machine where Appian server is running.

Like server monitoring application?

Not like server monitoring application. Any other application in the system parallel to Appian web server.

Even if it sends information back to the company monitoring it using through the same port as the Appian application uses?

This kind of behavior may because of process execution load over a larger number of CPUs. Processes are distributed across all available execution engines (so long as they have not reached the MAX_EXEC_ENGINE_LOAD threshold). Sub-processes start on the same engine as their parent.

You can add a pair of analytics and process execution engines to your existing configuration by simply listing the engine names in your topology file. Topology file found at <APPIAN_HOME>/conf/appian-topology.xml

Add an execution engine by listing the following definition after the <engine name="process-execution2"/> attribute of the <server> element.

<engine name="process-execution#"/>

Thank you for providing answers for my question. I think you are focusing more on the engine failing than what I was trying to find out. Then engine failed because something interrupted it from outside of Appian.

I was trying to see if other people have had a similar thing happen with their installations of Appian and a server monitoring tool, NOT troubleshoot why it failed or what to do to the Appian installation.

I already did an in depth look at what caused this to happen on the server, and nothing with the Appian installation or the released applications caused the engine to stop running. There is not much released to it yet and there isn't even a total number of 30 people logging into it on a weekly basis yet.

Thank you for providing answers for my question. I think you are focusing more on the engine failing than what I was trying to find out. Then engine failed because something interrupted it from outside of Appian.

I was trying to see if other people have had a similar thing happen with their installations of Appian and a server monitoring tool, NOT troubleshoot why it failed or what to do to the Appian installation.

I already did an in depth look at what caused this to happen on the server, and nothing with the Appian installation or the released applications caused the engine to stop running. There is not much released to it yet and there isn't even a total number of 30 people logging into it on a weekly basis yet.

Hi Jared,

Why cannot you raise a support ticket for this, May be Appian Team can give you more info on this.
Any Port interruption is happend? Just a guess..