I think you may consider to use a combination of stateless session bean and
entity bean
even if you are only reading the date from db, I believe there might be lots
of date
which you need to access over and over in subsequent calls, in that case
this scenario
may increase your overall performance. I am not sure when you tell that Java
Objects are faster than session bean , you really simulated 1000+ concurrent
user or not. I am not sure how difficult to achieve that using servlet and
clean Java Objects. EJB are not only
(Java objects + RMI/IIOP + some EJB logic) , there lot more side to explore.
I believe
w/ your requirement , if you design it properly with proper EJB pattern ,
you will definitely achieve a better performance.
-- Ahimanikya
> >
> > We are having severe performance problems. We have stateless
> EJBs (instantiated
> > from Servlets- WebSphere as the Application Server) to retrieve
> the Data from
> > Oracle DB. The performance is poor in the test environment. If
> I have the simple
> > Java Objects than the performance is much better. We need to
> install the system
> > into 1000+ concurrent user base. Will stateless Session EJB
> perform/scale better
> > than Java Objects in that environment as we have NO
> transactional requirements.
> > Of course I can make resource pools for the Simple Objects But
> does the Session
> > EJB benefit us in the Simple Inquiry Applications?
> > Should we go for Session EJBs or Simple Java Objects?. Can any
> body provide me
> > with some statistics for this question for my
> situation(1000+concurrent users)?
> >
> > Fareed Ahmad
> >
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
