Home Search Pricing Get inErrata About

Sign in Sign up

Graph/8945e3bf-9a8c-4eb2-af94-fb4ed4c4e323

Domainunvalidated

Transaction Management

8945e3bf-9a8c-4eb2-af94-fb4ed4c4e323

Transaction Management

Node Details

Public graph metadata

Updated5/1/2026

PageRank0.0001

Effectiveness0.000

Connections

17 linked nodes

PERTAIN_TOSolution

I know that it is recommended to use `select..for update skip locked` — under high data volume and frequent updates/deletions. Tension: it can lead to performance degradation. Outcome: `skip locked` is the cheapest option.

PERTAIN_TOSolution

with cte as (delete from edge where 'id1' in (id1,id2)) update node set version = version + 1 where id = 'id1'; — single query without having to start a transaction. Tension: should delete the edge; instead [23503] ERROR. Outcome: Or the other way around, taking `version` into account.

PERTAIN_TOProblem

PhotoComment is not updated when a user ratePhoto() changes a photo rating

PERTAIN_TOSolution

Use entityManager.update() inside a transaction to update all matching PhotoComment rows when saving a new PhotoRating

PERTAIN_TOProblem

The same code can be run in parallel in multiple threads, or even in multiple Kubernetes pods — DELETE FROM my_table WHERE ctid IN ( SELECT ctid FROM my_table WHERE some_condition LIMIT 1 ). Tension: two threads start fighting for the same record.

PERTAIN_TOSolution

in the concurrent setup. Tension: I am considering the following fix, but I am not sure if it is necessary.

PERTAIN_TOProblem

Is it possible to lost increment here? Tension: stats.setTotalSold(stats.getTotalSold() + 1); // lost increment? Outcome: Lost increment is impossible with REPEATABLE_READ isolation level (at least in PostgreSQL).

PERTAIN_TOSolution

Or you can increment value in one query — for READ_COMMITTED. Tension: There are solutions for READ_COMMITTED:.

PERTAIN_TOProblem

"No EntityManager with actual transaction available for current thread - cannot reliably process 'remove' call" — when trying to delete using the user email. Tension: When using the @Transactional it works, I've read that JPA uses @Transactional by default. Outcome: My question is, does JPA uses @Transactional by default and I'm doing something wrong or I really should explicitly use it on delete and update?

PERTAIN_TOSolution

you will have to give `@Transactional` explicitly either at Controller, Service or Repository level — since you have added a custom method - `void deleteByEmail(String email);`. Outcome: To run those methods transactionally, use `@Transactional` at the repository interface you define.

PERTAIN_TOSolution

if you use derived queries.

PERTAIN_TOProblem

The delete of table2 caused a timeout and a SQLTimeoutException occurred, but the delete of table1 was committed. — When a timeout occurs in the database, HikariCP does not rollback, but commits and terminates abnormally. Tension: org.springframework.transaction.TransactionSystemException: JDBC rollback failed. Outcome: Use the latest HikariCP 6.3.0, the problem has been fixed in that version.

PERTAIN_TOSolution

Use the latest HikariCP 6.3.0, the problem has been fixed in that version. — The above problem was not fixed in HikariCP version 5.0.1. Outcome: implementation("com.zaxxer:HikariCP:6.3.0").

PERTAIN_TOProblem

Multiple threads are writing in the file concurrently. — I need to persist this counter because if process get restarted then it counter should start from last count. Tension: I hope there wont be a case when any number shall be skipped or give duplicate value to thread. Outcome: how to reset this key when value reaches to 25k in a thread safe way.

PERTAIN_TOSolution

In addition to the suggestion of using a Lua script, you could stick to your solution of using `INCR` — since redis is single threaded so this will be thread safe. Tension: how to reset this key when value reaches to 25k in a thread safe way. Outcome: simulate the reset of the counter on the client side by taking the remainder of the returned value.

PERTAIN_TOProblem

Spring Boot 3 and using Java 21. Tension: the objects new UserTransactionImp() and new UserTransactionManager() are using the old way, with `javax.transaction.UserTransaction` and `javax.transaction.TransactionManager`. Outcome: How can I make `new UserTransactionImp()` and `new UserTransa.

PERTAIN_TOSolution

Using the starter — `transaction-jdbc`, `transaction-jms` and `transaction-jta` are automatically imported with `jakarta` as classifier. Tension: Check if you are importing the "no-jakarta" modules. Outcome: try to use the starter, or specify the classifier in pom.xml.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata