Hi, All. I think, the problem is caused not only by long transaction. Anything that lives long may cause problem since they occupy resources. For example, long-lived session beans & eneity beans will do even they are not involved in transactions.
Take my project as an example, there will be handerds of thousand entity beans, which will NEVER be removed once created. that is, every entity bean will live for ever. There will be one entity bean handling transactions. Each transaction is short. And I also encountered the "out of memory" problem. What I am going to say it that, EJB model is not suitable for those projects, which are database centric, because that will make app server demand storage resources as much as DB server, something is a mirror. <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3826814#3826814";>View the original post</a> <a href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3826814>Reply to the post</a> ------------------------------------------------------- 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
