Issues fixed in OpenEdge 12.8.12

SaxWriter class fails with longchar

When importing schema from SQL Server DataServer, when a varchar(max) array field is encountered, it throws the below error 10885 that causes crashes when attempting to compile code referencing the field in question.

Admin Server crashes randomly with “The error was triggered by the auth.dll module, which caused the JVM to terminate unexpectedly with the following exception: EXCEPTION_ACCESS_VIOLATION (0xc0000005).”

Using QUERY-TUNING (NO-JOIN-BY-SQLDB) crashes OpenEdge 12.8.8 prowin client when using OpenEdge DataServer for MSS SQL Server

MS SQL dataserver does not refresh the buffer within the same session when using the RECID function and the OE database is migrated with the “Try primary for RowId” option.

Outdated 11.7 executable bundled in the 12.8 install's 117_dbutil directory

WARNING: ESAM Installation failed

--------------------------------------

The ESAM installation has failed. For more details, contact the administrator to review either the ESAM_Install_mm_dd_yyyy_hh_mm_ss.log or the OpenEdge_External_Security_Administration_Manager_Install_mm_dd_yyyy_hh_mm_ss.log. Both files are accessible at the following location: C:\Windows\System32\openedge.d\audit

However, when you click “OK”, the installation continues after the warning.

Visual C++ x64 Redistributable not updated by openedge update install.

OpenEdge Update Installer Does Not Update %DLC%\pdbfiles to Match Updated Binaries

Deselecting the recommended component 'OpenEdge Explorer' during a custom OpenEdge 12.2.16 installation still installs and starts OpenEdge Explorer.

When only PASOE license is installed, during installation installer asks for the internationalization settings, but then in the DLC/startup.pf the settings are not set.

The OpenEdge 12.8.8 Client Networking 32-bit .msi installer installs the prox.dll in the wrong place.  After the installation the prox.dll is located in: “C:\Program Files (x86)\Common Files\Progress Software\11” But not the expected: “C:\Program Files (x86)\Common Files\Progress Software\12”

Progress.Lang.Stop exceptions are not raised when using class property SET accessors combined with a single ASSIGN statement.

PROCESS EVENTS can hang if making asynchronous PASOE requests with -maxConnections parameter, and the number of outstanding asynchronous requests exceeds the -maxConnections value.

Error 683 when running a session compile of a program with a shared frame using -defuntrans startup parameter.

PASOE agent may crash instantiating an OOABL class when using -q startup parameter.

Progress.Util.ResourceManager is unable to locate .resx files if they are located in a directory containing ASCII extended characters in the name of the directory.

Nested constructor calls with string literals will not appear in STRING-XREF output.

Invalid -0 result from ABL AGGREGATE statement when no records satisfy the query.

A memory leak may occur if you set a property with an implementation via a chained expression where the property resides in the object instance that was returned via one of the expressions in the chain expression.

Quotes around command arguments used with OS-COMMAND statement are stripped when executed by PASOE Web Transport

Chained use of Safe Navigation Operator (?:)  throws error 10068 when used on .NET objects.

Application crashes occur when INNER-LINES reference outdated coordinates. This issue may be noticed during a combo-box dropdown action.

When the WASPC library processes a Type attribute in an inline schema, it may trigger error 11748.

When passing a PRODATASET to a class with BY-REFERENCE and in the class the dataset is defined with a named static buffer, this can trigger a session crash in WRITE-XML.

AGGREGATE statement with COUNT operation can sometimes read records even if there is no record selection needed.

The READ-JSON method on a TEMP-TABLE triggers a client crash reading an empty JSON array while inferring schema from the JSON string.

Interactive _progres can continue executing ABL code despite a fatal error message if pending frames needs to be flushed out to the current output device.

Indeterminate arrays with constant initial values are initialized at runtime, when the array definition is encountered.  ABL that accesses a variable before the DEFINE VARIABLE statement will see the variable with an unknown EXTENT, ? .  For example, RUN proc  before DEFINE VARIABLE, where  proc appears after the definition and accesses the indeterminate array.

The bprowsdldoc and CONNECT methods are not accepted when the UsingPolicy element (a component of the WS-Policy WSDL extension) is included within the WSDL.

Client session may crash if you disconnect and reconnect to a PASOE or WebServices server while asynchronous requests are still pending and an asynchronous request has no event procedure defined.

Session may crash during PAUSE statement when running an ABL application with .NET windows if the procedure-complete event of an async request got processed prior to the PAUSE statement.

The OpenEdge Memory Profiler triggers platform memory growth that causes degraded performance after a certain length of time.

OEM/OEE Agent Metrics show date/time values with an incorrect UTC offset.

PASOE agent crashes when SOAP request to a 3rd party provider fails due to SSL errors

Using the ‘-connectionLifetime’ parameter to consume web services results in error 11773.

As part of the camel upgrade, there was a change made to create a direct route on each call to a remote adminserver.  This remote "invocation" is done here.  That function uses getRemoteResponse().  This getRemoteResponse() is used to create a synchronous response.  Unfortunately this getRemoteREsponse() creates a new direct route on every single invocation and never cleans it up.

OpenEdge management is giving CPU and memory usage alerts for usage above 100%

OEE not indicating actual database status.

Client connection to PASOE fails after 60 seconds with TLS 1.3 Protocol.

Error 'sem_timedwait() error: -1 errno: 4' shuts down the admin thread, terminating the agent

Error “The network path was not found” occurs when creating a pasoe instance or deploying webapps to an existing pasoe instance at the root of the drive. For example, using pasman/tcman.bat to create or deploy to C:/oepas1 fails with this error.

Cannot clear PASOE instance log files: check for locked files." when starting a pasoe instance using pasoestart or the OEM webinterface

Client-Principal attributes that contain special characters are not displayed properly.

PASOE logs does not record the reason/origin for ABL session termination

PASOE ABL Sessions randomly crash when calling a HTTPS REST service with the ABL HTTP client.

PASOE agent may crash when handling a .NET exception with a NO-ERROR.

PASSOE does not return details when a MsgFormatException is thrown, losing details on why the exception happened.

SOAP requests are not updating the pasoe Application Metrics 'Max Concurrent Clients:' counter and the related 'PAS Application Concurrent Connected Clients' chart when using OpenEdge 12.2.17 or 12.8.8Under OpenEdge 11.7.22 the pasoe Application Metrics 'Max Concurrent Clients:' counter is being updated when doing SOAP requests

Terminating hung PASOE agent crashed database

The PASOE Agent runs out of ABL Sessions before reaching maxAblSessionsPerAgent.

The PASOE Session Manager process (java) will crash when it receives signal 15 (SIGTERM).

Using the OE Manager REST API oemanager/applications//sessions?sessionID=&terminateOpt=2, the agent is terminating session immediately instead of waiting for the current request to complete.

PASOE ABL Sessions crash with fatal signal 11 when making calls to another PASOE instance via SSL.

When waiting for a record lock in a PASOE Application using a shared memory connection to the database, the STOP-AFTER time-out and Administrative STOP operations are ignored until the lock wait is satisfied.

Run Configuration: Relative paths cause error on Profiler/Performance tabs (Temporary files directory) when working directory is set to “C:\”.

The AppBuilder perspective of the Developer Studio doesn’t generate  trigger code for ABL menu widgets.

When Group by and Where clause contains similar columns then Group by is optimized to use stream aggregation by reusing the selected index for query filter. If there is NULL check in Where clause on a column then incorrect results might be returned due improper copy of the index related information.