Last Modified: Nov 07, 2022
See more info
Known Affected Versions:
11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9
Opened: Apr 10, 2015
Related Article: K17875190
In some rare cases, if a document is 'assembled', it can stall, giving little or no response to the client.
Requests for that document results in client timeouts.
This might occur when the original document is smaller than the small object cache size limit, but grows to be larger than the small object cache size limit during assembly. In rare cases, this can cause the document to be unservable.
Create a policy node for that specific document, and set to 'proxy always.'
This release corrects a miscalculation, allowing an 'assembled' document to be correctly written to the metastor cache and served to the requesting client.