Hi Vidur,
I think that your problem stems from the specifications themselves. See
the EJB1.1 spec section 9.1.11 about concurrent access to an entity bean.
As a work-around, you could perhaps copy the information from the entity
bean to a normal bean, and share that.
Nick Newman, SCIENTECH
At 04:53 AM 7/30/00 -0400, you wrote:
>Hello,
>
>I need help in working around this exception. Here's the scenario. In
>a stateful session bean, a particular method takes several seconds (and
>maybe even a minute or so) to execute. While executing it _reads_
>another entity bean. The session bean is marked "transaction required"
>and uses the default isolation setting. At any given time, there are
>several such session beans executing.
>
>My understanding is that since Orion does not support optimistic
>concurrency, the entity bean is "locked" by the first session while it
>is executing. Hence, any other session can not read the entity bean
>till the first session completes. Is my understanding correct? How can
>I workaround this? Is there a more general pattern I can use for
>allowing multiple clients concurrent read-only access to the entity
>beans?
>
>Thanks,
>Vidur
