Greetings,
Unfortunately the only way to resolve your concurrency problem is to use an
Entity bean containing you list. That way your Session bean acquires in its
create and activate methods a reference to the list entity bean and releases
it in the passivate and remove methods. Your Entity
ses a java.util.List. Therefore I
> suppose that it is an orion problem when the SLSB is created.
> Thanks, Esteban
>
>
>
> -Original Message-
> From: Rice, Ted [mailto:[EMAIL PROTECTED]]
> Sent: Friday, July 27, 2001 1:45 PM
> To: Orion-Interest
> Subject: RE:
> From: Rice, Ted [mailto:[EMAIL PROTECTED]]
> Sent: Friday, July 27, 2001 1:45 PM
> To: Orion-Interest
> Subject: RE: Concurrency
>
>
> you are working with a non-synchronized
> collection. if you get an iterator and
> attempt to modify the backing list with
> multiple threa
herefore I
suppose that it is an orion problem when the SLSB is created.
Thanks, Esteban
-Original Message-
From: Rice, Ted [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 27, 2001 1:45 PM
To: Orion-Interest
Subject: RE: Concurrency
you are working with a non-synchronized
collection. if
:[EMAIL PROTECTED]]
Sent: Friday, July 27, 2001 3:44 AM
To: Orion-Interest
Subject: Concurrency
> Hi
> Please help me. I am working with a stateless EJB and I have about 250
> clients which has to use this EJB.
> When the clients access to the SLEJB concurretly, the Orion crash, and the
> Hi
> Please help me. I am working with a stateless EJB and I have about 250
> clients which has to use this EJB.
> When the clients access to the SLEJB concurretly, the Orion crash, and the
> server.log shows:
>
> 7/4/01 6:45 PM Internal server error
> java.util.ConcurrentModificationException
> Hi
> Please help me. I am working with a stateless EJB and I have about 250
> clients which has to use this EJB.
> When the clients access to the SLEJB concurretly, the Orion crash, and the
> server.log shows:
>
> 7/4/01 6:45 PM Internal server error
> java.util.ConcurrentModificationException
When two log in request reach the Orion web server at the same time, it
confuses the two requests and logs in both people with the same userid and
two different sessions of one person are seen by the two clients sending the
log in request.
This is also true for when any teo similar requests
