Hello Vikas, Thanks for replying.
I am kind scared that this will be a valid behaviour because if I am executing a findBy.... method that is NOT read-only and has a transaction type "Required" then I better have the lock to do whatever I want with that bean. Nobody can do a findBy... on the same bean unless I am done with it first. Isn't this the appropiate behaviour? In the logs, I can see that two different threads are executing the same findBy... method of an entity bean which is kind of scary because if one thread decides to delete the record then the other one will have a primary key that doesn't exist anymore in the database. There has to be a way to avoid this confrontation between these two beans. How come the second thread is being allow to execute the findBy... method in the first place? Thanks in advance, jchang P.S. Please let me know if I am missing something? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3830447#3830447 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3830447 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
