nal Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 08, 2005 8:22 PM
> To: Struts Users Mailing List
> Subject: Re: concurrency problem
>
>
>
>
>
>
> Maybe I'm being dense here but:
>
> If every session contai
Maybe I'm being dense here but:
If every session contains a reference to the bean, and every thread is
synchronizing on their own session;
It would seem that there would not be any concurrency control.
I would think that they all need to sync on the same object.
JC
ss.
> Sounds like your provider might have a defect.
>
> Dennis
>
>
>
>
>
> [EMAIL PROTECTED]
> 04/08/2005 09:13 AM
> Please respond to
> "Struts Users Mailing List"
>
>
> To
> "Struts Users Mailing List"
> cc
>
> S
PROTECTED]
04/08/2005 09:13 AM
Please respond to
"Struts Users Mailing List"
To
"Struts Users Mailing List"
cc
Subject
RE: concurrency problem
You're synchronizing on an object which is unique for each user, which
might explain why more than 1 thread can concu
04/08/2005 08:53 AM
Please respond to
"Struts Users Mailing List"
To
"Struts Users Mailing List"
cc
Subject
RE: concurrency problem
Isnt that valid when request is going to same action. In my scenario,
different actions are invoked quickly and all the actions have thi
lto:[EMAIL PROTECTED]
> Sent: Friday, April 08, 2005 6:04 PM
> To: Struts Users Mailing List
> Subject: Re: concurrency problem
>
>
> You'd be better off implementing token processing.
>
> Struts includes token generation and helper methods to ensure
> only one valid
&g
You'd be better off implementing token processing.
Struts includes token generation and helper methods to ensure only one valid
request is handled at a time. Look at the struts example application
(mailreader) for an example.
For detailed info on why this pattern works, see:
http://www.amazon.c
7 matches
Mail list logo