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
Not sure if this is a bug or just a documentation issue.
Bug description
As of Batch 5, calling any JobExplorer method without an active transaction produces the following warning:
2022-11-11T23:33:19.650Z WARN o.s.jdbc.support.JdbcTransactionManager : Custom isolation level specified but no actual transaction initiated; isolation level will effectively be ignored: PROPAGATION_SUPPORTS,ISOLATION_READ_COMMITTED
The cause seems to be the changes made with #4195. As of these changes, JobExplorer is transactional with PROPAGATION_SUPPORTS,ISOLATION_READ_COMMITTED, causing the warning being logged if called outside of a transaction.
Environment
Spring Batch 5.0.0-RC2
Steps to reproduce
Call any JobExplorer method without an active transaction.
Expected behavior
The call works without issuing warnings.
kzander91
changed the title
Calling JobExplorer outside of a transaction logs warnings about the Isolation Level not being appliede
Calling JobExplorer outside of a transaction logs warnings about the isolation Level not being applied
Nov 11, 2022
@kzander91 Thank you for opening this issue. I think the current default propagation level SUPPORTS is correct, but not the default isolation level of READ_COMMITTED. This will be changed to DEFAULT, which fixes the issue.
Not sure if this is a bug or just a documentation issue.
Bug description
As of Batch 5, calling any
JobExplorer
method without an active transaction produces the following warning:The cause seems to be the changes made with #4195. As of these changes,
JobExplorer
is transactional withPROPAGATION_SUPPORTS,ISOLATION_READ_COMMITTED
, causing the warning being logged if called outside of a transaction.Environment
Spring Batch 5.0.0-RC2
Steps to reproduce
JobExplorer
method without an active transaction.Expected behavior
The call works without issuing warnings.
Minimal Complete Reproducible example
demo1.zip
mvn spring-boot:run
The app calls
JobExplorer#getJobInstanceCount()
from aCommandLineRunner
, which issues the warning mentioned above.The text was updated successfully, but these errors were encountered: