Add support for customizable transaction isolation level settings [JDBC]
See original GitHub issueIn some situations it would be useful to have the ability to override the default transaction isolation level when setting up the JdbcTemplateLockProvider
.
Specifically it looks like an extension could be made to the JdbcTemplateLockProvider.Configuration
class so that the desired isolation level could then be passed into the JdbcTemplateStorageAccessor
for use by the transactionTemplate in the constructor. As it is currently implemented, I’m not sure how to do this via overrides since JdbcTemplateStorageAccessor
is not public.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:9 (4 by maintainers)
Top Results From Across the Web
How to set the JDBC isolation level. - TIBCO Support
Resolution: For the BW XA transaction group, you can set the transaction isolation level using BW property in tra. The transaction isolation ...
Read more >A beginner's guide to transaction isolation levels in enterprise ...
In this post we are going to unravel the reasons behind using different transaction isolation levels and various configuration patterns for ...
Read more >Configuring the JDBC Connector (Optional)
Ensure that the JDBC driver for the external SQL database supports any connection-level property that you specify. Connection Transaction Isolation Property.
Read more >Transaction Isolation Level Settings
Specify transaction isolation level settings to set the transaction isolation level for a database. This setting prevents dirty read, repeatable read, ...
Read more >Specifying the isolation level - IBM
At run time, use the SQLSetConnectAttr function with the SQL_ATTR_TXN_ISOLATION attribute to set the transaction isolation level for the current connection ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Released as 4.27.0
Well, specifically with the default isolation level there are errors showing up in the database logs regarding transactions needing to be restarted due to all of the running instances waking up vying to run the job. I’ve noticed that if I elevate isolation to SERIALIZABLE, these errors go away. However, I don’t want to use SERIALIZABLE on all of my connections, so having this as a customizable feature just for Shedlock solves the problem for me.