[SLING-12471] The ScriptDependencyResolver can wrongly return null values when invoked concurrently

• Type: Improvement
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: Scripting HTL Engine 1.4.24-1.4.0
• Fix Version/s: Scripting HTL Engine 1.4.26-1.4.0
• Component/s: HTL, Scripting
• Assignee: Radu Cotescu
• Reporter: Joerg Hoh
• Created: 05/Nov/24 16:38
• Updated: 12/Dec/24 07:09
• Resolved: 06/Nov/24 15:34

Description

With caching enabled, under concurrency the ScriptDependencyResolver.resolve can return null values.

Context: Github

1. Multiple threads are trying to resolve the same scriptIdentifier
2. They all proceed to line 133 because the resolutionCache is not yet populated.
3. One thread gets the writeLock, resolves the result, stores it back into the resolutionCache, and eventually releases the write lock.
4. now all the other threads waiting on line 133 lock on the writelock one-by-one; and when checking the resolutionCache on line 136, the resolutionCache is already populated; and then they just release the writelock and proceed. But during this time result is never read from the resolutionCache, so it's still null and returned as such.

This normally happens immediately after startup, when the resolutionCache is still empty.

Issue Links

• links to: GitHub Pull Request #28