The following table lists issues fixed in this release:

Components Item Details
ABLTOOLS OCTA-29443 HTTPS response contains incomplete content when using the OpenEdge HTTP client, for servers that rely on diconnecting from clients when complete. These servers do not send a Content-Length header or use chunked Transfer-Encoding.
DB OCTA-19345 When loading a .df (containg a very large number of uncommitted db objects and their respective encryption policies from another TDE database, the dictionary load fails in the middle of the process with a popup error as does the database lg file, SYSTEM ERROR: rlbinext: past end of cluster 2368 (3829) is present.
DB OCTA-30385

PROUTIL truncate bi accepts an invalid _-biblocksize_ which it does not convert to a valid biblocksize. The utility uses this invalid biblocksize and then the subsequent open of the database fails because of the following error:

*bkwrite: write to disk failed errno 28. (3645)*

This results in an inaccessible database.

DataServers-ORACLE OCTA-20373 ABL Application fails when CLOB file content is 65535 bytes while using Oracle DataServer.
Install OCTA-23931/ADAS-24053 JavaVersion.ini file not found when trying to Add Components to an existing OE installation on Windows OS platforms. The installation process is unable to continue.
Install OCTA-23966

When installing the ‘OE Workgroup RDBMS', ‘Progress Dev Studio OE'*,* and ‘OE Ultra Controls .NET' as components on Windows platform, OpenEdge Explorer gets installed usually. However, while doing the same scenario through silent installation oemgmt/bin folder is missing and the oem_tailor log not gets created in DLC\\install\\cleanup folder.

Install OCTA-24037/ADAS-24081 OpenEdge Installation fails during Java Validation when the User TEMP directory constructs a space or a special character. User Name having spaces may also result into this problem.
Install OCTA-29355 OpenEdge Explorer tailoring fails on Linux with OpenEdge 12.2.1/12.2.2 updates when installing Enterprise RDBMS and PASOE Dev products.
Lang OCTA-20976 Garbage collection is not occurring for objects passed to the Event Procedure as part of an asynchronous request.
Lang OCTA-21469 A program that access the _Sequence table will not work properly if you generate the r-code while connected to an OpenEdge 11.X database and try to run the r-code while connected to an OpenEdge 12.X database.
Lang OCTA-22540 A dialog box displayed using the .NET ShowDialog method may be hidden behind its parent form if the application becomes non-responsive due to a long-running operation.
Lang OCTA-28276 Having a CAN-FIND inside of a block (or sub-block) with a STOP-AFTER clause may cause the STOP-AFTER to not take affect. Specifically, this will occur if the CAN-FIND contains a WHERE clause that causes some ABL code to run, for example a call to a method or a user-defined function.
Lang OCTA-28378 The OpenEdge AVM may become unresponsive when a frame containing a CONTROL-FRAME (with or without a control) is hidden and redisplayed.
Lang OCTA-29156 When using the startup parameter -rereadnolock, a FOR EACH join on a non-default buffer which uses the FIELDS clause causes subsequent uses of that buffer to improperly continue to use the FIELD clause restrictions.
Lang OCTA-29199 The OpenEdge AVM may crash when restoring frames which are hidden when applhelp.p is run in response to the HELP key.
Lang OCTA-29431 Changes to a temp-table's SERIALIZE-NAME are not reflected in WRITE-XML output.
PASOE OCTA-28596/ADAS-22347 Client Sessions get stuck in Request State "Reading" and even lowering the idle session timeout parameter has no impact on the behavior.
PASOE OCTA-29002 PASOE instance can't be stopped in the production environment with TCMAN STOP command.
PASOE OCTA-29028 Getting error Message: Error on connectRq(): com.progress.appserv.broker.exception.BrokerException$NoAvailableConnectionsException: Agent
PDSOE OCTA-28308 java.util.ConcurrentModificationException when using PDSOE plugin APIs for DB interactions
PDSOE OCTA-30344 The project's actual path is written to the ubpf.config (file name changed to build.config), instead of a relative path. This behavior results in an error when the project is used in a different machine as the actual paths are likely different.
SQL OCTA-22640 SQL: SELECT FETCH returns more records than expected when offset value is more than the range of 32 bit signed integer.