Two more temp-tables remain undeleted after each ASYNCHRONOU

Hello!

In .Net form we try to receive data from Appserver using asynchronous request. Everything is OK when server procedure runs on appserver. But when it runs on session handle, after each asynchronous request two more temp-tables remain undeleted.

OE 11.5.1, Windows 10 64 bit  

All temp-tables are explicitly deleted everywhere it needs to. To simplify explanation, in attached rar .net form is replaced by startproc.p procedure. How all stuff works:

- In startproc.p a dynamic temp-table is created and schema is saved in longchar var as XML ;
- startproc.p runs procedure pAsyncProcessor.p persistent to set its internal procedure "Updated_Data" as event-procedure;
- startproc.p calls asynchronous procedure named server-proc.p on AppserverHandle (which is set to SESSION:HANDLE) with input parameter xml schema and output parameter table-handle. At the end of procedure table-handle is deleted using "delete object";
- internal procedure Updated_Data, in pAsyncProcessor.p, receives data as input table-handle parameter and calls internal procedure named "ttData_Updated" in startproc.p (originally it invokes method in .net form) with input parameter table-handle. At the end of procedure table-handle is deleted using "delete object".
- "ttData_Updated" receive data as input table-handle parameter. At the end of procedure table-handle is deleted using "delete object".
- In startproc.p persistent procedure pAsyncProcessor.p is deleted';
- In startproc.p a dynamic temp-table is deleted using "delete object".
- in the end, startproc.p runs loop-tt.p to check for existing dynamic temp-tables, which shows two undeleted temp-tables, created by server-proc.p.

Attached RAR contains above mentioned procedures plus three log files, created using LOG-MANAGER:LOG-ENTRY-TYPES set to "DynObjects.DB":
- ClientOnAppserver.log - contains client part, when running on Appserver - OK;
- Appserver.log - contains server part, when running on Appserver - OK;
- ClientOnSession.log - contains full log, when running on SESSION:HANDLE - NOT ok.

According to OpenEdge Documentation -  "Running asynchronous requests on the SESSION system handle....still allows you to use the RUN...ASYNCHRONOUS statement to program local and remote requests in a similar way..."

P.S. Attach file button in post editor opens Insert/Edit media dialog, so I'll attach RAR as media.

[View:/cfs-file/__key/communityserver-discussions-components-files/19/2364.demo.rar:32:32]