noob question about EJB Transactions and concurrency
meatwadJun 23 2011 — edited Jun 28 2011I have a web client that calls a stateless session bean. This bean contains a method that checks the data in some database tables and, if everything looks good, calls a stored procedure which updates those tables. If I understand correctly, placing this method in a container-managed transaction should guarantee that only one instance of that method inside the bean can run at any time and would prevent 2 threads from running it simultaneously.
Do I have that right?