The container requires only 1 bean instance to service the finder call. It does not matter how many rows are returned as a result of the finder. A bean instance is required when servicing the business method through the component interface. The container associates/disassociates a bean instance from the remote/local object as required and hence can service lots of requests using a comparatively small pool.
-Saurabh ----- Original Message ----- From: "Saminathan Balasundaram" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, October 04, 2002 2:22 PM Subject: Entity Instance Pooling > Hi All > > I am not sure whether this question will make sense or not,But > i just wanted to get > clarified. > > My question is that i have instance pool setting in my application > server > say Min Size = 10, Max Size = 100 and the growth interval is 5. > > Now i have situation that one my queries is going to return 80 Rows.Now > as per entity bean > spec, entity bean represents a single row in the DB table. > At this point of time how many entity instance will be created by an > Application > server.Is that one entity will manage and retrieve all the 80 Rows or > multiple instance will be > operated by a application server for handling that sitution. > > Can some one please throw light on this? > > Thanks and Regards > Saminathan.B > > =========================================================================== > 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".
