I have been through this before. Its more like 2 client requests in
succession/ The session seems to be locked at some point in time and the
other request keeps on waiting for ever. Once I made the underlying servlet
implement single thread model it went away. Iam not sure about it in a
struts environment but this is a well known case.
But experts advise against single thread model usage(A different topic
anyway..)
The Jguru page had the same problem in the very beginning (They use jsp's).
But they somehow unlocked the session and made it attend the second request
too. As a consequence every bit of jsp content appeared twice on the page.
later
pathangi r
-----Original Message-----
From: Gogineni, Pratima [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 16, 2001 1:44 PM
To: '[EMAIL PROTECTED]'
Subject: thread problems?
Hi,
I have been fighting with the following situation and would appreciate any
ideas/suggestions.
I have a session scoped form bean "FBean", a jsp page that displays it
"dispFBean" & an action FBeanAction.
I have inserted transactional tokens to take care of duplicate posting.
After changing a value in dispFBean, an enter or/and a click work fine &
they do the same thing ie. call FBeanAction.
when the 2 events are done in rapid succession - one event executes fine
while the other event throws an exception because it is trying to access
row#5 where as the previous action changed the number of rows to 4.
Unfortunately the transactional tokens cant take care of this since this
error is being thrown in BeanUtils.populate before it ever reaches an
FBeanAction instance.
I also tried declaring the jsp page threadsafe to check if that is the
problem.
Also note that the FBeanAction replaces FBean with a new Instance of FBean.
Thanks
Pratima
