keep the Python/TERR/R service engine log if engine crashed

We noticed that if engine crashed when executing Python/TERR/R data functions on server, the engine will produce a hs_err_<pid>.log under engine's log folder.

C:\Windows\Temp\pythonsrv-62047\hs_err_pid15052.log

However, above log together with the folder pythonsrv-62047 could be deleted very soon if other data functions are executing which causes the crashed engine been pruned.

In our cases the log is deleted only several seconds after the creation, so it's difficult to collect this hs_err_pid15052.log for diagnostics.

Support confirmed that this is as designed, we hope this can be improved, at least keep the crash log from being deleted when the engine is pruned.

===

The deletion of the work\pythonsrv-XXXXX folder depends on when the engine shuts down. While it’s possible to extend the engine.prune time (which controls how long an idle session is kept before being cleaned up) to delay this deletion, doing so isn’t recommended in this case.

Right now, the service deletes the session directory as soon as the engine shuts down, which is generic and as designed.

Instead of this, user can have the JVM save crash reports to a different location by adding the following line to custom.properties file and restarting the service:

javaOptions: -XX:ErrorFile=C:/jvm_error_%p_%t.log

===