Skip to content

Batch with JPA should not use higher isolation levels #197

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
dsyer opened this issue Jan 8, 2014 · 0 comments
Closed

Batch with JPA should not use higher isolation levels #197

dsyer opened this issue Jan 8, 2014 · 0 comments
Milestone
0.5.0.M7

Comments

@dsyer
Copy link
Member

dsyer commented Jan 8, 2014

See stackoverflow for history.
@dsyer dsyer closed this as completed in 147968c Jan 8, 2014
gigfork pushed a commit to boostrack/spring-boot that referenced this issue Apr 21, 2014
Set isolation to DEFAULT for JPA transaction manager
3089660 
Also logs a warning about the fact that locks may not be taken when
starting a Job. JPA and Batch don't really work that well together
in general so it's probably not worth a lot of effort to work aoround
this. If anyone needs to they should create a custom JpaDialect
(and a BatchConfigurer).

Fixes spring-projectsgh-197
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.5.0.M7
Development

No branches or pull requests
1 participant
@dsyer