In my app I had I found if a user double-clicked on a search submit it generated a nasty error from my database (MySQL) about a dead lock problem.
Here is the first part of the error:
Having fixed the double-click problem, this has got me worried about collisions from multiple users trying to run a search simultaneously. If they happen to search at the same time won't one of them get the same error?
Is there a way to configure the transaction so that it will allow multiple reads at the same time?
Or is there a better replacement for the @Transactional annotation? This class does not really need a transaction. But when I take it off Spring does not know how to handle the entity.
The squeaky wheel gets the grease. Well, that or replaced...
Happily living in the valley of the dried frogs with a few tiny ads.