The project I am handling has the following features: 1. Quite a lot(hundreds of thousand) entity beans will be created 2. And they will NEVER be removed
The project is to enhance a legacy project which used JDBC directly to persist data. I also understand that EJB will be passivated and be put into the pool so that App Server will not be out of memory. The question is that, even if an EJB is passivated, will it still occupy some resources on App Server? If yes, what kind of resource is occupied? If there are several million EJBs created and then passivated, will they exhaust resources of App Server since they will never be removed? In the legacy system, this is not the problem. Because it used JDBC, all data only exists in DB, not App Server. I am going to enhance it using EJB. But due to the above considerations, I am hesitating whether to use it or not since it may require a huge amount resource to be added to App Server. (BTW, I am using JBOSS as App Server) Any suggestions? <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3826067#3826067";>View the original post</a> <a href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3826067>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
