Issues fixed in OpenEdge 12.8.5
- Last Updated: January 27, 2025
- 1 minute read
- OpenEdge
- Version 12.8
- Documentation
Released on January 27, 2025.
Click here for a list of known issues (release notes).
The following table lists issues fixed in this release:
| Component | Issue Number | Description |
|---|---|---|
| ABLTOOLS | OCTA-70538 |
The introduction of the OE.Core.File and OE.Core.Folder classes were intended to provide a more consistent experience with managing the FILE-INFO system handle, but could unintentionally overwrite the last reference used by ABL business logic. One such example is through use of the ABL Logger framework. The solution is to automatically detect then save and restore existing references whenever these classes must utilize the FILE-INFO handle. |
| ABLTOOLS / PASOE | OCTA-72190 |
Since 12.8 the internal ABL code which provides requests statistics to the OEJMX utility and OEMANAGER REST API attempts to return a list of all requests instead of being capped at the last 1000 requests as it was in prior releases. This can lead to the Tomcat process crashing if it runs out of memory when building the request metrics. |
| ADE | OCTA-60474 |
Error occured while opening a AppBuilder file, containing a browse widget with DB fields from the second connected DB. |
| ADE | OCTA-71643 |
When a browse widget contains a field from a temp table, the .w file is opened with the error “Field was not found in table. Aborting opening of file” |
| DataServers | OCTA-70751 |
Windows 32-bit ABL DataServer Oracle client experience hangs while attempting to execute a join table query in client-server mode. |
| DataServers | OCTA-70221 |
Invalid Oracle statement generated for 4GL reposition dynamic queries under 12.8.x, when actual query is ordered by ASC but reposition query is ordered by DESC. This was resulting in application failure. |
| DB | OCTA-71292 |
Limbo 2phase commit transaction of non-coordinator database is missing the coordinator nickname when viewed via promon. |
| DB | OCTA-68736 |
Index corruption may occur during record creation or update if an index key entry is at the maximum key size and the last component of that key entry is an empty string. |
| DB | OCTA-68933 |
Replication agent note application on target database fails with error 15706 |
| DB | OCTA-68093 |
Database intermittently does not allow more connections to the database after a self-service connection was terminated or crashed while it was holding login semaphore. |
| Docker | OCTA-66922 |
Unable to create SAX Reader due to missing libnsl in OE docker images. |
| Install | OCTA-69085 |
WebClient is installed in Program files and WebClient Application manager (prowcam) is getting created in Appdata folder. When customer is trying to access WebClient Application manager through another user, getting path not found error since other user cannot access AppData folder of different user. Till version 11, the WebClient Application manager used to be in Program files folder but for 12.8.2, it's part of AppData folder. |
| Install | OCTA-60986 |
OpenEdge Installer is attempting to update permissions of nonexistent file- /progress/dlc/install/oesec/liboeadvsec.so in Linux environment. |
| Install | OCTA-71198 |
12.8.4 install changes file permissions from user settings. |
| Lang | OCTA-68915 |
READ-JSON fails to parse a JSON string where a temp-table record contains no fields, i.e. “{ }”. This indicates that the fields in the record contain their initial value, with the exception of child fields in a NESTED DATA-RELATION. This can happen during WRITE-JSON when fields are marked SERIALIZE-HIDDEN, fields are children of a NESTED DATA-RELATION that specifies FOREIGN-KEY-HIDDEN, or when omit-initial-values is specified as an argument to WRITE-JSON.. |
| Lang | OCTA-67766 |
Client may crash when running a query against an OpenEdge database and server-side join, if the child table has a CAN-FIND and the parent table has a FIND trigger that executes a record retrieval statement. |
| Lang | OCTA-69213 |
Calling the CONNECTED method while connected to PASOE can cause a memory leak if the connection is lost. |
| Lang | OCTA-70027 |
A color setting in the Colors section of the Registry on Windows is ignored if the setting's value is a color name instead of an RGB value. All subsequent color settings in the Colors section will also be ignored even if they use RGB values. |
| Lang | OCTA-72366 |
AGGREGATE statement does not provide correct results with client/server when used with -defaultscrolling parameter |
| Lang | OCTA-70145 |
Passing a property as an output parameter to a procedure/function/method call inside the setter block for that property causes recursion, leading to stack exhaustion and a STOP condition. |
| Lang | OCTA-70393 |
WRITE-JSON with a JsonObject target type issues Error “Json Parser Error at offset xxx: parse error: invalid object key (must be a string). (16068)” when the Dataset definition contains parent-id-relations with parent-fields-before/parent-fields-after. |
| Lang | OCTA-70489 |
Session might crash when running request using the OE HttpClient, if the session is started with -pls. |
| Lang | OCTA-71614 |
When two dynamic datasets share the same dynamic temp-table and one dataset is deleted using DELETE OBJECT, and the other dataset is emptied, the AVM process will crash.This will not occur if you set the AUTO-DELETE attribute of the dynamic buffer of the deleted dataset. |
| Lang | OCTA-70615 |
When reading XML or JSON into a dataset where the temp-table records are nested inside of themselves, the nested elements are skipped over (ignored) by READ-XML and READ-JSON |
| Lang | OCTA-69234 |
When a parent class defines a global buffer and a child class that inherits from the parent defines the same buffer locally in a method, when the method is called, the session will crash. |
| Lang | OCTA-69401 |
Report Engine fails with error “Database server did not understand the Report Builder's request” when the Report Engine package is added to a 64-bit OpenEdge installation. |
| Lang | OCTA-69437 |
The PASOE agent crashes when executing the DELETE() method of a SELECTION-LIST widget. |
| Lang | OCTA-67297 |
There is an issue when generating XMLs from a ProDataset which contains temp-tables bound to and filled in a called procedure. In this case, the XML-NODE-NAME/SERIALIZE-NAME values are not preserved when the called procedure completes. |
| Lang | OCTA-71592 |
The _progres client may hang or crash if the terminal is closed while the client is connecting to a database. |
| Lang | OCTA-70144 |
The Get method on a type derived from System.Array is not recognized by the compiler. |
| Lang / PDSOE | OCTA-69679 |
Forms containing user controls with properties defined as rowid or recid do not properly load into Visual Designer. The user control cannot be added to the Visual Designer toolbox. |
| OEM | OCTA-60400 |
OpenEdge management is giving memory usage alerts for memory usage above 100% |
| PASOE | OCTA-67655 |
Client HTTP Sessions with State = READY and Session State RESERVED stay more than 15 seconds. |
| PASOE | OCTA-72296 |
ABL session may randomly crash when executing CANCEL-REQUESTS() method when connected to a PASOE server using HTTPS. |
| PASOE | OCTA-68215 |
Since applying the 12.2.14 update, when calling the stop agent action in the oemanager rest api, the waitToFinish option is no longer respected. Getting the below error:Wrong number of bytes read by ub_read(). (8122) Alternately (more often) seeing fewer records returned in a temp-table parameter to the client than were returned from the AppServer. With no error. |
| PASOE | OCTA-69751 |
In previous releases when PASOE is configured for oauth2 it supports only a single audience for validation of oauth2 tokens.This change allows specifying a comma-separated list of valid audiences for the oauth2.resSvc.audience property in oeablSecurity.properties. |
| PASOE | OCTA-67251 |
An unnecessary restriction on WebApp names restricted use of the _ character |
| PASOE | OCTA-69404 |
Cannot pass access_token as a URL query parameter in OpenEdge 12.8 |
| PDSOE | OCTA-71663 |
Assemblies are not available when importing project in PDSOE |
| PDSOE | OCTA-57091 |
Indentation (Ctrl+I) is not working for the function definitions within the class. |
| PDSOE | OCTA-57083 |
Variable INT64 getting lower cased on selecting Expand Keyword option(Ctrl + shift + 1) |
| PDSOE | OCTA-28556 |
The Expand keywords (Ctrl+Shift+1) modifies “Type=” to “type=”, which results in the form failing to load in the visual designer. |
| PDSOE | OCTA-57125 |
Indentation (Ctrl+I) in PDS is working for FIELDS but not with FIELD. |
| PDSOE | OCTA-57090 |
Indentation (Ctrl+I) in Progress Developer Studio is not working for the OTHERWISE block. |
| PDSOE | OCTA-61881 |
Autocompletion do not have correct cursor positioning for Enum class references. If a class is selected from the autocompletion list, the cursor is positioned in the middle of the class reference, not at the end. Autocompletion also fails to find Enum class members, so they are not presented in the selection list. |
| SQL | OCTA-60439 |
OpenEdge SQL Server results in crash, if the database start-up parameters are configured in a way that one OpenEdge SQL Server should serve more than 124 number of connections. |