I still don't believe you'll ever get concurrent threads going
trhough a single instance of your bean implementation. Yes, the
container can interleave, but not concurrently. It knows when a bean
is currently in a transaction, and won't use it for new requests until
it's finished. Or am I totally off base here?
Frank
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of James Cook
> Sent: Monday, July 17, 2000 5:06 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Multi-Threaded Protection within a SSB
>
>
> From: "Perry Hoekstra" <[EMAIL PROTECTED]>
> > What drew my concern was the "the Container may interleave
> requests from
> > multiple transactions to the same instance". If the vendor
> implements a
> > single instance of a SSB (to limit resource overhead) and
> manages the
> > interleaving of requests to that bean, how is access to the shared
> > resource (my collection of worksteps) handled.
>
> You are very correct, and my previous statement is incorrect
> according to
> the spec. Thanks for bringing this up. I suppose, I was
> confusing the way
> *my* container (Inprise IAS) works with the spec's description.
>
> It is unfortunate that the spec adds that last caveat...the interleave
> statement. I'm a little surprised they don't force the container's to
> serialize instead of interleave. In many places the spec
> states that their
> goal for a particular design is to free us from having to think about
> reentrant coding. Argh.
>
> Perhaps this can still be changed before EJB 2.0 is
> finalized. It would be a
> pretty trivial change on the vendor's part. I wonder how many of them
> support the interleaved approach anyway. I know that Inprise
> creates a new
> SLSB for each concurrent client request.
>
> jim
>
> ==============================================================
> =============
> 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".
