Issue |
Solution |
ID |
The Registry SO reads changes from the database while under a write lock, which pauses all active requests on a given server. |
This has been corrected in AudienceView 6.7.1.
The Registry has been changed to read records outside of the write lock and only obtain the write lock when applying changes to the Registry. |
AVD-1869
AVD-2543 |
Implement separate thread in cache service. |
This has been corrected in AudienceView 6.7.1.
Separate thread in cache service has been implemented. |
AVD-1871 |
The AVScheduler inserts an authentication record into ts_audit and then continues to process the scheduled job. Many jobs take a considerable amount of time to complete, leaving the record in ts_audit locked, which causes major performance issues whenever ts_audit is being queried without READUNCOMMITTED hint. |
This has been corrected in AudienceView 6.7.1.
New sessions authenticate in their own transactions, which only includes authentication and not the main job. |
AVD-2243 |
All of the promotional code access codes are being cached as new codes are added, eventually consuming all of the server's RAM. |
This has been corrected in AudienceView 6.7.1.
The memory leak has been fixed, and the RAM is no longer being consumed. |
AVD-2407 |
The BI query being used for the Customer Services application Customer|Customer History pages is causing performance issues. |
This has been corrected in AudienceView 6.7.1.
The BI behind the Customer Services application Customer|Customer History pages has been updated, and two new indexes were added to the ts_order and ts_order_audit tables. The performance issue no longer exists. |
AVD-2771 |