Issues fixed in OpenEdge 12.5.3
- Last Updated: September 9, 2024
- 1 minute read
- OpenEdge
- Documentation
Click here for a list of known issues.
The following table lists issues fixed in this release:
| Component | Issue Number | Description |
|---|---|---|
| ADE | OCTA-48091 |
While generating a delta.df, you may receive an error, “No _Field record is available. (91)” if the difference in the two database schemas means a DROP Field operation would go into the delta.df. |
| PASOE | OCTA-49729 |
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. |
| PASOE | OCTA-49865 |
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 | OCTA-46475 |
Starting in the OpenEdge 12.2.8 release, if your PAS for OpenEdge instance generates a high volume of log messages and there is high concurrency (greater than 40), then you may occasionally find a datetime stamp of [00/00/00@00:00:00.000+0000] in some of the messages. |
| PASOE | OCTA-50986 |
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 | OCTA-40782 |
If a PAS for OpenEdge agent thread encounters a SIGABRT signal, it may cause an immediate shutdown of the agent process. One source of a SIGABRT is a networking failure in handling the response from a SOAP Out request. If the PAS for OpenEdge agent is connected to an OpenEdge database via shared memory, this can cause the database to be shutdown. |