Hi J2EE 1.2 App server -------------------
I need to wrap my head around the issue of many servlets and/or Java objects on HOST-A calling one EJB on HOST-B and how this affects connection management issues. Can somebody explain how this process happens under the covers, is there connection management happening at the J2EE layer or does the application logic (connection pooling library) have to do it. The scenario ============ 1. The 'Business Delegate' java object (HOST A) is calling an EJB Stateless Session Bean 'Facade' (HOST B) 2. Potentially many HTTPServlets (implementing the SingleThreadModel) will be using the EJB's remote interface (HOST B) from the 'Business Delegate' java object(HOST A) . <HOSTA><HTTPServlets> -> <Business Delegate Java object></HOSTA> ---> <HOSTB><EJB Facade></HOSTB> Questions ========== 1. Do I use a connection pooling mechanism to handle a set number of EJB references? 2. Do I make the Business Delegate Java object Multi-threaded? 3. Do I make the Business delegate a Servlet and let the Servlet container deal with the threading issues? How does this affect the number of connections are opened on the Servlet container? How will this affect performance? Basically I am looking for an understanding on how to have many HTTPservlets use the EJB remote interface handle from the Java Business Delegate. Any ideas on the best approach to take here. cheers Luie ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
