With the start of the school year, we've been seeing repeated CPU Hog
abends on our proxy server. So I built a new proxy server and now it's
doing the same thing. Extending the cpu hog timeout from 1 minute to 30
minutes just delays the abends. No other software except BM proxy is
running on these boxes.

The first proxy server is a NW6 SP3 with BM 3.7 running just Proxy,
version 3.71.25.

The second proxy server is a NW6.5 SP2 with BM 3.8 running just Proxy,
version 4.02.12.

What should I try next?

Here are some sample sections of the abend logs:

[BM 3.7 on NW 6]

Server PROXY halted Friday, September 9, 2005 1:57:24.878 am
Abend 1 on P00: Server-5.60.03-1937: CPU Hog Detected by Timer

Registers:
CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 0010 SS = 0010
EAX = FCE1721B EBX = 1214B584 ECX = 00000000 EDX = D0FA1603
ESI = 1124F684 EDI = 1214B584 EBP = CED54F0C ESP = CED54EC0
EIP = 00000000 FLAGS = 00200082


Running process: Server 10 Process
Thread Owned by NLM: SERVER.NLM
Stack pointer: CED54F80
OS Stack limit: CED4D040
Scheduling priority: 67371008
Wait state: 50500F0 Waiting for work
Stack: --FCE1721B ?
BBB1B125 (PROXY.NLM|RestartRequests+5)
--65747962 ?
BBB1D5BA (PROXY.NLM|oc_readHeaders+1DA)
--1214B584 ?
--000000A8 ?
--BAA486EC ?
--000000A8 ?
--00000000 ?
--11235004 ?
-BBBBEF28 (PROXY.NLM|ViaHeaderString+0)
--11235004 ?
--00000007 ?
BBAE705C (PROXY.NLM|MergeNewAndExistingHeaders+2C)
--1214B584 ?
--CED54F08 ?
--CED54F0C ?
--CED54F10 ?
--BAA486EC ?
--BAA48644 ?
--0000002A ?
BBB1BDB1 (PROXY.NLM|oc_writeStatusLine+21)
--1214B500 ?
--11235004 ?
-BBBBEF28 (PROXY.NLM|ViaHeaderString+0)
--000012BF ?
--00000007 ?
BBAE68F7 (PROXY.NLM|ProcessReplyBody+2B7)
--11235004 ?
--00000001 ?
--001AEDCA ?
--11235004 ?
--11235004 ?
BBB076CA (PROXY.NLM|ProcessHTTPReplyHeaders+6A)
--11235004 ?
--001AEDCA ?
--D0F49ACA ?
--D0F499BE ?
BBAE60FE (PROXY.NLM|ClientReplyHandler+EE)
--11235004 ?
--D0F499BA ?
--11235004 ?
--BBC9CE80 ?
BBB3B7F0 (PROXY.NLM|CallrsCallBacks+0)
BBB3B844 (PROXY.NLM|CallrsCallBacks+54)
--11235004 ?
0071EBF9 (SERVER.NLM|StartWorkToDo+23)
--11235004 ?
--001AEDCA ?
--BBC9CE80 ?
--00000000 ?
--00000000 ?
0060EE3A (SERVER.NLM|WorkerThread+4DA)
--11235004 ?
--00000000 ?
--CEDAE2E0 ?
--00000000 ?
--CEDAE2E0 ?
0061AB18 (SERVER.NLM|TcoNewSystemThreadEntryPoint+3C)
--CEDAE2E0 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--65657246 ?
--65657246 ?
--65657246 ?
--65657246 ?
--65657246 ?
--65657246 ?
--CED4D000 ?
--65657246 ?
--65657246 ?
--65657246 ?
--65657246 ?
--65657246 ?
--65657246 ?
--65657246 ?
--65657246 ?
--65657246 ?

Stack dump exceeded the valid memory limit

Additional Information:
The NetWare OS detected a problem with the system while executing a
process owned by SERVER.NLM. It may be the source of the problem or
there may have been a memory corruption.



**********************************************

[BM 3.8 on NW 6.5]

Server ZIDON halted Friday, September 9, 2005 5:23:37.268 am
Abend 1 on P00: Server-5.70.02-1937: CPU Hog Detected by Timer

Registers:
CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 0010 SS = 0010
EAX = FCE17BBC EBX = 0002F49C ECX = 00000005 EDX = B3039232
ESI = B3039236 EDI = 0A7BD488 EBP = 05BD5004 ESP = B46B4E58
EIP = 00000000 FLAGS = 00000046


Running process: Server 11 Process
Thread Owned by NLM: SERVER.NLM
Stack pointer: B46B4F80
OS Stack limit: B46AD040
Scheduling priority: 67371008
Wait state: 50500F0 Waiting for work
Stack: --FCE17BBC ?
0035EE9C (SERVER.NLM|CCmpD+10)
--0A3C2794 ?
--00000000 ?
8521B400 (PROXY.NLM|oc_requestStart+130)
--B3039232 ?
--0A7BD484 ?
--00000006 ?
0010F449 (LOADER.NLM|GetRealModeMemoryLogicalAddress+1C5F)
--00000000 ?
-001437E0 (LOADER.NLM|activeScreen+4184)
--00000000 ?
--398DADE0 ?
0010EDA7 (LOADER.NLM|GetRealModeMemoryLogicalAddress+15BD)
--00000010 ?
--00000010 ?
806274FE (LSAPI.NLM|LSEnumProviders+425)
--00000006 ?
--00000018 ?
--8572EE74 ?
--0A3C2794 ?
--0A3C2780 ?
--B46B4F0C ?
--0A3C2794 ?
--080D90D4 ?
--0A3C2794 ?
85218DD6 (PROXY.NLM|RestartRequests+66)
--05BD5004 ?
--646F4D2D ?
8521B22A (PROXY.NLM|oc_readHeaders+1DA)
--0A3C2794 ?
--000000A8 ?
--85D93BEC ?
--000000A8 ?
--00000000 ?
--0A6A8004 ?
-84974148 (PROXY.NLM|ViaHeaderString+0)
--0A6A8004 ?
--00000007 ?
851E2A9C (PROXY.NLM|MergeNewAndExistingHeaders+2C)
--0A3C2794 ?
--B46B4F08 ?
--B46B4F0C ?
--B46B4F10 ?
--85D93BEC ?
--85D93B44 ?
--0000002A ?
85219A21 (PROXY.NLM|oc_writeStatusLine+21)
--0A3C2700 ?
--0A6A8004 ?
-84974148 (PROXY.NLM|ViaHeaderString+0)
--000001B1 ?
--00000007 ?
851E2334 (PROXY.NLM|ProcessReplyBody+2D4)
--0A6A8004 ?
--00000001 ?
0010FE6E (LOADER.NLM|LoaderTimerInterrupt+150)
--0A6A8004 ?
--0A6A8004 ?
852044CA (PROXY.NLM|ProcessHTTPReplyHeaders+6A)
--0A6A8004 ?
0010FE6E (LOADER.NLM|LoaderTimerInterrupt+150)
--B301F82D ?
--B301F71E ?
851E1B1E (PROXY.NLM|ClientReplyHandler+EE)
--0A6A8004 ?
--B301F71A ?
--0A6A8004 ?
--85304400 ?
8523ABA0 (PROXY.NLM|CallrsCallBacks+0)
8523ABF4 (PROXY.NLM|CallrsCallBacks+54)
--0A6A8004 ?
0035D0C9 (SERVER.NLM|StartWorkToDo+23)
--0A6A8004 ?
0010FE6E (LOADER.NLM|LoaderTimerInterrupt+150)
--85304400 ?
--00000000 ?
--00000000 ?
0021F69A (SERVER.NLM|WorkerThread+4DA)
--0A6A8004 ?
--00000000 ?
--B45DA120 ?
--00000000 ?
--B45DA120 ?
0022C194 (SERVER.NLM|TcoNewSystemThreadEntryPoint+3C)
--B45DA120 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--02740209 ?
--458B07EB ?
--0940C614 ?
--5DEC8903 ?
--C35B5E5F ?
--55575653 ?
--EC81E589 ?
--34343434 ?
--8B14458B ?
00252840 (SERVER.NLM|UpdateVMInfoCol11+66C)

Additional Information:
The NetWare OS detected a problem with the system while executing a
process owned by SERVER.NLM. It may be the source of the problem or
there may have been a memory corruption.