Information

Title	Access Violations if CONNECTED() is called with outstanding async request

URL Name	Access-Violations-if-CONNECTED-is-called-with-outstanding-async-request

Article Number	000205705

Environment	Product: OpenEdge Version: 12.4 OS: Windows

Question/Problem Description

Experiencing client crashes in Windows after upgrading to 12.4.

Stack trace from _mproapsv:

rnpopiLabels
rnpopi
rniproc_entry
rninterpret
rnudfunc_Body
rnudfuncOOMethod
rnudfunc_run
rnudfuncOOMethod
fmoo4glRunMethod
fmoo4glGetAttr
rnwdatr
rnwdatrx
fmeval
fmeval
rnexpstmt
rnexec_entry
rninterpret
umeDispatchEvent
wwRunDispatcher
rnHandleExternalEvent
rnHandleDotNetEvent
Progress::ClrBridge::rnProFromClr::HandleUIEvent

Steps to Reproduce

Clarifying Information

Error Message	Exception code: C0000005 ACCESS_VIOLATION Fault address: 00007FFA06B15FCA 01:0000000000024FCA C:\Windows\SYSTEM32\ntdll.dll SERVER <name> has outstanding asynchronous requests. Cannot RUN. (9004)

Defect Number	OCTA-39424

Enhancement Number

Cause

It is not possible to execute synchronous requests if there is an asynchronous request outstanding on the same AppServer.

Attempting to do this will result in error 9004 'SERVER <name> has outstanding asynchronous requests. Cannot RUN. (9004)'.

CONNECTED() is executing like a synchronous request using the same socket connection that is being used for async requests. When attempting this a memory stomp occurs while attempting to read the response.

Resolution

Fixed version(s): OpenEdge 12.5, OpenEdge 12.2.7, OpenEdge 12.4.1

Workaround

Notes

Keyword Phrase

Last Modified Date	10/23/2023 12:08 PM

Access Violations if CONNECTED() is called with outstanding async request

Information