Announcement Announcement Module
No announcement yet.
DataSourceTransactionManager Locking mechanism Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • DataSourceTransactionManager Locking mechanism

    Recently I started to get DeadLock Exceptions from my MySQL database.
    This lead me to deeper locking mechanism investigation, but I failed to find proper info on how DataSourceTransactionManager is locking and ensuring proper transaction.

    I have to change my database from different locations:
    1) Crontab - directly update table
    2) MySQL event
    3) Server 1 (connects directly and executes queries using JdbcTemplate)
    4) Server 2 (connects directly and executes queries using JdbcTemplate)

    Is there any option for me to keep my way of managing DB and get rid of those exceptions, or should I create an API, which would manage all database transactions?