CLI: Context Propagation Error in Asynchronous Task Execution

[jgambarios]

Problem Statement

We've identified an issue in our application where the context is not properly propagated in asynchronous task executions. This problem affects our ability to maintain consistent state and context (e.g., security context, transactional context) across asynchronous operations, leading to unpredictable behavior and errors during runtime.

Problem Details

The issue arises when executing asynchronous tasks that rely on context inherited from the parent thread. Due to the nature of our asynchronous operations, the context is not automatically propagated, resulting in tasks that execute in a contextually "blank" state.

Proposed Solution

After investigating potential solutions, we've determined that utilizing the ManagedExecutor service from MicroProfile Context Propagation is the most effective way to address this issue. ManagedExecutor ensures that the context is captured from the thread that submits the task and is then propagated to the thread that executes the task.

Implementation Details

The fix involves refactoring our existing asynchronous task execution model to leverage ManagedExecutor. This change will ensure that context is properly captured and propagated across asynchronous boundaries, maintaining consistent behavior across our application.

Specific changes include:

• Replacing direct usage of CompletableFuture and other native Java concurrency mechanisms with ManagedExecutor.
• Ensuring all asynchronous tasks are submitted through ManagedExecutor for execution.
• Adjusting unit and integration tests to account for the new asynchronous execution model.

Proposed Objective

Core Features

Proposed Priority

Priority 2 - Important