We're experiencing a lot of of JVM Timeout error messages (like "JVM Process has not received any CPU time for 11 seconds Extending timeouts.") in our console.log file. During this time OTM becomes unresponsive but usually does recover. These appear to happen at random but more often than not on days with heavy volume. We also have lots of memory related errors (OutOfMemory, swapDisk, and Page faults during GC) and we do know that we are running up against the limits of memory management under windows. But I don't see a direct correlation between the memory related errors and the JVM timeout errors.
My question is can we enable an additional level of logging that will help us determine what is happening inside the JVM at the time that a timeout error occurs?
I started running the EQ/TX thread diagnostics to see if I can match up the timeouts with a specific thread or event but so far haven't been lucky enough to have a timeout occur while thread diags are running.
Thanks,
Alan
My question is can we enable an additional level of logging that will help us determine what is happening inside the JVM at the time that a timeout error occurs?
I started running the EQ/TX thread diagnostics to see if I can match up the timeouts with a specific thread or event but so far haven't been lucky enough to have a timeout occur while thread diags are running.
Thanks,
Alan
Comment