Issues fixed in OpenEdge 12.5

*Question / Problem Description*
When timeouts are exceeded during a Web request, a STOP condition is raised in the PASOE session, which bubbles up and is returned as a Http 500 error.  This is incorrect.  Any type of Timeout that occurs should result in a 408 error sent to the client that mentions the exact timeout that expired to cause the event to occur.

For example "Execution timeout was exceeded by the agent...".

*Error Message*
[21/11/24@11:19:07.280-0500] P-019926 T-022908 1 AS-31 -- Unable to invoke 'HandleRequest' method from 'OpenEdge.Web.InternalWebRouter Class' (18198)

The above results in a HTTP 500 error sent back to the client.

ABL Unit fails with error "Test instance is invalid" for certain test procedures.

Temp-tables are not deleted using Data Object Handler on PASOE

No files are extracted from the OpenEdge.ServerAdmin.pl procedure library when using the %DLC%/src/extractpl.bat script.

In the ABL unit test screen, even if there are failed test cases, UI is not recognising failures.  It shows Zero failures and a Green color progress bar (which indicates the whole run is successful).
The test cases are ignored.

When running ABL unit with a very large number of tests (20,000+) , error 14675 (SYSTEM ERROR: Attempt to define too many indexes for area  database “) is raised and the test run fails to complete.

The http client ignores response data when the response has a blank content type and zero content length, but has a chunked transfer encoding.

“Unable to build type info” error is seen when running ABL Unit for a folder that contains both source and r-code.

ABL logging's NamedFileManager doesn't create folders specified in the logging.config configuration.

The HTTP Client returns error “Unsupported object type: OpenEdge.Core.ByteBucket” when creating a new message part with content-type “application/soap+xml” and a ByteBucket object. This error is also seen when creating any XML content types and using a ByteBucket object to hold the XML data.

The ABL HTTP client returns error “Cookie version must be positive” if the Version attribute of the Set-Cookie HTTP header is zero.

The StringEntityWriter attempts to convert memptr inputs to longchar  values using COPY-LOB. This may fail when the data contained is binary  or cannot be convered using the current  codepage.

This issue is to at least  investigate potential solutions for this - which may include  base64-encoding the data or otherwise.

Encode does not encode the + sign to the expected %2B

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)".

When the numeric / date formats in an ascii dump .d file do not match the current session formats, the load session will either abort (numeric format) or load bad data (date formats).

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

Message 4423 does not contain the index number being manipulated which will help identify that an  to unrelated index block(or any other type block) hitting issue with 32/64 bit boundary.

IDXCOMPACT does not compact a global unique index

Since 11.7.6, 12.2, PROSTRCT STATISTICS reports new LOCKCHN metrics without the index names/numbers the chain belongs to.

OpenEdge 12.2.6 remote client access of the sports database has been shown to be on average 8% slower than 11.7.x for very specific read oriented workloads.

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.

If you are running roll forward on a target database in a hot standby environment you may encounter an error where the block update counter is equal to the note update counter preventing roll forward from continuing.

For example:
(1028)  SYSTEM ERROR: Rollforward Apply AI note, BKUPDCTR=41689, note updctr=41689.

Additionally, a subsequent roll forward retry may result in an error suggesting the data extent has been truncated.

For example:
SYSTEM ERROR: Invalid block 2220542 for file /data/db-op/op_20.d1, max is 2220479 (2329)
SYSTEM ERROR: Possible file truncation, 2220542 too big for database. (612)

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.

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.

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

Prolog utility on TDE enabled database requests a passphrase when running it offline. Supplying a -Passphrase gives an error.

Idxactivate does not report duplicate keys when activating an unique index.

After allocating buffers to the alternate buffer pool (-B2), the value  returned in the _actsummary._Summary-DbAccesses field will be incorrect as it does not include accesses to buffers in the alternate buffer pool, only the primary buffer pool.  Note that the other fields in this VST such as _Summary-RecReads (record reads) will report all activity regardless of the buffer pool the table is accessed from.

Prostrct builddb results in warning 18591 when the extent value is more than 32bit.

Aborted prostrct addonline left orphan _Area records in the database. Operation retry failed with error 'must be a directory name or follow the convention. (6857)'

When checking for long-running transactions using _Trans._Trans-Duration  an incorrect value gets displayed, much too high when compared with  the length of time the database is up (_ActSummary._Summary-Uptime).

Both DBAGENT and ABL client may crash with a memory violation when reading the _block VST if the database has an 8k block size.

FOR FIRST or FOR LAST statement generates ORDER BY clause in SQL query even though  PRGRS_ALWAYS_INDEX,0  and startup parameter -noqryorderadd or QUERY_-TUNING(NO-QUERY-ORDER-ADD) is specified for Dataservers

When MS SQL Server database connection parameter  NO COUNT is set  updating a record fails with error “Tried to access a record without a valid id. (6167)”

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.

The Unique property of an index is not checked when pulling a unique, function-based index into a DataServer for Oracle schema holder.

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

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

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

Running the Client Networking MSI reports the following warning “Microsoft Defender SmartScreen prevented an unrecognized app from starting. Running this app might put your PC at risk”

The OpenEdge Client Networking MSI package includes files which aren't needed for application deployment. Unnecessary files include empty databases; build tools such as ANT, PCT, and Gradle; and miscellaneous files including new keyword lists and properties files.

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.

You may get an invalid handle (unknown value) when trying to dynamically access a buffer in a ProDataset defined in a class, if a subclass defines a buffer for the protected temp-table in that ProDataset.

Compiling an OPEN QUERY statement with multiple BY clause options causes the session to crash

Calling SUBSTITUTE() on a LONGCHAR that that has the Unknown value causes the session to crash or generate error 49.

REPLICATION-WRITE trigger is executed when there is no change in database record.

An error condition is not raised, when SET-SIZE fails to allocate the requested memory for a MEMPTR.

In Progress Application Server for OpenEdge, RETURN ERROR from the Connect procedure does not delete the AppError object.

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

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

All ABL statements which support unicode-filenames may fail when the filename is a character constant and cpinternal is UTF-8.

The statements impacted by this issue are:

OUTPUT TO

INPUT FROM OS-DIR(),
INPUT FROM ()
INPUT THROUGH
DEFINE IMAGE ... FILE
OUTPUT THROUGH
DOS
OS-COMMAND
OS-APPEND
OS-COPY
OS-CREATE-DIR
OS-DELETE
OS-RENAME
PROCEDURE ... EXTERNAL  (DLLs)

When the READ-JSON() method fails it reports things like expecting this but found that, but it does not provide any cursor offset, which makes it almost impossible to work with.

Expected Product Behavior:
Enriching error 15358 is already a very high concern now.

Use of DYNAMIC-FUNCTION to invoke an ABL method fails with error message  ‘5639 - User-defined function ‘Function’ invoked dynamically but could  not be found’

Deleting a widget in a trigger on that widget (for example, deleting a button in the trigger for the button’s CHOOSE event) may result in error “UIM Error: Invalid UIC method called. (4044)”.

The RELEASE EXTERNAL statement does not release the external procedure library (DLL or shared library) in the PASOE agent.

Attempting to write to or delete a file after querying its size with the FILE-INFO:FILE-SIZE attribute may fail on Windows. An error may be displayed or the operation may fail silently.

An empty string (““) is returned as the SCREEN-VALUE for a selection-list with no selected items. In previous releases the unknown value was returned as the SCREEN-VALUE for a selection-list with no selected items.

The AVM changes the widget IDs assigned to extent fields which have been given explicit IDs. This can cause conflicts with other IDs and results in error "Widget ID NNN not unique".

String concatenation in the ErrorMessage parameter of the Progress.Lang.AppError(ErrorMessage, MessageNumber) constructor doesn't work as expected when one of the values being concatenated has the unknown value.

The bproxsdto4gl utility crashes when the input XSD file contains table names which are longer than 32 characters.

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

Message 8000 (WARNING: Invalid _Field-Rpos setting nnn for table.field. Setting to nnn) is a warning but it cannot be suppressed by the suppress warnings list.

The AVM hangs on Windows if the result of the EXP function exceeds the limits of the internal floating point value which stores the result.

Using an OUTPUT DATASET-HANDLE or INPUT-OUTPUT DATASET-HANDLE parameter to dynamically pass a dataset which has the SERIALIZE-HIDDEN attribute set doesn't set the SERIALIZE-HIDDEN attribute on the returned dataset.

The Number of Databases startup parameter (-h) allows one less database connection than the value specified by the parameter.

Closing a named stream that is defined with KEEP-MESSAGES in an internal procedure raises the error “ already has a  conflicting use. (99)”.

Error 14629 while creating large XML file using SAX-WRITER

WRITE-XML doesn’t hide SERIALIZE-HIDDEN/XML-NODE-TYPE=”HIDDEN” fields that are part of a PARENT-FIELDS-AFTER phrase of a PARENT-ID-RELATION

Comparing buffer-value with initial of a clob field crashes AVM

SAX-READER Characters callback fails silently when processing XML with  invalid characters; charData, defined as LONGCHAR, returns unknown  (?).

READ-JSON fails to populate key fields when the data-relation uses FOREIGN-KEY-HIDDEN attributes.

When just executing Sax-Writer:WRITE-EMPTY-ELEMENT() with the output destination of LONGCHAR , the LONGCHAR appears to not contain the empty element.  The resulting LONGCHAR just contains the XML prolog.

A sub-procedure FINALLY block whose associated block handles stop conditions via ON STOP UNDO, LEAVE or a CATCH block for stop, can prevent a STOP-AFTER in the caller from stopping processing.

If one PAS session creates a .NET form or control, and then another new session tries to reference any class in .NET, you will misleadingly get the error “Error loading the .NET runtime”.   The real error is: “"You cannot set the exception mode after the application has created its first window."  You should not create .NET forms or controls in a PAS session.

The ABL session may crash when compiling code that accesses a .NET class containing a method or property marked as isFamilyAndAssembly.  This means that only a child class (Family) that is also within the same assembly can access the element.  Those elements should not be accessible from the ABL.

The compiler will stop if "disable triggers for dump of <table> allow-replication" causes an error when compiled instead of continuing to compile to see if there are other errors in the ABL code.

.NET classes that contain any element marked as isFamilyAndAssembly (i.e., they can only be used by other classes in the same package or the same assembly) will make that class unusable in the ABL.  The compiler will incorrectly give error: “Invalid datatype specified:  Specify a datatype such as ‘character’ or the name of a class. (5638)”, when you try to compile code that defines a variable of that type.

Compiling a code base with multi-compile on causes a crash if the root of a class hierarchy is precompiled.

If you are using an assembly (in your assemblies.xml file) that has a dependency on another assembly, and that 2nd assembly cannot be found, you may get “Could not get class or interface xxx (12886)” where xxx is the class you are trying to use from the original assembly.  There will be no indication that the dependent assembly is involved. You will not get this error when the assembly is initially loaded. It will happen later when trying to NEW the class.

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“.

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

If you try to subscribe to an event that is part of an interface, and there have been no previous references to any .NET objects (non-interfaces) before that, the code will not compile.  You will get the error “Could not locate element _psc_Subscribe_NET in class <classname>. (12927).  This only happens from the Procedure Editor, not from PDSOE.

Compile returns (8004) and (201) after field is added.

OE12 R-Code referencing the _file-trig or _field-trig tables and compiled against an OE11 db will not run against an OE12 db; conversely, that same r-code compiled with OE12 against an OE12 db will not run against an OE11 db. Instead it will generate CRC error message number 7968.

Profiler output shows time spent for FOR statement at line 0 instead of actual FOR statement line number .

When using READ-JSON into an empty dataset handle, data will not get loaded if the table is anything but the first table in the JSON file

Starting the OpenEdge Database from OpenEdge Management Console (OEM) after enabling SSL and configuring sslkeyaliaspassword results in an error 'SSL error 12063-SSL Server Unable to load private key...' in the respective Database logs. The Database fails to start from OEM.

The dbagent process will crash if the database it connects to has a very high number of extents.

OpenEdge Explorer (OEE) console login page cannot be restricted accessing it from remote machines even after adding TrustedClients property with 127.0.0.1 and localhost in fathom.properties file. This is to prevent accessing OEE from Internet or Intranet and allow only local server access which is our enterprise business need.

In the OpenEdge Management console, the date-time values displayed against the *Agent Sessions, ABL Application Requests, Client Sessions* pages are not in local time-zone format. For example, the “Session start time” vs “Agent start time” format is not matching.

After initiating a refresh of a PASOE instance by terminating all ABL Sessions using terminateABLSessions, requests may begin to fail with “No sessions available.” followed by “Error handling request\! Status=-1003” messages in the agent log. The agent may then eventually run out of worker threads with the message “Cannot allocate another thread.”

Importing an ABLapplication without the dash character fails when one with a (-) dash is deployed first (vice-versa as well)

Application becomes unresponsive when user tries to 'X' out of a synchronous call to PASOE

4GLTrace always results in some level of overhead to ABL execution. However, when 4GLTrace is enabled for PASOE, higher levels of concurrency (16 or more concurrent requests in a single PASOE agent) can cause contention writing to the agent log file, which can result in a significant slow down in processing requests. This is true whether 4GLTrace is enabled via either agentLogEntryTypes or defrdLogEntryTypes.

4GLTrace always results in some level of overhead to ABL execution. However, when 4GLTrace is enabled for PASOE, higher levels of concurrency (16 or more concurrent requests in a single PASOE agent) can cause contention writing to the agent log file, which can result in a significant slow down in processing requests.

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

“/oepasInstanceLocation/bin/tcman.sh clean -A” command do not archive non default pasoe log file locations

PASOE PROPATH is concatenated with extra text when it is published via deploying Build Automatically

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”.

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

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().

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

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

The default cipher list (below) has been the same between 11.6 and 11.7.current and it includes (ADH*) ciphers, which are NOT supported by OpenSsl.  This has opened customers up to other bugs that are encountering these invalid ciphers in our default supported list when they attempt to add to it using PSC_SSLCCLIENT_CIPHERS.

"AES128-SHA256:AES256-SHA256:DHE-RSA-AES128-SHA256:AES128-GCM-SHA256:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-SHA256:ADH-AES128-SHA256:ADH-AES256-SHA256:ADH-AES128-GCM-SHA256"

Cannot determine whether a StopError was raised from the terminateABLSession JMX query

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

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

The available JMX queries for PAS instances do not support the return of a single ABL session’s metrics, only returning metrics for all ABL sessions of an agent.

The “tcman stop” and “tcman pasoestart -halt” commands do not fully shut down client sessions, leading to connections which may prevent a clean shutdown of PAS agents (notably when bound APSV connections are used).

Soap response ignores dataset serialize-name

PASOE 12.x SOAP web service with namespace with a specific URL can raises an error while same web service under 11.7 runs flawlessly.

PASOE HTTP SSO does not copy Client-Principal properties from the original user login C-P Token when creating the accesstoken returned to a client.

The Option "Organize Using Statement" doesn’t work when it’s used on static classes in concatenated assign statements.

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

Editing a Data Object Service in PDSOE fails with StringIndexOutOfBoundsException

Content assist only works with ENUM's in Developer Studio if r-code has been generated for the class that defines the ENUM.

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

Using Save from an ABL UI Design view fails if the project uses a non-default location for the project directory.

SQL Query containing SSQ (Scalar SubQuery) in SELECT list along with SSQ in OR condition of WHERE clause can result in a Crash or an Internal Error.

Select query with an OR condition such that all parts of the OR go for an index scan shows "record lock" error, even when NOLOCK hint is specified.
Example:
select "cust-num", "order-num", "order-date" from pub.order where ("cust-num" = 53) or ("order-num" = 2) with(nolock);

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.

Single quotes around a rowid value when using a not equal to rowid value in a where condition does not exclude the record having the mentioned rowid

Correlated SSQ query with a relational clause such as BETWEEN or IN leading to an internal error.

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.