If TimerTask is being used, then a new thread is created everytime the timer task executes, right? And since that task needs access to the JTA transaction manager to establish a write lock for eviction
So, this would mean there is a new thread, not created by the servlet/ejb container, which is associated with the container-managed transaction. Am I correct on this? Thanks for the tip on optimistic locking. I am going to look at this for the future, but it is a little scary if the transactions are going to fail if an out-of-sync version is detected. Hopefully these cases would be few and far between but even a couple would not be ideal. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3942652#3942652 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3942652 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
