We are using Java EE. And are making an apllication where in the worst case, aloot of message queue messages willl come form the same User.
Therefore we are looking on Pessimistic, SELECT FOR UPDATE style locking. Which in theory and fisrt tests solves our problems.
But we are afraid of deadlocks. Not the classical ones: User X locks A, User Y locks B.But more of scenarious like: system crash, netowrk problems,... and so on. Datbase system locking up, for no know reason. We will use modern databases like: oracle, MS SQL and postgresql.
What we would like to know is pessimistic locking used in production and what practical problmes to expect?
Thanks in advance!