Protrace from using .NET regex class in Webspeed

Posted by christian.bryan@capita.co.uk on 07-Mar-2017 12:25

[View:/cfs-file/__key/communityserver-discussions-components-files/19/JSON_5F00_Validate_5F00_BarCode.p:320:240]

HI All 

We have a webspeed app that uses the .NET regex class and causes intermittent protrace errors and crashes the webspeed agent.

It also seems to coincide with other com object issues with excel and msxml 6.0.

I have attached the source code and an example protrace file.

The issues is in LIVE production environment with OE 11.3.3 and SQL Server dataserver.

Protrace >>>>>>>>>>>>>>>>>>>>>>>>>>>>>

=====================================================
PROGRESS stack trace as of Wed Sep 14 15:27:15 2016
=====================================================

Progress OpenEdge Release 11.3 build 1461 SP03 on WINNT

Startup parameters:
-pf C:\Progress\OpenEdge\startup.pf,-cpinternal ISO8859-1,-cpstream ISO8859-1,-cpcoll Basic,-cpcase Basic,-d dmy,-numsep 44,-numdec 46,(end .pf),-web,-logginglevel 2,-logfile C:\OpenEdge\WRK\OPENAccess-Live.server.log,-ubpid 12172,-wtbhostname 10.71.4.176,-wtbport 61897,-wtaminport 3202,-wtamaxport 3502,-wtbname OPENAccess-Live,-wtainstance 7,-ubpropfile C:\Progress\OpenEdge\properties\ubroker.properties,-logname OPENAccess-Live,-logthreshold 0,-numlogfiles 3,-logentrytypes DB.Connects,-ipver IPv4,-pf \\SDSDC02\OPENAssets\Params\Live\webstartup.pf,-db \\SDSDC02\OPENAssets\Code\live\SH\ihsh,-RO,-trig trig,-db oa_live,-ld ih,-dt MSS,-Dsrv PRGRS_NATIVE_LOCKWAIT,50,skip_schema_check,qt_cache_size,50000,prgrs_prepcache,500,-db \\SDSDC02\OPENAssets\Code\live\SH\faultlogssh,-RO,-trig trig,-db oa_live_faultlogs,-ld faultlogs,-dt MSS,-Dsrv PRGRS_NATIVE_LOCKWAIT,50,skip_schema_check,qt_cache_size,50000,prgrs_prepcache,500,-assemblies \\SDSDC02\OPENAssets\Code\live\ihlive\assemblies,-preloadCLR,-d dmy,-yy 1950,-rand 2,-s 500,-D 500,-IOEverywhere 1,-noincrwarn,-Bt 4000,-tmpbsize 8,-mmax 40000,-Mm 350,-dslog C:\OpenEdge\WRK\Logs\Live\datasrv.lg,-T C:\OpenEdge\WRK,-rereadnolock,-q,-cpinternal UTF-8,-cpstream UTF-8,(end .pf),-p webstartup.p,-weblogerror

Exception code: E0434352
Fault address: 77114878 01:00013878 C:\Windows\SYSTEM32\KERNELBASE.dll

Registers:
EAX:00B9DE20
EBX:00000005
ECX:00000005
EDX:00000000
ESI:00B9DEE4
EDI:00000001
CS:EIP:0023:77114878
SS:ESP:002B:00B9DE20 EBP:00B9DE7C
DS:002B ES:002B FS:0053 GS:002B
Flags:00200212


Debugging dll: C:\Progress\OpenEdge\bin\DBGHELP.DLL
Symbol Path:
C:\Progress\OpenEdge\bin;C:\Progress\OpenEdge\pdbfiles


Call Stack:
Address Frame
77114878 00B9DE7C RaiseException+48
6CC206F2 00B9DF18 GetCLRFunction+1AF3D
6CE337FF 00B9DF4C CreateHistoryReader+15204
6CE48F82 00B9DFDC CreateHistoryReader+2A987
6E23B8BD 00B9DFEC 0001:0000A8BD C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
6E2476E4 00B9E71C 0001:000166E4 C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
6E23825E 00B9E79C 0001:0000725E C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
6E238453 00B9E7B4 0001:00007453 C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
6E2384C4 00B9E7D0 0001:000074C4 C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
6E23C3BC 00B9E808 0001:0000B3BC C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
6E23C819 00B9E880 0001:0000B819 C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
6E23BEE4 00B9E978 0001:0000AEE4 C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
6E2311B7 00B9E99C 0001:000001B7 C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
6CC6479F 00B9E9F0 CoUninitializeEE+14093
6CC65A43 00B9EA30 CoUninitializeEE+15337
6CC65A88 00B9EA9C CoUninitializeEE+1537C
6CC653AA 00B9EE54 CoUninitializeEE+14C9E
6CC6567F 00B9EF38 CoUninitializeEE+14F73
6CC666E6 00B9EFB8 CoUninitializeEE+15FDA
6CC4EB4D 00B9F030 DllCanUnloadNowInternal+91D
6CB81851 00B9F060 0001:00000851 C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
6CC4EB9E 00B9F088 DllCanUnloadNowInternal+96E
04139739 00B9F1A4 0000:00000000
0068C186 00B9F1B4 Progress::ClrBridge::ITypeManager::ITypeManager+26
00278F38 00B9F254 dbut_utclex+1B27D8


** ABL Stack Trace **

--> pr-Validate json_validate_longitude.p at line 7736 (\\SDSDC02\OPENAssets\Code\Live\Updates\json_validate_longitude.r)
json_validate_longitude.p at line 7724 (\\SDSDC02\OPENAssets\Code\Live\Updates\json_validate_longitude.r)
run-web-object web/objects/stateaware.p at line 3806 (C:\Progress\OpenEdge\tty\web\objects\stateaware.r)
run-web-object web/objects/web-util.p at line 4212 (C:\Progress\OpenEdge\tty\web\objects\web-util.r)
SYSTEM-TRIGGER web/objects/web-disp.p at line 653 (C:\Progress\OpenEdge\tty\web\objects\web-disp.r)
web/objects/web-disp.p at line 721 (C:\Progress\OpenEdge\tty\web\objects\web-disp.r)
webstartup.p at line 705 (\\SDSDC02\OPENAssets\Code\Live\ihlive\OHWEB\wwwcos\webstartup.r)

** Persistent procedures/Classes **

Handle File Name
045664 \\SDSDC02\OPENAssets\Code\Live\Updates\json_validate_longitude.r
013416 \\SDSDC02\OPENAssets\Code\Live\ihlive\LoggerActive.r
000000 \\SDSDC02\OPENAssets\Code\Live\ihlive\LogManager.r (STATIC)
013408 \\SDSDC02\OPENAssets\Code\Live\ihlive\libRepairs.r
001260 \\SDSDC02\OPENAssets\Code\Live\ihlive\libgen.r
001229 \\SDSDC02\OPENAssets\Code\Live\Updates\sds_joballoc_manager.r
001034 C:\Progress\OpenEdge\tty\web2\admweb.r
001033 C:\Progress\OpenEdge\tty\web2\wbdata.r
001032 C:\Progress\OpenEdge\tty\web2\webrep.r
001030 C:\Progress\OpenEdge\tty\adm2\queryext.r
001029 C:\Progress\OpenEdge\tty\adm2\query.r
001026 C:\Progress\OpenEdge\tty\adm2\dataquery.r
001022 C:\Progress\OpenEdge\tty\adm2\smart.r
001019 C:\Progress\OpenEdge\tty\web\support\webmsg.r
001018 C:\Progress\OpenEdge\tty\web\support\tagrun.r
001017 C:\Progress\OpenEdge\tty\web\support\webedit.r
001016 C:\Progress\OpenEdge\tty\web\support\weblist.r
001015 C:\Progress\OpenEdge\tty\web\support\webradio.r
001014 C:\Progress\OpenEdge\tty\web\support\webtog.r
001013 C:\Progress\OpenEdge\tty\web\support\webinput.r
001012 C:\Progress\OpenEdge\tty\web\objects\session.r
001011 C:\Progress\OpenEdge\tty\web\objects\web-util.r
001010 C:\Progress\OpenEdge\tty\web\objects\stateaware.r
001009 C:\Progress\OpenEdge\tty\webutil\webstart.r
001008 \\SDSDC02\OPENAssets\Code\Live\ihlive\toolbar.r
001007 \\SDSDC02\OPENAssets\Code\Live\core\stdprocs.r
000000 \\SDSDC02\OPENAssets\Code\Live\ihlive\Consultingwerk\WidgetTypeEnum.r (STATIC)
000000 \\SDSDC02\OPENAssets\Code\Live\ihlive\Consultingwerk\Assertion\HandleAssert.r (STATIC)
000000 \\SDSDC02\OPENAssets\Code\Live\ihlive\SessionHelper.r (STATIC)
001000 \\SDSDC02\OPENAssets\Code\Live\core\stdproc.r

** PROPATH **
.,C:\Progress\OpenEdge\tty,C:\Progress\OpenEdge\tty\adecomm.pl,C:\Progress\OpenEdge\tty\adecomp.pl,C:\Progress\OpenEdge\tty\adeedit.pl,C:\Progress\OpenEdge\tty\adeshar.pl,C:\Progress\OpenEdge\tty\dataadmin.pl,C:\Progress\OpenEdge\tty\prodict.pl,C:\OpenEdge\WRK,\\SDSDC02\OPENAssets\Params\Live,\\SDSDC02\OPENAssets\Code\Live\Custom,\\SDSDC02\OPENAssets\Code\Live\Updates,\\SDSDC02\OPENAssets\Code\Live\ihlive,\\SDSDC02\OPENAssets\Code\Live\core,\\SDSDC02\OPENAssets\Code\Live\ihlive\OHWEB\wwwcos,\\SDSDC02\OPENAssets\Code\Live\ihlive\OHWEB\wwwcoh,\\SDSDC02\OPENAssets\Code\Live\os,\\SDSDC02\OPENAssets\Code\Live\workflow,C:\Progress\OpenEdge,C:\Progress\OpenEdge\bin

** Databases (logical/type/physical) **
ihsh PROGRESS \\SDSDC02\OPENAssets\Code\live\SH\ihsh
ih MSS oa_live
faultlogssh PROGRESS \\SDSDC02\OPENAssets\Code\live\SH\faultlogssh
faultlogs MSS oa_live_faultlogs

** End of Protrace **

Any help appreciated.

Thanks 

Christian.

All Replies

Posted by Garry Hall on 08-Mar-2017 07:29

I might be forum-challenged, but I don't see the protrace attached. If it is an issue with .NET, then such protraces might not yield much, and require more intensive debugging techniques. My recommendation would be to contact Technical Support, as intermittent issues are tough to track down. TS can engage Development to work through the issue if need be.

Posted by Garry Hall on 08-Mar-2017 07:32

Hmm... it seems my browser is forum-challenged, because now I see the protrace. It did not unwind correctly. You will need to get the .pdb files in place to correctly unwind the stack trace. I would still recommend opening a call with Technical Support to assist with this.

This thread is closed