Issues fixed in OpenEdge 12.7

OpenEdge.Core.Assert:Equals throw multiple errors when comparing two longchars with different data that are longer than 11000 characters

Business Entity reports only first error message when AppError includes more than one error message

The HTTP client automatically performs redirects based on a response status code. The existing HTTP Response object is reused for the redirect.  If the initial request returns chunked data (ie Transfer-Encoding:chunked header value), and the second request does not, an error 9407 is raised.

The _file_._catagory field may contain a space as opposed to an empty string as the initial value if the database was converted from OE 10 using either of the OE 11.0 or 11.1 releases.

The Client Session Authentication Report is failing due to a field being badly named in the audit extraction program.

When restoring to a specific point in time with ai roll-forward the database cannot recover if there are limbo transactions to resolve.

*Question / Problem Description*
The proutil dbanalysis csoutput for lob data is missing quotes surrounding the field name of the lob.

Proutil dumpspecified might not dump all the values in the filter criteria when filtering on a non-indexed character field.

Promon option “C. 2PC Coordinator Information” will crash a non-2pc enabled database if when prompted with the the “2phase must be enabled to use this option” error message the user issues an “enter”  followed by a transaction number or a cntrl-C followed by a transaction number .

*idxfix* and *idxcheck* will hang accessing menu options online when the database is started with *-omsize* greater than or equal to 200832.

The _ActLock._Lock-RecGetLock VST filed should use the INT64 data type.  Currently it uses an INTEGER data type and this triggers the 15747 error when the Get Locks value is more than 2 Gig.

Database-Request Statement Cache Directory is not available via database start-up parameters and VSTs.

Promon and VST transaction statistics do not report transactions “allocated only” vs transactions “activated”.

applyextent fails on files larger than 2GB with error 'After-image extent is not found'.

Querying the _lock table sometimes returns lock records which contain an empty lock flag.

Able to failover and failback using replication datasets, however, once I failback, the subsequent failover fails.

Multi-volume backup is failing with error 1617 but not specifying the reason why

ai extents locked after restart of rpls/rpla and aimgt

The “rfutil  -C aimage list” command shows incorrect Start Dates.

On target replication synchronization failed when online backup started.

AIMGT is not logging probkup online  -estimate.

When the invalid "-estimate"  switch is used with an ONLINE probkup,
Notes about the  completed backup are not written to the archiver  log:
0032,...,BACKUP_SET_20150601_151759,...

For OpenEdge DataServer for MS SQL Server, CLOB field smaller than 1 GB fails to be read through a Stored Procedure (RUN STORED-PROC) where stored-procedure result set processed using temp-table.

OpenEdge Installer returns to serial number prompt and does not proceed when a serial number entered is less than 9 digits

Progress OpenEdge 12.2.8 Client Networking installation doesn't register the libraries %DLC%\bin\system\pstimer.ocx and %DLC%\bin\prox.dll

Uninstalling 32-bit Progress WebClient application breaks 64-bit Progress WebClient application as it results into un-installing dlls PSCCab, PSCSecReg from 64-bit WebClient.

ABL/WEB Client is sending data from previous request if network was disrupted for previous request that was sending a MEMPTR to the server

OpenEdge 12.6 HttpClient no longer reports SSL failures/certificate hash correctly when the certificate missing

Syntax error when MIX/MAX functions are passed a dynamic buffer field reference as one of its parameters, and the function is a parameter to a built-in function/statement (for example, OVERLAY or SUBSTRING).

Client may leak a small amount of memory each time it connects to a Web service.

The conversion of an rpc-encoded SOAP output parameter into a dataset by a webservice client may fail due to a mismatch between the outer element name and the WSDL's specified part name.

When using the ABL Web Services client (WSO), an invalid HTTP response may cause the client to crash. In the case of a PASOE ABL Session, it will bring down the whole MS-Agent process.

For each with join does not return records with Server Side join enabled if the database codepage and the -cpinternal of the database server do not match

If the source string is a LONGCHAR variable the NORMALIZE function modifies the LONGCHAR variable’s value in addition to returning the normalized string.

If an OUTPUT DATASET-HANDLE or INPUT-OUTPUT DATASET-HANDLE parameter is passed to an asynchronous procedure which is run locally (RUN … ON SESSION) and the parameter is not assigned a value (either in the caller or callee) the AVM will crash when calling the associated event procedure.

When NEWing a class that inherits a class which has been modified (and recompiled) after the NEWed class was compiled, the session crashes if the modified class contains a PROTECTED constructor.

The AVM crashes if the first reference to a .NET object in the session is an OUTPUT parameter which returns a .NET object. This occurs when running the application in r-code.

The application compiler does not raise an error for an invalid BY clause if the index picked for the query is UNIQUE and the components of that index match the BY clauses from left to right. Any BY clauses which follow the BY clause(s) which match the index components will not be validated.

PASOE session may intermittently throw error “You are trying to use a multi-threaded .NET object in a way that is not supported. The ABL cannot be called on a thread other than the main thread. (15740)” when trying to access a .NET data member or execute a .NET method even though multi-threading is not involved.

Using the Add method to create a large number of elements in a JsonArray (Progress.Json.ObjectModel.JsonArray) may result in slow performance.

Error “Cycle in procedure calls detected in <procedure> while executing WRITE trigger for <table>. (2868)” may lead to record corruption if trigger is running within the scope of a sub-transaction.

The AVM may crash when a .NET string containing multibyte Unicode characters is converted to an ABL LONGCHAR variable if the length of the string in bytes is approximately 32,000.

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.

The _dbutil executables from 10.1A (101a_dbutil), 10.2B (102b08_dbutil), and 11.7 (117_dbutil) display the error “Unable to read progress.cfg, reason=-5 (1732)” when they are used with OpenEdge 12.5 on Linux.

A compilation listing from within a PASOE session does not produce the debug listing.  Running this same code from a GUI editor on the same PAS server works fine.

The -require-return-values compilation option generates a warning (or error, if enabled) if a return path contains the UNDO, THROW statement instead of a RETURN statement.

Deleting a dynamic dataset that is an INPUT-OUTPUT/OUTPUT DATASET-HANDLE parameter marks the dataset as pending delete. If you then set the DATASET-HANDLE parameter to the unknown value, deleting its member dynamic temp-table might cause a crash.

Infinite (or too deep) recursion in an ABL Application crashes the complete PASOE agent instead of just the thread running the recursion. The last messages typically seen in the log file before the disappearance without a trace are Error 5407.

Extraneous characters may appear in the output file if a message contains extended characters (for example, a message from the French PROMSGS file) and output is redirected to a file.

In 32-bit OpenEdge products on Windows, the READ-JSON method may generate error “Couldn&#39;t allocate memory for copying a large object. (11325)” when reading a very large JSON file.

The LOOKUP function returns 0 when the codepage is set to UTF-8

If there is code in an internal procedure called by a database trigger that does RETURN ERROR , the RETURN-VALUE that is set will be cleared, incorrectly, before the trigger returns.  So that RETURN-VALUE will not be seen by the code that caused the trigger to fire.

.NET Open Client tracing tracing and logging have an impact on GC performance due to string concatenation of log messages even when tracing and logging are disabled.

Using .NET OpenClient with debug logging enabled, System.NullReferenceException and stack traces are written to the log file if the releaseConnection() function is not called on the Connection before the object is garbage collected.

The parameters defined in the .NET Open Client ParamArray object that are passed to the Dynamic AppObject RunProc method are set to null when an exception occurs.

ProxyGen allows characters that do not conform to XML specification within the name of an XML tag / element when using the XML-NODE-NAME / SERIALIZE-NAME option for Temp-Tables and ProDataSets, resulting in errors when these tags are received in a response by a client that performs tag name validation.

System.Reflection.AmbiguousMatchException is thrown when calling a method for which there is a generic and a non-generic method implementation with the same method name and the same parameter counts and types.

If you try to subscribe to an event in an ABL interface that inherits the event from a .NET interface, you will get the following error when the code is compiled:

Could not locate element &#39;_psc_Subscribe_NET&#39; in class &#39;&#39;.(12927)

Webclient or ABL client crashes when application uses garbage collection, and profiler is enabled at run-time using PROFILER system handle, and disabled in class destructor that is triggered by the garbage collector.

DataServer schema allows duplicate index numbers for indexes on a given table, which can cause the client to crash when accessing such table.

Security vulnerabilities have been identified in Apache Xerces C++ 3.1.1, a third-party component which is included in OpenEdge.

OpenEdge Management does not allow to set the After-image archival interval to on-demand

Stop agent button is missing from Classic AppServer resource view in OpenEdge Management console

PASOE agent process disappeared without a trace while one of its threads was holding a DB latch in shared memory.

reassignConnection() message informing connection state is now moved to diagnostic logging

Resource manager generated a fatal SYSTEM ERROR (163) on seek error 9, and then generates a protrace file. The PASOE Agent process may hang.

PASOE application is slower or hangs sometimes when running on AIX platform

ABL Client processes hang while connecting to either Classic AppServer or PASOE. This has most commonly been reported in Pro2 environments when Pro2 threads are connecting to an AppServer across a WAN and experiencing a fairly high level of network errors.

Terminating an ABL Session in a PASOE agent after an asynchronous STOP event has interrupted a SOAP Out request to an external service may cause a thread in the PASOE agent process to crash and generate a protrace when the ABL Session is shut down.

PASOE client session stuck in WRITING state and some times PASOE agent consuming 100% CPU

Terminating an ABL Session in a PASOE agent after an asynchronous STOP event has interrupted a SOAP request to an external service may cause the PASOE agent process to crash without a trace. If it is connected to an OpenEdge Database via Shared Memory, this can cause the Database to be shutdown.

PAS for OpenEdge agent capacity self-management should not have interrupted the handling of a missing OpenEdge Database connection. The agent is left in a state where it can’t service any request.

If a refresh of the ABL Sessions occur while an ABL Session is busy executing the Session Startup Procedure, then the ABL Session may crash and bring down the database that it is connected to. It may also prevent new requests from being processed for a period of time.

The pasman utility with pasoestart option on Windows platform doesn&#39;t return the correct exit error code when the script fails because the PAS for OpenEdge instance in question is already running.

Client Principal user-id uses the jwt sub claim and ignores *jwtToken.usernameField*. The solution now correctly uses the jwtToken.usernameField for the Client Principal user-id.

The documentation of the following properties were injected into the middle of the OEClientPrincipalFilter.loadAccntAttrList property in oeablSecurity.properties.README.

OEClientPrincipalFilter.validateClientDomain
OEClientPrincipalFilter.useEMailID

This caused the majority of the documentation for OEClientPrincipalFilter.loadAccntAttrList to be pushed down under the definition of OEClientPrincipalFilter.useEMailID

New oeablSecurity.properties property oauth2.resSvc.*strictAudience* (default false) added for strict validation . Property works as follows:

* When the oauth2.resSvc.audience is _not specified_ in the PASOE configuration, validation is disabled
* When the oauth2.resSvc.audience is specified, but the token has no claim, strict==true will fail, strict==false will succeed
* When the oauth2.resSvc.audience is specified and the claim does not match, will fail
* When the oauth2.resSvc.audience is specified and matches the claim, will succeed

PDSOE context assist shows odd characters for some suggested methods

Accessing some of the help pages in PDSOE 404 is reported with some links.

The edit button doesn&#39;t save SQL connections, only Configure database connections link will save changes.

PDSOE Class browser not showing reference for Progress.Database.TempTableInfo and Progress.Database.VSTTableID class in OpenEdge 12.5

Problem with content Assistant when attempting to set a local field from a property in PDS OE.

Organize USING statements incorrectly inserts USING System.Buffer for buffer parameters.

OpenEdge SQL server (_sqlsrv2) might result into a crash when the CLASSPATH environment variable is empty and the database is started with option “-SQLWidthUpdate ON”.

When a query containing derived table is run on multi-tenant enabled database, as a result we are getting “Access denied error (Authorization failed) (7512)” error on OpenEdge Sql Server where as this query runs fine on non multi-tenant database.