|
From: hhale21 <hh...@ya...> - 2009-08-19 15:40:45
|
Hello, I am using JSW 3.2.3. We are experiencing some odd behaviour of our servers on single CPU/core Windows XP/SP3 (32bit) computers. I am looking for ways to try and troubleshoot this problem. There are 3 different servers running as windows services using the wrapper.exe. On a regular basis 1 or more of these servers is getting jvm hung messages and are being started. This seems only to occur on single core/CPU computers. Have not observed this on multi core CPUs. I have wrapper.debug=true in the conf files. I don't seen anything in the log files other that logging for the application stops completly for 30 secs (default wrapper ping value) before the jvm is restarted. I tried starting one of the servers using the wrapper.exe as regular process (as opposed to a service). The hang does not occur however one of the threads in the application is using almost 100% of the CPU constantly. I am using Process Explorer inspect the process. JVM has not occurred when not run as service. When I run the server without the wrapper.exe, I don't have the thread that uses 100% of the CPU and so far the server has run with out any issues. Just looking for some feedback on how to troubleshoot this problem. Thanks -- View this message in context: http://www.nabble.com/jvm-hung-and-high-CPU-usage-with-wrapper-tp25046592p25046592.html Sent from the Java Service Wrapper mailing list archive at Nabble.com. |