INC-194305 · Issue 681681
File Dataset wildcards updated for ADM storage
Resolved in Pega Version 8.7
Attempting to access the filepath was failing and an error was seen indicating "Could not obtain lock 'Create repository file pegacloudfilestorage:ADM/Rule-Decision-AdaptiveModel/Data-Decision-Request-Customer". While creating a file name, a lock is generated while checking the file names of existing files. If the file data set has a large number of files, a condition may occur where some threads are unable to save data and an exception is thrown. To resolve this, the wildcard previously used in the file name has been replaced with the Pega node id + thread id + current timestamp. This will ensure all wildcards are unique and there is no need to lock and list existing files.
INC-170721 · Issue 658960
Stricter criteria set for reusing an SSAExecutionContext
Resolved in Pega Version 8.7
After a Strategy was configured with an existing Proposition Filter and the Explain Results box was unchecked, executing the strategy resulted in the error "Stack is empty, cannot pop any more frames". Investigation showed that the SSAExecutionContext object was reused across the two criteria evaluation in Proposition Filter rule: this works well as long as the input is the same across the two evaluations. However, the SSAExecutionContext object also stashed a reference to a PublicAPI object which became stale in the second evaluation and caused the empty stack issue for the given scenario. This has been resolved by providing stricter criteria in deciding when an SSAExecutionContext can be reused or not in the case of Proposition Filter rule.
SR-B48818 · Issue 305799
Enhancement to make Cassandra data file location configurable
Resolved in Pega Version 7.3.1
The location of the Cassandra data directory is hardcoded in versions 7.2.1 and greater and points to a different directory than previous releases. This caused problems for upgrades from pre-7.2.1 systems where disk volumes may already be configured specifically to house Cassandra data in the old locations. For Tomcat installations, the data file location is hard coded to be a directory under the Catalina Home directory. In customer systems, this creates a problem because the home directory is frequently not configured to be big enough to accommodate the Cassandra data volume. In order to improve compatibility, a new configuration property (DNode/cassandra_data_directory) has been added to override the hardcoded location using prconfig.xml, Dynamic System Settings, or the command line. Configuration options are provided for prconfig.xml and Dynamic System Settings that allow specifying the location of the Cassandra data.
SR-B50813 · Issue 315070
Improved performance for Proposition updates
Resolved in Pega Version 7.3.1
While updating propositions through DSM portal it was observed that the thread count got very high while overall performance became degraded. This happened in Pega versions where the propositions are data instances and not rules. The issue was traced to the Proposition cache getting reloaded from the database table in a synchronized block; all of the strategy execution threads were waiting until the reloading completed despite strategy reading the propositions from the cache. To resolve this, the system will reload the proposition cache from the database table in the thread where the pulse message is being processed when the node receives the pulse notification. Thus other strategy execution threads will not be blocked and continue reading propositions from the cache.