Content Delivery hotfixes
This section describes the hotfixes in release 9 CU1 that apply to specifically to Content Delivery.
- Hotfix CRQ-9939
During bulk publishing, a few items failed during transporting phase. - Hotfix CRQ-9986
Webapps running at 100% CPU when reading and writing simultaneously to Sdl.Web.Delivery.Model.DynamicDataLoader. - Hotfix CRQ-11360
Content Delivery throws an exception: "java.nio.file.FileSystemNotFoundException: Provider "zip" not installed" when deploying legacy roles such as the Preview Service or Content Service as .war files in Weblogic. - Hotfix CRQ-12136
Transactional unpublishing failed on theXoContentFragmentUnDeploystep. - Hotfix CRQ-12271
Content Delivery did not include the possibility to enable TLSv1.2 with Content Delivery microservices that communicate with the Content Delivery database. - Hotfix CRQ-12815
Public Content API GraphQL client threw aGraphQLClientExceptionexception with the following main error text: "PCA client returned an unexpected response when retrieving enity model data for idIDENTIFIER". This was due to a failure of properly setting Publication IDs. - Hotfix CRQ-12913
The Content Interaction Libraries (CIL) for .NET were not retrieving metadata. - Hotfix CRQ-13138
TheGetTaxonomyKeywordsmethod inTaxonomyRelationManagerwas not returning values. - Hotfix CRQ-13166
A security scan identified an Apache ActiveMQ vulnerability with the identifier CVE-2016-3088. - Hotfix CRQ-13167
A security scan revealed a vulnerability identified as CVE-2018-1000632 (a dom4j vulnerability). - Hotfix CRQ-13397
The Content Deployer was experiencing a memory leak. - Hotfix CRQ-13405
Incorrect or old content was being shown by the DXA Model Extension due to a lack of Page context inEntitiesCache. - Hotfix CRQ-13406
The DXA Model Extension could not use the proximity logic used in core Content Delivery link resolving. - Hotfix CRQ-13495
HTML entities were being unescaped when a Dynamic Component Presentation was being rendered; for example, the string "Sites & Docs" was returned as "Sites & Docs". - Hotfix CRQ-13711
The Content Deployer service needed additional configuration to support pooling in the state store configuration. - Hotfix CRQ-13730
Public Content API GraphQL queries did not return the titles of Categories or Keywords. - Hotfix CRQ-13733
Ambient Data Framework headers being sent uncompressed was causing problem in, among others, Experience Manager, because the uncompressed header could sometimes be too large to be handled by a load balancer. - Hotfix CRQ-13900
The JDBC driver did not yet support asocketTimeoutproperty. - Hotfix CRQ-14124
Missing indexes in the Content Deployer State Store database caused the Content Deployer to throw a java.nio.file.NoSuchFileException exception, and caused a deadlock error when mass publishing against a multi-destination target. - Hotfix CRQ-14128
The Ambient Data Framework client threw aConcurrentModificationExceptionexception - Hotfix CRQ-14351
Elasticsearch 5 requests did not have strict content type checking. - Hotfix CRQ-14573 / Hotfix CRQ-19221
Sorting on custom metadata fields in GraphQL, either normally or using the Component Presentation method, was not possible. - Hotfix CRQ-14802
When a microservice was configured to use integrated authentication when connecting to its database, the error "Unable to acquire JDBC Connection" occurred. - Hotfix CRQ-14838
Content Data Store temporary database tables were not being cleaned up. - Hotfix CRQ-14973
The Public Content API did not include the ability to sort on custom metadata field values when using GraphQL queries. - Hotfix CRQ-14978
Using DXA, resolved links sometimes didn't include a domain name, but only a relative path, even when a domain was configured. - Hotfix CRQ-15038
TransformContextwas missingODataparameters, which made it impossible to access theODataparameters (including query string parameters) from a customTagRenderer. TheTransformContextargument passed todoStartTaganddoEndTagwould only have a single, empty$expandvariable when expanding a section such asPageContent. - Hotfix CRQ-15121
Starting the Content Service as a Windows service was hanging while showing the message "Starting storage transaction monitoring". - Hotfix CRQ-15330
The database connection pool size for the Content Service was not configurable. - Hotfix CRQ-15564
TheOAuthTokenProviderdid not synchronize sufficiently. - Hotfix CRQ-15928
HTTP security headers were needed in the Content Delivery microservices. - Hotfix CRQ-16047
A persistent error reading "Unable to get response from OData service" occurred. - Hotfix CRQ-16054
A "preview needs update" message appeared when selecting Update Preview, and various SQL warnings and errors related to binaries were reported in the Content Service logs. - Hotfix CRQ-16304
Stopping and restarting the Context Engine microservice caused the device database to increase in size each time. This was caused by the recreating of indexes. - Hotfix CRQ-16315
A JAR scanner that is part of Spring Boot (a library used by Content Delivery) reportedly gave errors of the following format: "Failed to scan JARNAME from classloader hierarchy - java.io.FileNotFoundException: JARNAME (The system cannot find the file specified), where JARNAME is the name of a JAR file. - Hotfix CRQ-16416
Various issues related to resolving evidence, which occurred when using DXA with Content Delivery, were fixed. - Hotfix CRQ-16496
A security scan revealed a vulnerability identified as CVE-2019-16335 in Jackson Databind. - Hotfix CRQ-16649
The Content Interaction Services (CIS) Content Service crashed frequently, reporting errors while trying to retrieve Keyword lists. - Hotfix CRQ-16672
The search feature was not working for Japanese content. - Hotfix CRQ-16778
A vulnerability was discovered in Jackson Databind. - Hotfix CRQ-16811
Mass publishing was causing performance issues. - Hotfix CRQ-16874
Link caching was found to never have worked in the Session-enabled Content Service or Model Service. - Hotfix CRQ-16907
An error occurred: "Violation of PRIMARY KEY constraint 'PK_ITEMS'. Cannot insert duplicate key in object 'dbo.ITEMS'. The duplicate key value is [...]" - Hotfix CRQ-16908
The Content Service remains stuck in a "stopping..." state when you try to stop it. - Hotfix CRQ-16977
ThehasKeywordChildrenmethod ofkeyworderrors due to cyclic references in the keyword tree in output JSON. - Hotfix CRQ-17023
Publishing pages with an internationalized URI fails in the Commit Deployment phase. - Hotfix CRQ-17035
Triggers of type Boolean did not hit Experience Optimization Promotions. - Hotfix CRQ-17059
The DXA Java web application went down after 3 failed tries to connect to Content Delivery microservices. - Hotfix CRQ-17103
Using theTRIDION_HOMEenvironment variable to load Content Data Store content was not working when using the in-process API for .NET. - Hotfix CRQ-17118
The flush interval of the Discovery Service was not configurable, leading to errors such as "java.lang.RuntimeException: Not possible to retrieve the dynamic configuration". - Hotfix CRQ-17161
The Content Interaction Libraries (CIL) cache was polling the wrong URL for the Content Service for health checks, returning in the same HTTP 401 value every time. - Hotfix CRQ-17338
In-process API caching and ActiveMQ caching were not working. - Hotfix CRQ-17389
This hotfix fixes performance problems with the Content Deployer. - Hotfix CRQ-17440
When upgrading DXA to work with a newer Content Delivery version, the following error occurred: "Unable to cast object of type 'System.Collections.Generic.Dictionary`2[System.String,System.Object]' to type 'System.Collections.Generic.Dictionary`2[System.String,System.String]'. - Hotfix CRQ-17518
The Content Service threw aNumberFormatExceptionexception when querying for Dynamic Component Presentations. - Hotfix CRQ-17547
AnArrayIndexOutOfBoundExceptionexception was thrown. - Hotfix CRQ-17548
DynamicContentProvidersometimes used the cache for the methodList<String> getPublicationUrls(int publicationId) - Hotfix CRQ-17549
A null pointer exception occurred. - Hotfix CRQ-17628
The Conditions "is above or equal" and "is below" for Content Filtering numeric values were not functioning. - Hotfix CRQ-17632
In Triggers, "Contains", "Starts with" and "Ends with" only worked if they were an exact match. - Hotfix CRQ-17761
The database server spiked and Content Service experiences latency when publishing just a few pages. - Hotfix CRQ-17772
One or two files failed when (un)publishing multiple files at the same time. This could occur because the Content Deployer picked up incoming transaction ZIP packages based on the ZIP file's last modified date, which could sometimes lead to wrong behavior. - Hotfix CRQ-17783
Despite the installation of hotfix CD_8.5.0.14838, the cron job does not clear all records in the execution table of the Content Deployer. - Hotfix CRQ-18066
Theservletpathindex was found to be out of range in the Contextual Image Delivery filter, resulting in the error on WebSphere: "java.lang.StringIndexOutOfBoundsException: String index out of range: 4" - Hotfix CRQ-18144
The Content Deployer was found to be unable to load a module. - Hotfix CRQ-18167
In a scaled-out setup with multiple Content Deployer workers, the BINARY_STORAGE\ subfolder of the installation folder contained thousands of XML files, leading to a variety of problems. - Hotfix CRQ-18192
When a storage extension failed, Content Deployer kept on retrying forever. - Hotfix CRQ-18447
This hotfix adds additional logging for JMS and JDBC pools. - Hotfix CRQ-18569
Cache invalidation doesn't seem to work or is delayed. A multithreading issue deteriorated the calculation of cache size and prevented a correct cleanup of the cache. - Hotfix CRQ-18623
HSQL support was added for Preview functionality to fix performance degradation for the Session-enabled Content Service and the Preview Service. - Hotfix CRQ-18658
Caching byEhcachewas prevented due to a non-serializable class, com.sdl.odata.client.ActionImportClientQuery, and the application stopped, throwing an exception. - Hotfix CRQ-18750
The caching policy implemented by com.tridion.cache.LRUPolicy had the potential of causing memory leaks, because itsprocessPutmethod may not remove elements from memory. - Hotfix CRQ-18753
Even though a commit operation fails (specifically, ifTridionCommitStepfails), the Content Deployer nevertheless keeps retrying the package. - Hotfix CRQ-18754
Ehcachewas consuming a large part of the memory heap with a custom meta query, becauseCustomMetaValueCriteriahad asignatureIdfield that incremented every time the object is constructed. This led to a unique cache key every time. - Hotfix CRQ-19012
The Content Service threw an exception "Incorrect data format" due to being unable to filter by custom (date) metadata. - Hotfix CRQ-19030
A running Content Broker call caused the CPU of the database server to spike and took 4 minutes to complete due to an inefficient SQL query. - Hotfix CRQ-19164
Experience Optimization on the Content Delivery side wrongly converts Trigger values defines as String to Long when the value is a series of digits, even when starting with leading zeroes. - Hotfix CRQ-19212
A pen test on the Content Deployer found a number of high and medium issues. - Hotfix CRQ-19229
ContentClientdid not use the cache in 99% of cases. - Hotfix CRQ-19354
TheEvidenceSerializerclass of the Context Service threw a null pointer exception. - Hotfix CRQ-19499
Presentation servers became unresponsive after an upgrade, with threads hanging. - Hotfix CRQ-19557
InvalidGrantissues resulted in "Token expired" messages in logs. - Hotfix CRQ-19562
The Content Broker schema was missing the Tridion item type which should be part of a unique key. - Hotfix CRQ-19630
A combination of DXA 2.0 and an in-process Model Service caused Experience Manager not to work properly, resulting in a null pointer exception. - Hotfix CRQ-19747
While calculation an object's size, the Content Delivery cache threw a null pointer exception. - Hotfix CRQ-19782
Insufficient synchronization took place on theeventQueuefield in com.tridion.cache.CacheChannel. - Hotfix CRQ-19901
Null pointer exception was thrown in RequirementUtil#claimMatch. - Hotfix CRQ-19977
Public Content API GraphQL queries were sometimes found to be slow. - Hotfix CRQ-20084
This hotfix makes theApplicationIntentsetting configurable in the Storage Layer configuration file, cd_storage_conf.xml, through a new property calledIsolationLevel. - Hotfix CRQ-20115
This hotfix fixes an issue with the log level forHeartbeatGenerator. - Hotfix CRQ-20318
Content Deployer was not sending an ActiveMQ message to invalidate caches. As a result, binary items which were updated in theBINARY_CONTENTtable were not updated in the presentation environment. - Hotfix CRQ-20530
When using DXA on a high availability stack, performance was found to degrade. - Hotfix CRQ-20623
A null pointer exception occurred inCachedBaseDAO. - Hotfix CRQ-20754
The database migration script provided no way to specify a custom port. - Hotfix CRQ-20791
Running database scripts resulted in the error "com.microsoft.sqlserver.jdbc.SQLServerException: Cannot insert the value NULL into column 'COMPONENT_PRES_META_DATA_KEY ". - Hotfix CRQ-20800
Cache statistics information was missing from the log. - Hotfix CRQ-20949
A Public Content API GraphQL call was found to take too much time. - Hotfix CRQ-21215
Upgrading Content Delivery databases failed because the Powershell version was too old. - Hotfix CRQ-21335
The Ambient Data Framework was not accepting third-party cookies. - Hotfix CRQ-21358
Upgrade scripts, specifically Utilities.ps1, were not compatible with Azure SQL - Hotfix CRQ-21391
In the Discovery Service, some configurations were found to have no parent. This can cause problems when trying to load a parent item or making batch requests from Topology Manager. - Hotfix CRQ-21415
Content Interaction Services (CIS) requests were found to slow down after applying the Surrogate Key hotfix. - Hotfix CRQ-21434
After applying the Surrogate Key hotfix, some database issues were reported. - Hotfix UDP-9225
This version of Content Delivery did not work with the 19c database client software for Oracle databases.