MDVA-39605: Redis cache TTL (expiration date) has wrong value

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.

Affected products and versions

The patch is created for Adobe Commerce version:

• Adobe Commerce (all deployment methods) 2.4.2

Compatible with Adobe Commerce versions:

• Adobe Commerce (all deployment methods) 2.3.4 - 2.4.4

Issue

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:

1. Run the command: redis-cli.
2. Run KEYS "*PRICE" (there should be only one key in the result, for example, zc:ti:e54_PRICE). Copy the key.
3. Run SMEMBERS followed by the key from the previous step (for example, SMEMBERS zc:ti:e54_PRICE). Copy any key from the result (for example, e54_4E67B390D5C28FC7C3D9BB0D37AB3F7B5E576421).
4. Run 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.
5. Run HGETALL followed 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.
6. Run TTL followed 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.

Expected results:

Expiration limit is 2592000s

Actual results:

Expiration limit is set to -1 or -2.

Apply the patch

To apply individual patches, use the following links depending on your deployment method:

• Adobe Commerce or Magento Open Source on-premises: Software Update Guide > Apply Patches in our developer documentation.
• Adobe Commerce on cloud infrastructure: Upgrades and Patches > Apply Patches in our developer documentation.

Related reading

To learn more about Quality Patches Tool, refer to:

• Quality Patches Tool released: a new tool to self-serve quality patches in our support knowledge base.
• Check if patch is available for your Adobe Commerce issue using Quality Patches Tool in our support knowledge base.

For info about other patches available in QPT, refer to Patches available in QPT in our developer documentation.