----- Original Message -----
From: "Nitin Kulkarni" <[EMAIL PROTECTED]>
> 1. Is it true that the number of EJBObject class instances (generated by the
> container) as same as that of the clients connected at the same time. Or can
> an EJBObject be shared between the clients?
This is up to the container.
Most containers generate one EJBObject per bean that is shared among clients.
> 2. What exactly hapeens when multiple clients want to fire the same query?
> How many instances of entity beans are created by the container? Some
> literature say that Entity beans are not shared at all? then why do we need
> isolation levels?
This is up to the container.
Most containers allow multiple clients to simultaneously access an entity bean.
This is achieved by creating multiple instances of the entity bean and giving
each client exclusive access to one instance.
Keep in mind that WebLogic (pre 6.0) serialized access to Entity Beans on a per
container basis. jBoss also currently works this way. WebLogic changed their
approach in 6.0 because serialized access can impose serious performance
problems, as well as potential deadlock scenarios.
AFAIK, isolation levels have no meaning inside the EJB Container. They are used
by the container to set the appropriate iso level on the JDBC connection.
jim
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".
