Hi,
Sorry for bad English
I have installed wps6.1.2.1 in cluster on virtual machines (8Gb memory, 4intel-3GGz) with Win2003EEx64
Today after stress (high CPU) has been released the NodeAgent will incorrectly
restart server on the node.
In this time current CPU usage 82%. In operation system logs no error
Has anyone encountered, and solved, something similar? Please tell the reason
Thanks!

In systemout.log exist next string:
13:04:38:127 NOVST] 00000010 ApplicationMo W DCSV0004W: Stack DCS DefaultCoreGroup,at Member
nolesCell01\nolesNode01\nodeagent: Did not receive adequate CPU Stack DefaultCoreGroup time slice.
Last known CPU usage time at 12:58:40:756 NOVST.Inactivity duration was 163 seconds.
13:04:38:158 NOVST] 0000465c CoordinatorCo W HMGR0152W: CPU Starvation detected
13:04:38:236 NOVST] 00004662 DiscoveryServ W DCSV1115W: Стек DCS DefaultCoreGroup...

In file native_stderr.log in this time:






















Unhandled exception
Type=Segmentation error vmState=0x00000000
Windows_ExceptionCode=c0000005 J9Generic_Signal=00000004 ExceptionAddress=0000000077EF6296 ContextFlags=0010001f
Handler1=0000000010030300 Handler2=000000001110AB80
RDI=FFFFFFFF0000FFFF RSI=00000000004D0080 RAX=EAF2501002E30004 RBX=0000000000002D00
RCX=000000005AEBD010 RDX=0000000000000004 R8=000000005AEBFE40 R9=0000000053EB07B0
R10=000000005AEBFE50 R11=0000000000000067 R12=0000000077EC0000 R13=00000000004E1420
R14=0000000000000000 R15=00000000004D0880
RIP=0000000077EF6296 RSP=000000004283F500 RBP=0000000000008000
XMM0 000000000000027f (f: 639.000000, d: 3.157079e-321)
XMM1 0000000000000000 (f: 0.000000, d: 0.000000e+000)
XMM2 0000000000000000 (f: 0.000000, d: 0.000000e+000)
XMM3 0000000000000000 (f: 0.000000, d: 0.000000e+000)
XMM4 0000000000000000 (f: 0.000000, d: 0.000000e+000)
XMM5 0000000000000000 (f: 0.000000, d: 0.000000e+000)
XMM6 0000000000000000 (f: 0.000000, d: 0.000000e+000)
XMM7 0000000000000000 (f: 0.000000, d: 0.000000e+000)
XMM8 0000000000000000 (f: 0.000000, d: 0.000000e+000)
XMM9 0000000000000000 (f: 0.000000, d: 0.000000e+000)
XMM10 0000000000000000 (f: 0.000000, d: 0.000000e+000)
XMM11 0000000000000000 (f: 0.000000, d: 0.000000e+000)
XMM12 0000000000000000 (f: 0.000000, d: 0.000000e+000)
XMM13 0000000000000000 (f: 0.000000, d: 0.000000e+000)
XMM14 0000000000000000 (f: 0.000000, d: 0.000000e+000)
XMM15 0000000000000000 (f: 0.000000, d: 0.000000e+000)
Module=C:\WINDOWS\system32\ntdll.dll
Module_base_address=0000000077EC0000 Offset_in_DLL=0000000000036296
Target=2_30_20080809_21892_LEdSMr (Windows Server 2003 5.2 build 3790 Service Pack 2)
CPU=amd64 (4 logical CPUs) (0x1eff42000 RAM)
JVMDUMP006I Processing Dump Event "gpf", detail "" - Please Wait.
JVMDUMP007I JVM Requesting System Dump using 'c:\IBM\WPS61\profiles\N1\core.20090930.125958.281 6.0001.dmp'
JVMDUMP010I System Dump written to c:\IBM\WPS61\profiles\N1\core.20090930.125958.2816 .0001.dmp
JVMDUMP007I JVM Requesting Snap Dump using 'c:\IBM\WPS61\profiles\N1\Snap.20090930.125958.281 6.0002.trc'
JVMDUMP010I Snap Dump written to c:\IBM\WPS61\profiles\N1\Snap.20090930.125958.2816 .0002.trc
JVMDUMP007I JVM Requesting Java Dump using 'c:\IBM\WPS61\profiles\N1\javacore.20090930.125958 .2816.0003.txt'
JVMDUMP012E Error in Java Dump: c:\IBM\WPS61\profiles\N1\javacore.20090930.125958. 2816.0003.txt
JVMDUMP013I Processed Dump Event "gpf", detail "".