Geeks, please accept the hero post of 2021 Microsoft x Intel hacking contest>>>
No EntityManager with actual transaction available for current thread – cannot reliably process ‘remove’ call; nested exception is javax.persistence.TransactionRequiredException: No EntityManager with actual transaction available for current thread – cannot reliably process ‘remove’ call
The reason is that in the business method of update delete operation, there is a service without @ transaction annotation
Only in the business method of new operation, some services are not annotated and will not report an error
Question: will all of the update and delete involved in this way be in the same thing?How to refine the modification and update of the whole business
Similar Posts:
- [Solved] MYSQL Deadlock found when trying to get lock; try restarting transaction
- MySQL reports an error lock wait timeout exceeded; Try restarting transaction problem solving method
- How to Solve Spring Bean Same Name Conflict
- MySQL Lock Error: Lock wait timeout exceeded [How to Solve]
- Lock wait timeout exceeded; try restarting transaction-Mysql [How to Solve]
- SpringMVC @RequestBody Error:Unrecognized field, not marked as ignorable
- AOP Configuration Services error: javax.persistence.TransactionRequiredException: no transaction is in progress
- Quartz: add transaction rollback error [How to Solve]
- Can not issue data manipulation statements with executeQuery().
- How to deal with the exception of database connection pool in Python flash