Running the same code sometimes causes the error below and other times is fine. This seemed to start happening since upgrading from 10.1C01 to 10.2A. When I look in the appserver logs for the process that matches the protrace file all looks well and then an abnormal shutdown is written in the broker log.
Any ideas would be greatfully received.
broker log
[10/11/02@12:14:45.177+0100] P-002848 T-S-0077 3 UB Basic got PROCSTATS msg=
[10/11/02@12:14:47.599+0100] P-002848 T-L-3092 3 UB Basic Recieved connection:: (8125)
[10/11/02@12:14:47.661+0100] P-002848 T-C-0002 2 UB Basic ConnectionID= 10.128.156.67::DMLIVE::3092::a0d2cc6ad798ddde:-781c800:12be6b6ae80:-1bb7. (8096)
[10/11/02@12:14:47.724+0100] P-002848 T-C-0002 2 UB Basic Client connected : . (8533)
[10/11/02@12:14:47.755+0100] P-002848 T-C-0002 3 UB Basic The ASK major version was missing in the CONNECT request (com.progress.ubroker.util.ubMsg$TlvFieldNotFoundException: TlvAccessException). AppServer Keepalive protocol is disabled for this connection. (13767)
[10/11/02@12:14:47.771+0100] P-002848 T-C-0002 3 UB Basic The client C-0002 has disconnected from the broker. (8084)
[10/11/02@12:14:47.771+0100] P-002848 T-C-0002 2 UB Basic Client disconnected : . (8534)
[10/11/02@12:14:51.177+0100] P-002848 T-S-0075 3 UB Basic got PROCSTATS msg=
[10/11/02@12:14:56.770+0100] P-002848 T-S-0076 3 UB Basic got PROCSTATS msg=
[10/11/02@12:14:57.192+0100] P-002848 T-S-0077 3 UB Basic got PROCSTATS msg=
[10/11/02@12:15:00.192+0100] P-002848 T-S-0075 3 UB Basic got PROCSTATS msg=
[10/11/02@12:15:05.817+0100] P-002848 T-S-0076 3 UB Basic got PROCSTATS msg=
[10/11/02@12:15:09.208+0100] P-002848 T-S-0077 3 UB Basic got PROCSTATS msg=
[10/11/02@12:15:09.223+0100] P-002848 T-S-0075 3 UB Basic got PROCSTATS msg=
[10/11/02@12:15:16.848+0100] P-002848 T-S-0077 3 UB Basic got PROCSTATS msg=
[10/11/02@12:15:18.864+0100] P-002848 T-fileWatchdog 3 UB Basic Posted EUbrokerLogFileNameChanged for broker: DMLIVE (D:\Apps\OpenEdge102aWRK\DMLIVE.server.014241.log)
[10/11/02@12:15:19.848+0100] P-002848 T-S-0075 3 UB Basic got PROCSTATS msg=
[10/11/02@12:15:20.973+0100] P-002848 T-S-0076 1 UB ---------- Posted EAbnormalShutdownServerEvent for PID: 4812
[10/11/02@12:15:20.973+0100] P-002848 T-S-0076 3 UB Basic Ending serverPool thread: S-0076. (8077)
protrace 4812
=====================================================
PROGRESS stack trace as of Tue Nov 02 14:09:01 2010
=====================================================
Startup parameters:
-pf D:\Apps\OpenEdge102A\startup.pf,-cpinternal ISO8859-15,-cpstream ISO8859-15,-cpcoll Basic,-cpcase Basic,-d dmy,-numsep 44,-numdec 46,(end .pf),-logginglevel 2,-logfile D:\Apps\OpenEdge102AWRK\DMLIVE.server.000001.log,-ubpid 6392,-Ms 1,-logname DMLIVE,-logentrytypes ASPlumbing,DB.Connects,-logthreshold 500000,-numlogfiles 3,-ASID 6,-ubpropfile D:\Apps\OpenEdge102A\properties\ubroker.properties,-svrefresh,-ipver IPv4
Exception code: C0000005 ACCESS_VIOLATION
Fault address: 7C832819 01:00031819 C:\WINDOWS\system32\ntdll.dll
Registers:
EAX:00150140
EBX:00150000
ECX:00000000
EDX:00000000
ESI:00150138
EDI:001501E0
CS:EIP:001B:7C832819
SS:ESP:0023:0012F064 EBP:0012F070
DS:0023 ES:0023 FS:003B GS:0000
Flags:00010246
Call Stack:
Address Frame Logical addr Module
7C832819 0012F070 0001:00031819 C:\WINDOWS\system32\ntdll.dll
7C82FFA2 0012F158 0001:0002EFA2 C:\WINDOWS\system32\ntdll.dll
7C8321D3 0012F16C 0001:000311D3 C:\WINDOWS\system32\ntdll.dll
7C8321E3 0012F17C 0001:000311E3 C:\WINDOWS\system32\ntdll.dll
77E6C765 0012F1B8 0001:0002B765 C:\WINDOWS\system32\kernel32.dll
78154B75 0012F1E4 0001:00023B75 C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0DE06ACD\MSVCR80.dll
78154FC1 0012F284 0001:00023FC1 C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0DE06ACD\MSVCR80.dll
** ABL Stack Trace **
--> build-menu app-broker.p (app-broker.r) at line 5580
** Persistent procedures/Classes **
Handle File Name
000000 ssy-plngbroker.r
001401 com/duty/terminology.r
001401 com/duty/systemBroker.r
001401 com/duty/objectCommon.r
001400 com/duty/collector.r
001400 com/duty/objectCommon.r
000000 com/duty/objectCommon.r (STATIC)
001397 sm-broker.r
001396 lng-broker.r
001398 app-broker.r
//=====================================================
PROGRESS stack trace as of Tue Nov 02 14:09:02 2010
//=====================================================
Exception code: C0000005 ACCESS_VIOLATION
Fault address: 7C832819 01:00031819 C:\WINDOWS\system32\ntdll.dll
Registers:
EAX:00150140
EBX:00150000
ECX:00000000
EDX:00000000
ESI:00150138
EDI:001501E0
CS:EIP:001B:7C832819
SS:ESP:0023:0012F064 EBP:0012F070
DS:0023 ES:0023 FS:003B GS:0000
Flags:00010246
Call Stack:
Address Frame Logical addr Module
7C832819 0012F070 0001:00031819 C:\WINDOWS\system32\ntdll.dll
7C82FFA2 0012F158 0001:0002EFA2 C:\WINDOWS\system32\ntdll.dll
7C8321D3 0012F16C 0001:000311D3 C:\WINDOWS\system32\ntdll.dll
7C8321E3 0012F17C 0001:000311E3 C:\WINDOWS\system32\ntdll.dll
77E6C765 0012F1B8 0001:0002B765 C:\WINDOWS\system32\kernel32.dll
78154B75 0012F1E4 0001:00023B75 C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0DE06ACD\MSVCR80.dll
We had quite a few occurrences of the ACCESS_VIOLATION errors when we upgraded to 10.2A as well. Most of ours appeared to be related to PROCESS EVENTS.
Hi, how did you resolve it? We patched to 10.2A03 but still get it.
Kind Regards
Jason Donaldson
Tel 01904 727190
We were able to remove the references that seemed most likely in the path. We rarely had steps to duplicate issues our customers were reporting but we had a general idea and once the PROCESS EVENTS were removed the occurrences of ACCESS_VIOLATIONS dropped dramatically.
The lines of code being run in both live and test both refer to running a new persistent procedure:
run value(ssy-puserbrwconfig.p) persistent set v-userbrwconfig-hdl no-error.
run VALUE(LC("ssy-pbuildmenu.p")) persistent set v-buildmenu-hdl no-error.
Both environments are OS level Windows Server 2003 R1 Openedge 10.2A03.