Rickard Oberg wrote:
>
> Hi!
>
> > I use Stateful Session bean for keeping information for each user. The
> > Session bean is stored to the HttpSession. If servlets are running in
> > one frame all is OK. But if I let run servelts in 3 frames the "No
> > concurrent calls on stateful beans Exception" is called.
>
> This is as specified by the EJB 1.1 specification, i.e. normal.
>
> > I tested the same bean in simple thread application( 20 threads used the
> > same bean ) and no exception was thrown. Therefore I guess the problem
> > is in Tomcat.
>
> There is most likely a bug in your test application. It should fail. Are you
> sure your threads are accessing the same stateful session instance ?
You are right. It was my mistake in the test application.
But anyway , How to solve this problem ? I need somehow keep client
specific session data( and I don't want store it in HttpSession).
I have Similar using in my applet which in the thread is loading data
and in another thread use another methods from Bean. Using "critical
sections" for all calling of business method's is not so easy.
thanks
mino
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
