1) I have a stateless session EJB (say MyEJB)deployed in weblogic 7 (on a linux box with weblogic allocated memory as 256 mb)with maximum pool size as 100.Now my stateless session EJB calls sequentially two classes namely A and B. Class A access a HTTPServlet and retrieves a message and gives that message to another Stateless Session EJB(with pool size 100) through class C. Now I tried to increase the EJB pool size from 100 to 500 in both the beans in order to increase the performance. To my surprise the EJBBean Instance in use is not increasing beyond 80 even though when I try to pump in Heavy loads of data (i.e when I try to access simultaneously 1000 instances of "MyEJB" from a client program).Why is the EJBPool size is not growing Beyond a particular limit say 80 in this case ?. 2)Is it advisable to cache a stateless session beans object ?If i cache will it affect the Scalability of the stateless session EJB?
Thanks for reading my question patiently and trying to solve it. regards Smyle
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: Stateless Bean Optimum PoolSize and Caching of StatelessBean