Frank Sauer wrote: > According to the EJB 1.1 spec the container is *supposed* to > throw an exception on the 2nd-Nth re-entrant call. Apparently > not all vendors are compliant yet. > > We ran into this problem (Gemstone is compliant and throws the exception) > and solved it by creating a session pool on the client side. There's issues here for large scale systems who need more performance container memory efficiency than serializing calls to a pool of non-reentrant beans can provide? If your Entity is designed for re-entrant calls then why not? BTW, how does WLS 5.x propose to provide capacity when they've disallowed reentrant calls to Enties and SB's??? Another typical scenario that needs higher perf. solution: Threaded client (500 threads) needs a handle to a SB that supports reentrant calls to a shared EJBObject. What else? Each thread does home.create() 500 times??? curt
begin:vcard n:Smith;Curt tel;work:404-237-1166 x182 x-mozilla-html:FALSE org:Z-tel.com adr:;;;;;; version:2.1 email;internet:[EMAIL PROTECTED] title:Senior Software Engineer x-mozilla-cpt:;-1 fn:Curt Smith end:vcard
