Issues fixed in OpenEdge 12.2.7

The Admin service via SOAP which is being utilized by ABL is no longer exists in Corticon 6.0. When a call is made to invoke the deployed service, the user faces the error "Error loading WSDL document (11748)".

IDXCOMPACT does not compact a global unique index

TABANALYS Fragmentation Factor is calculated incorrectly on tables with more than 4.3 billion (2^32) records.

When using the OpenEdge Authentication Gateway, it is possible to see sockets in the CLOSE_WAIT state when the DB Servers or Self Service Clients have not made authentication requests within the last 60 seconds.   These sockets will be properly managed as new authentication requests are made.  If your environment is adverse to having sockets in the CLOSE_WAIT state as has been seen when running particular port scanners, you can set the “-stsSocketReuse no”  parameter when starting the DB Broker.  This will close these socket after each authentication request.

When using OpenEdge 12.2 with a Workgroup license, the first access of a restored online backup may fail the REDO phase with “(10612) SYSTEM ERROR: numlive 1 tx_count 1”  if not restarted with the same startup parameters as the online database that was backed up.

Fixing SQL Width in dbtool in a database with auditing enabled can cause a memory violation

Index rebuild can crash with the error “(10831) SYSTEM ERROR: Record continuation not found” during the database recovery phase of opening the database .  This may or may not prevent truncate bi from completing depending on the extent of possible corruption.

When cusror is re-used for Oracle DataServer, memory leak might occur causing high memory usage followed by error 1450 and crash.

Oracle dataserver crashes when cursor is re-used from LRU cache and it has repeatedly cursor number 0 in dataserv.lg

Query with join fails with ORA-00907 when the database and schema holder has been generated by a push operation where Linguistic sorting has been enabled.

SonicMQ ABL adapter session hangs on send2 in jms/impl/message-header.p

The GUI Procedure editor may display the remainder of a program as comments when displaying or modifying existing block comments.

PASOE ABL sessions occasionally return a “System.IO.FileNotFoundException: Could not load file or assembly” error when using the -assemblies startup parameter.

If an application is using a .NET UI, and execution of the APPLY statement can cause some Windows event to occur (for example, focus change), and asynchronous RUN requests may complete during this time, you can get error  3234, “Mismatched number of parameters pass to routine xxx“.

In the Windows GUI client there may be a delay of several seconds when displaying a combo-box which uses the SORT option in combination with LIST-ITEM-PAIRS.

Progress Application Server for OpenEdge session may crash if its activate procedure invokes a remote procedure call.

An error occurs when assigning a .NET string value with a length of exactly 31,999 bytes to an OpenEdge LONGCHAR variable.  The error does not occur if the string length is greater than 31,999 or less than 31,999

bprowsdldoc and the CONNECT method fail when reading a WSDL file containing ‘ANY’ element type

Under certain circumstances the log file will be filled with repeating messages. When this happens the current log file will grow until the disk is full.

Not all pasoe logs are redirected by setting catalina.logging.folder property in conf/appserver.properties.

PASOE sessions are stuck in the STOPPING state and they will not go away until the instance is shut down.

PASOE multi-session agent session crashes with memory violation (49). protrace contains csMtBindSecondThread in the stack trace.

When ABL request  runs longer then the idleSessionTimeout the ABL session is prematurely terminated when useHttpSession=0.

On Unix systems, the PASOE Agent crashes when an unmanaged thread attempts to call a non-thread-safe C runtime function such as rand(). An unmanaged thread is a thread spawned by third party software which has been initiated by an Application call to a shared object function (in a .dll or .so). Threads running in the PASOE Agent should always call thread-safe versions of the C runtime functions; for example, rand_r() instead of rand().

Access Violations if CONNECTED() is called with an outstanding async request.

After issuing the oejmx query terminateABLSession with option 2 to terminate a PASOE ABL Session (option 2 means: allow current request to complete before terminating), a subsequent request may fail. If this happens, there will be error messages in the agent log file that state: “Could not get and/or initialize session\! Cannot process request.” followed by: “Error handling request\! Status=-1003”.

Experiencing 9407 and 5468 errors periodically while using the new useEnhancedConnected feature in 12.2.7.

When the PASOE instance is shutting down, Java / .Net Open clients which had active connections to it will continue to return TRUE for isConnected() method even after the instance is shut down.

Related temp-tables do not show as nested JSON data in rest call when using WEB transport in PDSOE.

Editing a Data Object Service in PDSOE fails with StringIndexOutOfBoundsException

ShowOkMessageInIDE in  \{adecomm/oeideservice.i} is making PDSOE stay in a ‘wait’ state due to which the project cannot be closed.

Invalid index key created for very long char field on a UTF-8 Database with ICU-UCA collation.

When Auditing and Autonomous Schema Update (ASU) capabilities are enabled together, OE-SQL Server process can result into a crash when automatic update of width is triggered internally.

Client process stop loading ciphers list once it reads a non-supported cipher. And this behavior is random.

The server_name SSL extension is not sent to a web server that uses SNI when the ABL client is communicating via a proxy server.