You might have a JVM log file with more information in case the JVM fails or gives up on TWS for some reason. The file is called? hs_err_pidXXXXX.log with XXXX elaced with the JVM process ID. You will find that file in the "current working directory" where the JVM was running. In many cases that is the Jts installation root folder. But it could be in one of your local folders if you start TWS in a different folder.
You might have quite a lot of those files if your TWS exists frequently.
JR
toggle quoted message
Show quoted text
On Thu, Mar 18, 2021 at 10:44 AM, Stuart Cracraft wrote:
Nothing in the logs.
Not doing anything except letting it run.
I suspect general memory starvation on the instance and will increase its capacity (memory + compute + network) for a tech refresh.
On Mar 18, 2021, at 8:37 AM, mark collins <mark.collins@...> wrote:
Check the logs for errors, because that's not normal behaviour. If there's no errors it could be getting terminated by the os if it's taking a lot of resources, but almost certainly it's something you're doing and not noticing.
Best wishes,
M
On Thu, 18 Mar 2021, 14:27 Stuart Cracraft via groups.io, <smcracraft@...> wrote:
I login, go away, come back and it¡¯s exited.
How do I make it not exit.
All that happens every 30-60 minutes¡
Bizarre.
