The MDVA-39605 patch solves the issue where the Redis cache TTL (expiration date) has a wrong value. This patch is available when the Quality Patches Tool (QPT) 1.1.13 is installed. The patch ID is MDVA-39605. Please note that the issue is scheduled to be fixed in Adobe Commerce 2.4.5.
The patch is created for Adobe Commerce version:
Compatible with Adobe Commerce versions:
The patch might become applicable to other versions with new Quality Patches Tool releases. To check if the patch is compatible with your Adobe Commerce version, update the
magento/quality-patches package to the latest version and check the compatibility on the QPT landing page. Use the patch ID as a search keyword to locate the patch.
The Redis cache TTL (expiration date) has a wrong value.
Steps to reproduce:
In order to test the fix, flush cache and open a configurable product on the storefront. Then open a terminal (console) and follow the steps below:
KEYS "*PRICE"(there should be only one key in the result, for example, zc:ti:e54_PRICE). Copy the key.
SMEMBERSfollowed by the key from the previous step (for example,
SMEMBERS zc:ti:e54_PRICE). Copy any key from the result (for example, e54_4E67B390D5C28FC7C3D9BB0D37AB3F7B5E576421).
KEYS "*<key>"with the key name from the previous step to get the full key name (for example,
KEYS "*e54_4E67B390D5C28FC7C3D9BB0D37AB3F7B5E576421"). There should be only one key in the result (for example, zc:k:e54_4E67B390D5C28FC7C3D9BB0D37AB3F7B5E576421). As you may notice, the full key name is simply the key name with prefix “zc:k:”. Now copy the full key name.
HGETALLfollowed by the full key name from Step 4 to check the value. The value should contain serialized data of associated products of a related configurable product.
TTLfollowed by the full key name from Step 4 to check whether the key has an expiration. The result should be different from -1 and -2 and should be approximately 2592000 (30 days). Although the expiration set in the code is one year, the Redis library used in Adobe Commerce has a hard max expiration limit of 2592000s.
Expiration limit is 2592000s
Expiration limit is set to -1 or -2.
To apply individual patches, use the following links depending on your deployment method:
To learn more about Quality Patches Tool, refer to:
For info about other patches available in QPT, refer to Patches available in QPT in our developer documentation.