You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug description
I use a RepositoryItemReader in a multi-thread scope (with a task executor)
RepositoryItemReader is thread safe, and as documented I set up : .saveState(false) and manage my state in my own code.
Steps to reproduce
Run my Job and the WARN logs are showed: ItemStream was opened in a different thread. Restart data could be compromised.
Expected behavior
No warn about state when save state is disabled.
Minimal Complete Reproducible example
Please provide a failing test or a minimal complete verifiable example that reproduces the issue.
Bug reports that are reproducible will take priority in resolution over reports that are not reproducible.
// ChunkMonitor.javaprivateChunkMonitorDatagetData() {
ChunkMonitorDatadata = holder.get();
if (data == null) {
if (streamsRegistered) {
logger.warn("ItemStream was opened in a different thread. Restart data could be compromised.");
}
data = newChunkMonitorData(0, 0);
holder.set(data);
}
returndata;
}
The text was updated successfully, but these errors were encountered:
Bug description
I use a RepositoryItemReader in a multi-thread scope (with a task executor)
RepositoryItemReader is thread safe, and as documented I set up :
.saveState(false)
and manage my state in my own code.Environment
Java 21
SpringBoot 3.3.0
SpringBatch 5.1.2
Hibernate 6.5.2
Steps to reproduce
Run my Job and the WARN logs are showed:
ItemStream was opened in a different thread. Restart data could be compromised.
Expected behavior
No warn about state when save state is disabled.
Minimal Complete Reproducible example
Please provide a failing test or a minimal complete verifiable example that reproduces the issue.
Bug reports that are reproducible will take priority in resolution over reports that are not reproducible.
My Step:
My reader:
The text was updated successfully, but these errors were encountered: