ERROR: could not serialize access due to concurrent update
859542May 4 2011 — edited May 20 2011Hi.
I use ejb+glassfish+postgres in my project.
The project is a web application for finansial data transfering.
I have three DBs, long global transactions, serializable isolation level, container-managed transaction.
When i test the project with concurent threads, i get an exception: "ERROR: could not serialize access due to
concurrent update"
I read that when you get suck kind of error, your program must rollback current transaction and then reply this transaction.
what do i need to do to complete this transaction? :
1) rollback and reply transaction
2) maybe, the are other ways to reply transaction (for example: glassfish configurations, ....)
Edited by: 856539 on 04.05.2011 8:10