INC-164514 · Issue 635085
Unnecessary logging removed from startup
Resolved in Pega Version 8.6
The error "SettingMisusageFailure: Database is null" was repeatedly being logged following an update that consolidated error-handling logic for using a third-party custom jar file during the compiling process. This was an unnecessary message for this scenario as the database is often null at the early stages of startup, and SystemSettingsImpl has been updated to skip logging this error.
INC-166498 · Issue 637351
Locking and classmap improvements
Resolved in Pega Version 8.6
Threads were getting stuck inside classMap and tableInformationMap, causing nodes to go down. This was traced to issues with class map performance and locking, and has been resolved by replacing the lock library with a newer version and refactoring the tableInformationMapImpl class to use a concurrent hashmap instead.
INC-85182 · Issue 622326
Process added to clear unneeded requestors from shared pools
Resolved in Pega Version 8.6
Shared service requestor pools were persistently showing a growing count of active requestors when a service was under heavy use, potentially leading to timeouts and exceptions. Investigation showed requestors were moving from active to inactive without updating the pool manager, causing service requestor pools to be held in an inconsistent state with active requestor pools not going down even after completion of service request. To resolve this, a job scheduler process has been added to stabilize the service requestor pools heuristically.