> -----Original Message-----
> From: Curt Smith [mailto:[EMAIL PROTECTED]]
> Sent: Viernes, 31 de Agosto de 2001 9:27
> To: Orion-Interest
> Subject: Shared SB reference in Web tier business delegate??
>
>
> Greetings,
>
> My app is a thick client replacement with J2EE web-ified functionality
> where 3000+ clients will login and stay logged in all day.
>
> I'm wanting to reduce the number of session objects as a result of so
> many concurrent sessions. I plan on keeping a per session business
> deligate manager, but make the DAO instances static thus shared amoung
> all sessions since my DAO's are re-entrant.
>
> I'm concerned about sharing a single SB remote interface amoung all
> sessions (Threads)???
Why not let the container manage the actual number of instances created?
That would lead to 3000 proxy instances, but just a handful of SLSB.
>
> Of course SSB remote interfaces will need to be tied to that session!!
I can't quite follow you here. Do you meaqn the http session?
>
> What about the few Entities that might be accessed from the web tier?
> <reentrant> vs not reentrant Entities??
Entities that are reentrant, by the EJB 1.1 spec (section 9.1.12), are those
that can be called in a loopback WITHIN the same
transaction. Different transactional contexts calling the same Entity(by
this I mean an entity with equal PK) are not reentrant calls. Basically,
this allows for loopbacks in a call thread, but its use is discouraged by
the spec.
>
> I wish the EJB spec was clearer about reentrancy of the remote
> interface or maybe someone can shed some light??
Again, check out the same section on the spec; transactional context
(sometimes called activity) plays an important role in determining if a call
is reentrant.
>
> Thanks alot to the orion mail list.
>
> curt
>
>
> Curt Smith
> [EMAIL PROTECTED]
> (w) 404-463-0973
> (h) 404-294-6686
>
