I think this only applies at beans with very long initialization (ejbCreate()) time). Initializing on startup helps reduce latency later. The exact number is a tradeoff between resource usage, runtime latency, and server startup time, and of course should be on a bean-by-bean basis. I wouldn't touch it unless I have a very complex init sequence in a bean. Most SLSB's do very little init. - Avi -- This signature intentionally left blank. > > Weblogic has this feature of populating the free pool > of SLSB at startup time. > > It accepts a "initial-beans-in-free-pool" in the > deployment descriptor and populates the specified > number of instances at start up. > > What shd be the basis to arrive at such a number ? > Would it be a uniform figure across SLSBs or should it > be decided on a Bean to Bean basis ? > > rgds > - arun > > > > > __________________________________________________ > Do You Yahoo!? > Make international calls for as low as $.04/minute with > Yahoo! Messenger > http://phonecard.yahoo.com/ > > ============================================================== > ============= > 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".
