Issues fixed in OpenEdge 12.2.14

Error 12371 when selecting menu options in the Data Administration tool.

PASOE Lite doesn't ship CONSPAWN.EXE

The ‘Disconnect’ field of the _Connect VST behaves differently for self-service vs client-server connections

PROMON will defer signal handling while in calls that may break consistency of database state.

The JTA menu in PROMON is unable to prompt for confirmation when the JTA transaction ID is 9 or more digits. This prevents rolling back or committing JTA transactions stuck in the prepared state.

Message 7129 still showing up in database log file for SQL connections when using -omitLgMsgs 7129

Database failed to start due to error (9215) last open date mismatch between .db file and the d1.

Database connections using -RO are very slow if the .lg file has no write permissions.

After upgrading glibc on Linux, DB broker fails to spawn server with the following error:

enssbrocon: child terminated due to signal 11, err=9.

The _mtprosrv executable produces Segmentation Fault when run directly without any arguments.

Oracle DataServer - indexed-reposition - query get-next() after reposition jumps back to first result when the first index component have duplicate values, second index component have null value and third index component have distinct values  for RowId on which reposition-to-rwoid is called.

An update to datetime field of a table with multiple number of Varchar2 and datetime fields Using the dataserver on Oracle DB with system property MAX_STRING_SIZE set to extended reports error: ORA-01830.

Running r code using prowin32 results in error -”OpenEdge Graphical Client has stopped working”.

READ-JSON and READ-XML leak memory when they directly call a method or function that returns a LONGCHAR or MEMPTR.

PASOE agent crashes intermittently calling a dotnet method that returns a double as a decimal.

Version 12.2 fathom -load failed to ignore deprecated product from fathom dump from version 11.7

_dbagent does not shutdown with proshut db -by -shutdownTimeout 2m causing a failure to shutdown.

When an AppServer procedure with a DATASET and LONGCHAR output parameter is exposed as a SOAP web service within PASOE, then the response will hang for a considerable amount of time while serializing the LONGCHAR output parameter.

Under 12.2.11 PASOE failed to pass three parameter values to connect procedure.

PASOE PROPATH is concatenated with extra text when it is published via deploying build automatically. Process adds propath entries to the running agent, but somehow many entries are duplicated, causing the propath list to grow increasingly longer.

Client unable to connect to PASOE after multiple agent refresh REST calls

PAS for OpenEdge 12.2.12 results in high CPU for java process when servicing SOAP requests

OE SQL Server is crashing in highly concurrent environment due to free memory read. Its happening while using cached information about table`s field.