I have an application that is a fairly straightforward
Struts project where the Action classes call some business methods on plain old
java objects (POJOs), stuff the results into the request, and forward to JSPs for display.
We are expecting a significant increase in traffic after our next release. The POJOs are short-lived, but we could conceivably reach the point where we run out of memory.
My thought is to either turn the POJOs into Stateless Session Beans or have Stateless Session Beans control access to the POJOs. We could then tune performance by adjusting the pool size of the Stateless Session Beans. In essence, the Stateless Session Beans would act as a throttle when we reach a certain level of traffic.
The application has no need for other kinds of EJBs.
We are already using a full
J2EE app server for this app, so cost is not an issue.
Any comments / suggestions?
Also, are there any standard metrics for determing pool sizes?
thanks!
[ May 19, 2005: Message edited by: Paul Croarkin ]