| Re: JVM Timeouts in 5.0 under Windows
Hey Alan!
There's no additional logging that I can recommend, besides ensuring that verbosegc is enabled. While you're not seeing a correlation between memory issues and the timeouts, I'd look a bit deeper into it. One of the issues with Win32 is that the OTM heaps are limited to about 1.5GB. There was a large UK client that we hosted back in the G-Log days and this was one of the main issues they encountered.
When the JVM either runs out of memory (large amounts of garbage collection using up all CPU time) or threads, these timeout issues are encountered. Usually the former is the cause. Oh - I forgot. I've also seen this issue if too much memory is allocated, I've seen the same thing. A 1.5GB JRockit heap can consume 2.5-3GB of total memory, due to JRockit's memory usage for optimization.
Hope this helps!
--Chris |