Issues fixed in OpenEdge 12.4

When a response to a request causes a redirect - via a 302/Found status code for example - and the original/first response returns a "Content-Type" header and the redirect response returns chunked data, specified using the "Transfer-Encoding: chunked" header, then the second response does not process the chunked body at all.

HTTPS response contains incomplete content when using the OpenEdge HTTP client, for servers that rely on diconnecting from clients when complete. These servers do not send a Content-Length header or use chunked Transfer-Encoding.

Not enough space for the other things in the buffer used to store the value of the variables because of which data execeding issue occured.

After a failed attempt to run idxactivate on an index, the Dictionary's Quick Index and Detailed Table reports show the index as active.

In the 64-bit Windows  AppBuilder, a dialog box comes up with a warning that viewing procedures in the tree-view is not available.

Display an alert message when the maximum character limit is reached in AppBuilder's section Editor.

incremental .df produced in 12.2.2 adds ACTIVE to index properties

SYSTEM ERROR attempting to close AppBuilder after failing to open a program because error 12370

When an ABL window is created in the AppBuilder and later some of the database field names used in the window are changed, then it is not possible to open the window in the AppBuilder.

The installer now installs ubqmanager folder into the DLC area.
ubqmanager folder and it's contained procedures _6dar399.r, _6deq399.r, _6enq399.r.  These procedures are used to internally keep track of appserver asynchronous requests and if not found, will raise STOP conditions on the appserver at runtime.

Excessive calls to getpid() on AIX causing performance degradation for OE 12.2.4 ( _mprosrv) compared to 11.7.1 (_mprosrv)

When a PROMON -F session is disconnected it takes out a USR latch which it should not. If USR latch is being held by any other client, promon -F will appear hung.

IDXCOMPACT crashes with Block Corruption 1124,
Database must be restored as BI recovery fails during Physical Undo:
(645)   SYSTEM ERROR: bkwrite: bktbl dbk  not equal to bkbuf dbk

Update progress.cfg cause broker to crash on startup

If -keyalias or -keyaliaspasswd is defined in a .pf file, the database will incorrectly parse the parameter values.

dbtool option 3 output has 2 lines merged into 1

PROMON shows BROKER (user 0) information when a user name is used instead of the user number.

PROUTIL truncate bi accepts an invalid _-biblocksize_ which it does not convert to a valid biblocksize.  The utility uses this invalid biblocksize and then the subsequent open of the database fails because of the following error:

*bkwrite: write to disk failed errno 28. (3645)*

This results in an inaccessible database.

When block corruption is encountered, the debug messages and block content are dumped multiple times when releasing the buffer from shared memory. This duplicative information makes reading the .lg file and debugging problems more difficult.

DSRUTIL does not work and make proenv shell to close unexpectedly.

Target db hangs after transition when rprepl -C status -detail is run

Pct in promon Activity: Resource Queues is not correct, needs to be x100

RFUTIL is not displaying the error of corrupted AIfile until the next AI file applied:

Some database parameters may be ignored if multiple instances of "-db" parameter are specified.

"proutil -C dumpspecified mytables.myfileds = 0 mydirectory" do not use  the primary index but another non primary index defined for that  database table

Oracle DataServer client crashing with memory violation, when UNDO is done on stored-procedure having CLOB columns in sub-transaction.

Delta.sql utility generates the wrong SQL statement if the SQL Server database uses native sequences, creating an UPDATE statement instead of an ALTER SEQUENCE statement.

Unable to specify Oracle version 19 or 18 when connecting with OpenEdge 12.2.4 to an Oracle 19c database

Running dynamic/static query using MS SQL dataserver and -cpcoll ICU_48-DUCET does not return the expected record when column is defined using case-sensitive collation like Latin1_General_100_CS_AI.

Dataserver schema holder date field with initial value of TODAY function is putting incorrect date upon creation of the new record.

Progress Runtime crashes with Join-Queries on Oracle Dataserver

ABL Application fails when CLOB file content is 65535 bytes while using Oracle DataServer

The official PASOE Docker image is missing the DLC\ubqmanager directory.

When a STOP condition occurs within a transaction while waiting for messages from the Sonic Adapter, cleanup code that attempts to run deleteSession from a FINALLY block causes the below error to be thrown from deleteMessage in jms/impl/message.p:

Attempt to reference an UNDO GLOOBAL variable after a transaction backout has removed its definition. (9064)

The line of code this occurs on is:
ASSIGN PRGRS-JMS-MESSAGE-COUNT = PRGRS-JMS-MESSAGE-COUNT - 1.

If the cleanup code is not run, this results in memory leaks.

The OpenEdge installer reports it is unable to find libproxml_m.so and libprosoap_m.so during the tailoring phase when OpenEdge Enterprise RDBMS and 4GL Development are installed in silent mode.

JavaVersion.ini file not found when trying to Add Components to an existing OE installation on Windows OS platforms. The installation process is unable to continue.

The FOR EACH statement retrieves the wrong records if a FIND TRIGGER rejects a record using the RETURN ERROR statement.

Progress Application Server for OpenEdge sessions connecting to a remote webservice may crash

Running a query with a malformed CONTAINS string (asterisk in the middle of the string) with server side joins enabled (the default) results in error 778 “reading socket, ret=10054, errno=2”,  followed by the ABL client being disconnected from the database.

When using the startup parameter -rereadnolock, a nested FOR EACH join on a non-default buffer which uses the FIELDS clause causes subsequent uses of that buffer to improperly continue to use the FIELD clause restrictions.

The RUN statement supports the ability to execute remote procedures via the ON \[SERVER] server-handle syntax.   When the server-handle is identified via the execution of ABL code, DYNAMIC-FUNCTION for example, the AVM executes this code twice.

RETURN ERROR in an application server's Startup procedure does not terminate the agent when it is documented that it should.

When compiling a program in a session which is connected to two databases which have the same structure and the program uses RECID or ROWID in WHERE clause, the session crashes with a memory violation (49).

The use of SESSION:CURRENT-REQUEST-INFO as a parameter to a function (for example, VALID-OBJECT (SESSION:CURRENT-REQUEST-INFO) ) causes a memory leak

A compile-time error is generated when defining an indeterminate array with the INITIAL option before calling SUPER() in a constructor.

With Database Client Notification enabled, the client may crash when blocked on acquiring a record lock.

When a class with a temp-table data member which is defined using LIKE phrase is deleted, the AVM session may crash.  This may occur when reuseable objects is enabled (the default).

While running an OS-COMMAND in PAS for OpenEdge, you may get error: "Error running OS-COMMAND status 6 errno 22".

A RPC encoded WebService request fails when a parameter partname is an element type

The UNIQUE-ID value was truncated to 32-bits

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.

The AVM may crash when the MOVE-TO-TOP method is executed on a frame which is displayed in a dialog box.

The AVM sets the codepage on a LONGCHAR variable to the session's default codepage (-cpinternal) when the SUBSTRING statement is used to modify the contents of the LONGCHAR variable.

The OpenEdge AVM crashes if an empty filename (““ or '') is provided as the argument to the -clientlog or -dslog startup parameter.

The AVM crashes or displays error 1987 "Operation number nnn is not supported in this release" if the DCOLOR attribute of a frame is overridden at runtime before the frame is realized.

In 64-bit Window products, AppBuilder does not display a procedure which exceeds the Section Editor's 20,000-byte limit. The same procedure can be viewed in AppBuilder in 32-bit Windows products.

In a PAS for OpenEdge session, executing an OS-COMMAND statement to run an operating system command that creates a file with Unicode characters in its name creates a file with a corrupted name. The filename is created correctly when the same OS-COMMAND statement is executed from an interactive GUI client or a batch client.

When serializing nested JSON with parent-fields-before and parent-fields-after, if there were no child records then the parent-fields-after fields do not get serialized.

Error message 12724 ("DATA-SOURCE may not contain a REFERENCE-ONLY buffer 'name'") is missing the buffer name.

The OpenEdge AVM may crash when restoring frames which are hidden when applhelp.p is run in response to the HELP key.

With READ-JSON and READ-XML in Merge mode the duplicate unique index violation (error 132) is not suppressed when some components of the unique index are missing from the JSON/XML input.

A dialog box displayed using the .NET ShowDialog method may be hidden behind its parent form if the application becomes non-responsive due to a long-running operation.

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

The Find Next and Find Previous commands in the GUI Procedure Editor don't work as they did in earlier versions of OpenEdge. If the editor has to scroll to make the matching line visible the line is shown at the bottom (for Find Next) or top (for Find Previous) of the editor instead of being shown in the center of the editor.

A system error is reported when attempting to run prodict/load_cdc.p against a database with a low -omsize (Storage Object Cache Size) setting.

A literal string more than 32,767 bytes in length is accepted by the ABL compiler but appears as an empty string (zero bytes in length) at runtime.

If a .NET method returns an array of string values whose total length exceeds 32,000 bytes the AVM incorrectly changes the array's type to LONGCHAR. This causes the assignment of the return value to an ABL array to raise error 5729 "Incompatible datatypes found during runtime conversion".

Error 4043 “DITEM is not large enough to hold string” occurs if the length of the RCODE-INFORMATION:TABLE-LIST attribute exceeds 32,000 bytes.

When an r-code file is run explicitly, using either -p <filename>.r or RUN <filename>.r, and the file does not exist, the AVM searches for r-code file twice.

DynObjects client logging may show a discrepancy between the number of bytes allocated and the number of bytes deallocated for a MEMPTR or LONGCHAR in certain SUBSTRING and CODEPAGE-CONVERT operations.

When compiling with XREF-XML, if the file contains a ProDataset with a very long definition, you might encounter an error message “Error in DataSet relations information during XREF-XML”.

In OpenEdge 12.3, the READ-XML method may return an unusual error reading empty data into the Date field:  JSON string is not a valid ISO-DATE. (20015)

READ-XML does not correctly populate the child record of a Data-Relation with the parent record's relation-field value when the parent field is represented as an XML attribute.

HTTPS URLs may give error "Unable to run web object file", classic WebSpeed OpenEdge in 11.7.8 while trying to validate international characters

The SAX-PARSE method has a memory leak in OpenEdge 11 and OpenEdge 12.

Running a window from AppBuilder that executes a QUIT statement exits the entire progress session under certain circumstances.

Message 4065, which indicates that a handle method was given invalid arguments, and other similar messages are treated by the AVM as warnings instead of as errors and cannot be caught by a CATCH block.

If you compile a class on Windows that inherits from a .NET class and try to run the r-code on Unix or Linux, it will crash.

Client (prowin.exe/_progres.exe/_proapsv.exe ) will crash when exiting with error 1077 when not able to reach database server after successfully connecting to the login broker.

If a method on a handle is called within an expression or ASSIGN statement and structured error handling is being used in the block, the error is not handled properly.  The error may not be raised, and therefore the error cannot be caught by a CATCH block.  It is also possible that an error is raised but the left-hand side of the assignment statement is still set, which it should not be.

When making requests to Progress Application Server using the APSV transport and the instance is started with the parameter -ttindexrangesize with a non zero value, every request to the application server spawns an error 132 in the agent log: _AgentRequest already exists with ?. (132)

1. If a STOP condition occurs during a non-void method called within an expression, the expression will erroneously continue to be evaluated and can cause a crash or other unpredictable behavior.  
2. If a STOP condition occurs having to do with OpenEdge-supplied code that is responsible for queueing/dequeueing asynchronous RUN requests/responses, the error message from the STOP condition will be lost.

If the Data Dictionary is used to deactivate the indexes on _aud* tables, the CRC values will be generated, creating a CRC mismatch for any r-code that uses those indexes.

If you edit a form in 12.2.2 the Visual Designer tool will add a line to set the value of SyncToSelectedRow on the BindingSource to TRUE. This is a new property in 12.2.2. Compiling the resulting code in a version earlier than 12.2.2 will result in compiler errors because the new property is not present.

Setting the RunTimeProperties.IdleConnectionTimeout in the .NET Open Client will cause connections to the AppServer to fail with a NullReferenceException.

When proxygen is used to generate a .NET Open Client proxy and the proxy configuration .xpxg has the data table namespace set to blank and the option to "use default namespace" turned off, the proxygen utility will fail without an explanatory error message.

On Unix platforms, files with UTF-8 extended characters in the file name return the Unknown value for FILE-INFO:FILE-MOD-TIME and FILE-INFO:FILE-MOD-DATE.

A static code analysis tool reports that .NET Open Client may fail to properly close a stream object in the ProMessageFormat class.

An unclosed stream in logging functions of .NET Open Client may trigger Unclosed Resource warnings from a static analysis tool.

Invoking ShowDialog for a form within a non-void method which is called from an expression, like RETURN  may cause the session to crash.

The PSCUrlParser class in progress.o4glrt.dll may not remove cleartext information from memory after use.

The HttpClientProtocol class in progress.o4glrt.dll may not remove cleartext information from memory after use.

The SessionPool class in progress.o4glrt.dll may not remove cleartext information from memory after use.

The SessionPool class in progress.o4glrt.dll may not remove cleartext information from memory after use.

Having a CAN-FIND inside of a block (or sub-block) with a STOP-AFTER clause may cause the STOP-AFTER to not take affect.  Specifically, this will occur if the CAN-FIND contains a WHERE clause that causes some ABL code to run, for example a call to a method or a user-defined function.

Error 1750 (Could not read database record for undoing. (1750)) has been replaced by a hard coded message in OpenEdge 11.7 and OpenEdge 12:

Could not read table  for undoing DBKEY  partitionid

Selecting Default Preferences from the main menu in ProxyGen before loading or creating a configuration will result in a NullReferenceException being thrown.

The -checkwidth startup parameter is not calculated correctly with multibyte characters and will erroneously warn about or block data insertion.

Calling :INVOKE() does not raise any error when CLOB/BLOB datatype is  passed as a parameter in the SET-PARAMETER() method. CLOB and BLOB are  not supported data types for the parameters.

The AVM may hang when running an ABL program for a very long time with the ABL Profiler enabled. The amount of time necessary to experience the hang depends on the number of ABL statements executed. If there are over 2 billion statements, it will hang.

When a very long ABL Application runs with the ABL Profiler enabled, the overhead to collect the profiling information may gradually grow. This may cause the Application to take longer to run. For example, a job that ordinarily takes one hour to complete without profiling may take two hours to complete with profiling.

Enabling the profiler may cause the client to crash if r-code for active procedures or classes has been swapped out; certain segments of the r-code may be swapped out if the AVM exhausts the -mmax memory setting.

Running encrypt code from a knowledgebase article appears to have a memory leak when DynObjects logging is turned on, however it is actually a bug in the DynObjects logging.

When the System Wide CPU monitoring option is selected in OpenEdge Management Resource Monitoring Configuration page then the User can’t be able to define system resources like FileSystem, Disk.

Updating an existing remote AdminServer configuration in OpenEdge Management (OEM) console results in printing the password in clear text into the remote AdminServer log file. This happens intermittently. Knowing that this exists, anyone with access to that log file can search it and possibly find OS passwords.

Adding more than 20 Web handlers through the OpenEdge Explorer (OEE) Web Console, only 20 handlers are written to the openedge.properties file. When additional 20+ Web handlers are manually added to \{CATALINA_BASE}\\openedge.properties, updating or adding handlers through the OEE Web Console fails and overwrites the entire properties file. As a consequence the PAS instance no longer starts until the openedge.properties file can be manually restored.

In OpenEdge Management the scheduled jobs run fine. However, OEM fails to retrieve the trend database port due to which the job history under the jobs tab returns an error.

When trying to publish a classic rest application to a Linux server, it results in errors.  Publishing to a remote Windows server works fine. This problem occurs for all the REST services being published to the REST Broker on Linux. The code gets published fine, the below error occurs every time:

A problem occurred while publishing files to the REST broker.
Unknown error occurred while doing publishing application…: null

OE Client-Principal converter automatically appends a comma (,) even if the SAML attribute is a single value.

After configuring a PASOE instance to enable SOAP transport and restarting the instance any attempts to use the service results in a NullPointerException.

When connecting to a database from an ABL Session in a PASOE agent, if the CONNECT statement fails because of a failure to authenticate, then if the ABL Session tries to CONNECT again, it may result in a Memory violation (49). This only happens if connecting to the database using shared memory; it does not happen when connecting using via the network.

In DB shared memory connection record locks are not released when the session is crashed.

Terminate http sessions API does not terminate tomcat sessions

$DLC/servers/pasoe/bin/tcmanager.sh does not search correctly if a port already exist in /etc/services

PAS appserver using OEREALM on other appserver gets session-timeout

\[ERROR] Property not found: AppServer.Agent.someApp.PROPATH

when first deploying webapp having a dash and then webapp without a dash using pasman

ABL client fails to connect to a remote OpenEdge Authentication Gateway enabled database with error - client key not found (16399)

ABLWebAppPackage Ant task produces different WebHandler listings order in the merge.properties file on Windows and Linux.

Unable to generate pidl file without losing existing mapping when we add a new parameter in the resource. There used to be an option to do this in Project Properties->Build->Generate REST Invocation Files, which is no longer available.

Environment variable properties are not evaluated in the Launch Configuration

When Progress Developer Studio for OpenEdge starts with -checkdbe startup  parameter in project properties, it triggers warning 2411.

When closing the property sheet of a widget with the "X" button in the top right-hand corner, in the AppBuilder perspective of PDSOE, this results in an error 293.

Exporting a web application to a .war file in Progress Developer Studio for OpenEdge, containing many source files (1000 files) associated with one or more services, fails to export.

SQL SELECT query with a CASE statement having character constant specified in THEN clause and Date column specified in ELSE clause can cause the _sqlsrv2 process to crash if the character constant’s length is less than 10.

internal error in SQL ENGINE at 4081 in Z:/vobs_sql/sql/src/rds/stat.cxx for join queries involving large and very small table when the column statistics data contain null values

DELETE statement generates SQL server crash if WHERE clause contains the correlated sub-query having correlation defined on rowid and access the last row of the table.  

Query Timeout was not working for cases when query does not have Order By or it results in Index scan.

SQL:  SELECT FETCH returns more records than expected when offset value is more than the range of 32 bit signed integer.

OpenEdge SQL connection to OEAG enabled DB fails with UNLISTED PAM ERROR when the domain type is “_extsso”.

ESB adapter spawns a high number of dispatcher I/O threads in a blocked state and stopped processing messages.