According to the documentation, the service should restart on power failures or application crashes (client-server utilities, databases, etc.) automatically.

I've occasionally run into situations where my application will crash due to running out of memory for the JVM. In this instance, the service doesn't appear to restart or, if it does, I'm running into the previous issue I reported where it isn't clearing out the log information (even after adding -Xrs to the executable).

Should it be detecting this situation?

Could you, please, export settings of your service and send us for investigation.

I'm still having issues with this feature, I think. I have Java running as a service and the application running as a service. After this has been running for a couple of days, we appear to run out of java memory. It appears that the stdout isn't recording anything now either, even though this is specified in my service information and had been recording. It updates the timestamp of the file but isn't recording the output of the application running anymore?

Is the only way around this to schedule a stop and restart of the service?

I'm still having issues with this feature, I think. I have Java running as a service and the application running as a service. After this has been running for a couple of days, we appear to run out of java memory. It appears that the stdout isn't recording anything now either, even though this is specified in my service information and had been recording. It updates the timestamp of the file but isn't recording the output of the application running anymore?

Is the only way around this to schedule a stop and restart of the service?

In order to get the stdout to begin logging again, I had to delete the file so that it got recreated after restarting the service. Is this a known issue?

Is anyone from support around?

We deeply apologize for delay with reply.

Our developers are currently investigating the problem you described. Please, let us know the size of "stdout" file.