Issues fixed in OpenEdge 12.2.12

Temp-tables are not deleted using Data Object Handler on PASOE

The _file_._catagory field may contain a space as opposed to an empty string as the initial value if the database was converted from OE 10 using either of the OE 11.0 or 11.1 releases.

When restoring to a specific point in time with ai roll-forward the database cannot recover if there are limbo transactions to resolve.

The proquiet enable/disable utility will fail on a database started with -bistall and -bithreshold after the proquiet bithreshold utility was used to increase the threshold when the bi threshold was reached.

Proutil dumpspecified might not dump all the values in the filter criteria when filtering on a non-indexed character field.

Promon option “C. 2PC Coordinator Information” will crash a non-2pc enabled database if when prompted with the the “2phase must be enabled to use this option” error message the user issues an “enter”  followed by a transaction number or a cntrl-C followed by a transaction number .

Online failover transition fails in synchronization test on source db when source db AI seq is at least 65536.

On target replication synchronization failed when online backup started.

Able to failover and failback using replication datasets, however, once I failback, the subsequent failover fails.

Uninstalling 32-bit Progress WebClient application breaks 64-bit Progress WebClient application as it results into un-installing dlls PSCCab, PSCSecReg from 64-bit WebClient.

Progress OpenEdge 12.2.8 Client Networking installation doesn't register the libraries %DLC%\bin\system\pstimer.ocx and %DLC%\bin\prox.dll

When NEWing a class that inherits a class which has been modified (and recompiled) after the NEWed class was compiled, the session crashes if the modified class contains a PROTECTED constructor.

Using  WRITE-FRAGMENT with returned LONGCHAR object created with SAX-WRITER  can cause a large memory leak.

The version of Infragistics Ultra Controls shipped with OpenEdge 12.2.9 was upgraded from 19.2.20192.198 to 19.2.20192.476 but the redirections required to enable r-code built against 19.2.20192.198 to run without recompilation were not included in prowin.exe.config (prowin32.exe.config in 32-bit OpenEdge products).

PASOE session may intermittently throw error “You are trying to use a multi-threaded .NET object in a way that is not supported. The ABL cannot be called on a thread other than the main thread. (15740)” when trying to access a .NET data member or execute a .NET method even though multi-threading is not involved.

PASOE Connection procedure executes a second time from a single connection attempt from the ABL code, when the first call raises an error.

Memptr is being vacated too soon when used as input parameter.

If there is code in an internal procedure called by a database trigger that does RETURN ERROR , the RETURN-VALUE that is set will be cleared, incorrectly, before the trigger returns.  So that RETURN-VALUE will not be seen by the code that caused the trigger to fire.

Error “Cycle in procedure calls detected in <procedure> while executing WRITE trigger for <table>. (2868)” may lead to record corruption if trigger is running within the scope of a sub-transaction.

Client may leak a small amount of memory each time it connects to a Web service.

ABL/WEB Client is sending data from previous request if network was disrupted for previous request that was sending a MEMPTR to the server

A client connection to a remote OpenEdge database with many triggers is slower in OE12 when compared to OE11.

Security vulnerabilities have been identified in Apache Xerces C++ 3.1.1, a third-party component which is included in OpenEdge.

Stop agent button is missing from Classic AppServer resource view in OpenEdge Management console

The pasman utility with pasoestart option on Windows platform doesn&#39;t return the correct exit error code when the script fails because the PAS for OpenEdge instance in question is already running.

Terminating an ABL Session in a PASOE agent after an asynchronous STOP event has interrupted a SOAP Out request to an external service may cause a thread in the PASOE agent process to crash and generate a protrace when the ABL Session is shut down.

PASOE client session stuck in WRITING state and some times PASOE agent consuming 100% CPU

PASOE application is slower or hangs sometimes when running on AIX platform

If a refresh of the ABL Sessions occur while an ABL Session is busy executing the Session Startup Procedure, then the ABL Session may crash and bring down the database that it is connected to. It may also prevent new requests from being processed for a period of time.

If a PAS for OpenEdge agent thread encounters a SIGABRT signal, it may cause an immediate shutdown of the agent process. One source of a SIGABRT is a networking failure in handling the response from a SOAP Out request. If the PAS for OpenEdge agent is connected to an OpenEdge database via shared memory, this can cause the database to be shutdown.

Failed SSL connection is preventing new SSL connections to the database under Linux

Logback version 1.2.7 and prior versions contain CVE-2021-42550 vulnerability. Logback must be upgraded to resolve CVE-2021-42550 vulnerability