Hi,
All EJBHomes and Stateless Session Beans are workload managed in WebSphere.
On Stateful session beans the creation only is WLM'ed and individual
requests are not, but I think this does not apply to you as you are on
Stateless.
Please refer to a WebSphere 2000 conference presentation (2-3A) for some
clarifications on what the WLM can and cannot do.
http://www-4.ibm.com/software/webservers/ws2000_present.html
Note, also you need to up to some efix levels if you are running WAS
3.0.2.1. There are special fixes for WLM.
http://www-4.ibm.com/software/webservers/appserv/efix.html
-- Aravind
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Fabrizio Barbero
> Sent: Tuesday, 23 May 2000 17:51
> To: [EMAIL PROTECTED]
> Subject: ejb and load balancing
>
>
> I'am working with WebSphere 3.0 ae, on a enteprise solution involving
> jsp/servlet front-end and EJB components ( the servlet/jsp
> component calls ejb
> stateless components for business logics ).
> Considering that my application should support a great amount of users
> connected via browser, I was wondering about providing correct
> load balancing
> feature at appserver ( ejb container ) level.
>
> In particular I am asking if Application server ( websphere for instance )
> load balancing routering is provided in the lookup ejb phase, that is when
> issuing the following statements
> Object o = SingletonContextFN.getInitialContext().lookup("MyMgr");
> myHome = (MyMgrHome)PortableRemoteObject.narrow(o,
> MyMgrHome.class);
>
> or when the ejb components is created, that is when:
> MyMgr myMgr = myHome.create();
>
> or when the ejb components is used ( i don't think so .. )
> myMgr.insertStock( sessionId, "001052050" );
>
> I was designing the application to set the reference to myHome interface
> just at serlvet startup ( or in any case the reference gets invalid .. ),
> using for instance a static var.
> But, if load balancing is applied only at lookup phase, I have to bind the
> home iface every "create", that is every time I am using the ejb
> components, that could be a big overhead. Otherwise my servlet
> instance will be
> linked always to the same ejb container instance, not providing a
> correct load
> balancing.
> Is it correct ?
> Any ideas ?
> Thanks
> Fab
>
> ==================================================================
> =========
> 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".
>
>
===========================================================================
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".
