I think he means with the SAME primary key. That depends on the server implementation, and the amount of concurrent TX's that interact with the SAME entity, the latter of course depends on the isolation level associated with the EB.
That information is supposed to be concealed by the app server(for a number of reasons, mainly, scalability issues, and TX isolation). You should not care about it. The real question is: Why do you want to know? Remains curious, Juan Pablo Lorandi Chief Software Architect Code Foundry Ltd. [EMAIL PROTECTED] Barberstown, Straffan, Co. Kildare, Ireland. Tel: +353-1-6012050 Fax: +353-1-6012051 Mobile: +353-86-2157900 www.codefoundry.com > -----Original Message----- > From: A mailing list for Enterprise JavaBeans development > [mailto:[EMAIL PROTECTED]] On Behalf Of John Bateman > Sent: Monday, April 22, 2002 7:24 PM > To: [EMAIL PROTECTED] > Subject: Re: Reg number of instances per primary key? > > > Hi > > Aren't these number all dependant on the amout that the > initial pool size is set to? > > > > 1)How many instances of an entity bean(Read only) > > exist with a given primary key on a single server > > instance? > > ============================================================== > ============= > 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".
