Issues fixed in OpenEdge 12.2.15
- Last Updated: September 6, 2024
- 1 minute read
- OpenEdge
- Version 12.2
- Documentation
Released on May 29, 2024.
Click here for the list of known issues (release notes).
The following table lists issues fixed in this release:
| Component | Issue Number | Description |
|---|---|---|
| ADE / DataServers | OCTA-56151 |
“For field widths use Width” option in the Data Administration menu “Delta df to MS SQL Server Conversion” does not update DSRVR-PRECISION value correctly for decimal fields. |
| ADE / DataServers | OCTA-57941 |
“For field widths use Width” option in the Data Administration menu “Delta df to Oracle Server Conversion” does not register SQL width changes for decimal fields when a SQL width value is updated on a decimal field. |
| DataServers | OCTA-62042 |
DataServer client on Linux platform crashes on cross platform use case (client (Linux) communicates with server (NT64)), when tried to create a record for the time field. |
| DB | OCTA-55909 |
Target databases log file showing error (-----) Cannot update remote agent agent0/0 with AI seq NNNN because it's not connected. |
| Install | OCTA-60071 |
12.8 installer returns message when trying to install OpenEdge as The installation utility has detected that there is NOT enough disk space to install. |
| Lang | OCTA-60922 |
READ-JSON can fail to load data into a ProDataset if the JSON source contains JSON Arrays with names that do not match temp-table members of the Dataset . |
| Lang | OCTA-61165 |
ABL client can end up in a loop retrying a block that has the ON STOP, RETRY directive, if an outer block has the STOP-AFTER option and it has timed out. |
| Lang | OCTA-61154 |
In user-defined functions and OOABL methods, INPUT-OUTPUT and OUTPUT MEMPTR array parameters that are INDETERMINATE in both the caller and callee are freed when calling functions, such as GET-SIZE, on the indeterminate MEMPTR. |
| Lang | OCTA-49476 |
When an indeterminate array of MEMPTRs is returned from a procedure the size (as shown by GET-SIZE) of the elements of the array is zero. |
| Lang | OCTA-60007 |
An OpenEdge 12.2 ABL client which is connected to a 12.2 (or later) database server may perform worse than an OpenEdge 11.7 ABL client when receiving a larger Temp-Table from a PASOE instance. |
| Lang | OCTA-59155 |
ABL client crashes with error “Error starting a database transaction. The client cannot continue” when trying to connect to a database in client/server mode if using an ABL authentication callback procedure. |
| Lang | OCTA-45366 |
The Dynamic objects logging for MEMPTRs may log different sizes for Allocation and Deallocation lines when working with the Progress.IO.MemoryOutputStream and/or OpenEdge.Core.ByteBucket classes. |
| Lang | OCTA-61124 |
OE 12.X client raises error 7997 when the SEAL method is executed while an OE 11.X database is connected and it has the “Record Authenticated Client Sessions” option enabled. |
| Lang / PASOE | OCTA-60297 |
PASOE Agent stuck in STOPPING state. This is due to an internal memory corruption issue caused by a race condition in the destruction of an ABL Session. This bug should be very rare, but is more likely to occur when the PASOE Agent receives an Administrative “terminateABLSession with option FINISH.” |
| Lang / PASOE | OCTA-58611 |
ABL session may crash after an internal procedure or function in a persistent procedure deletes the procedure itself. |
| PASOE | OCTA-50127 |
When a SOAP request containing the href attribute and the multRref tag is sent to a PASOE SOAP web service, then the following exception is thrown: com.progress.appserv.adapters.camel.soap.CamelSOAPException: Exception unmarshalling a parameter value. |
| PASOE | OCTA-56356 |
JSON arrays are sent empty in the response when the output parameter is mapped as Array Json type. |