-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Open
Labels
status: waiting-for-triageIssues that we did not analyse yetIssues that we did not analyse yettype: bug
Description
In Spring Batch 5.2.x the StepExecution returned from the SimpleJobExplorer returned a fully populated StepExecution, including the ExecutionContext.
Spring Batch 6.0.0, is using a JobRepository for the same task fetching the StepExecution, however, that doesn't seem to populate the ExecutionContext for the StepExecution. It ultimately delegates to: JdbcStepExecutionDao without loading the ExecutionContext from the BATCH_STEP_EXECUTION_CONTEXT table. Failing my remote partitioned batch job.
Not sure if this is intentional and I am missing out on something, but to me this seems to be an issue.
NOTE: It does work when you switch to using ResourcelessJobRepository.
Regards
Ruud
Metadata
Metadata
Assignees
Labels
status: waiting-for-triageIssues that we did not analyse yetIssues that we did not analyse yettype: bug