The TOPLink container for WebLogic also creates multiple instances of entity beans used by more than one client. Wolf Siberski Jean-Baptiste Nizet wrote: > Floyd Marinescu wrote: > > > Hi everyone, > > > > I was stumped by the following post on TheServerSide: > > > http://www.theserverside.com:8080/patterns/thread.jsp?thread_i > d=220#2665 > > > > Gal suggests that most ejbServers will load multiple instances of an > > entity bean with the same primary key inorder to service multiple clients. > > > > Is this true? Which app. servers do this? > > > > Yes, it's true. Actually, I've played a little bit with three AppServers, and > only Weblogic didn't do this (except when the servers are clustered, which should > be the most common config.). > Both Inprise AppServer and iPlanet 6 can have multiple instances of the same > logical Entity Bean, because they chose to use optimistic concurrency instead of > pessimistic concurrency. This gives them a better performance, and no deadlocks. > To me, the choice made by WL in this area is wrong, because it leads to > deadlocks, and because the behavior becomes different when you go from a single > box to a clustered environment. > > JB. ------------------------------------------------------------- Wolf Siberski TUI Infotec GmbH OO Consultant Karl-Wiechert-Allee 23 mail: Wolf Siberski at tui de D-30625 Hannover =========================================================================== 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".
