Re: [WebMacro-user] [WebMacro-user

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

<html><body>Hi Nikolaos. 
 
This is most disturbing to hear about. 
 
First, there is a known concurrency issue with WM in 2.0 and possibly
in prior releases. If you look at the mail thread dating back for 45
days, you will definitely see it. 
 
My concern is that the webmacro instance, shared, and the context, not
shared, is improperly orchestrated for concurrency. The webmacro
instance is local to WMServlet. You might consider synchronizing access
to this variable as a trial fix in your local calls below. This will
introduce some serialization of web processing but it might help to
verify the solution. 
 
One thing you might consider trying is to use a different cache
handler. A few years ago, I wrote one and it is a part of the distro. I
have never had a problem using this cache handler. 
 
Lane --- Nikolaos Papadakis &lt;nk...@cc...&gt; wrote: <=
br>From: Nikolaos Papadakis &lt;nk...@cc...&gt; Date: Sat, 18 F=
eb 2006 10:50:33 +0200 To: web...@li... Subjec=
t: [WebMacro-user] [WebMacro-user Hi all, I am using webmac=
ro to develop a web-based application. Things seemed to work fine till =
yesterday. A customer complained that he managed to =E2=80=9Csee=E2=80=
=9D the account of another customer when he logged-in using his own cr=
edentials (he send me a screen shot of the =E2=80=9Cview=E2=80=9D). By =
inspecting the log file I found that both users have been logged-in at=
 the same time (the second customer logged in 3 sec after the first cu=
stomer). The system has more than 1000 customers but this inconvenience=
 happened for the first time yesterday (?). It seems that differen=
t sessions have been mixed up. The servlet includes a handle method and=
 uses several other methods (methods that write and read from a databa=
se). All methods are defined in the same class (that extends WMServlet)=
. As far as I know servlets must not have instance variables (only loca=
l variables -inside methods- to prevent data corruption and incon=
sistencies). However in my servlet I use only one non local variable (=
a Logger) and I don't think this is the cause of the problem. As an att=
ached file I send you a fragment of the before mentioned servlet. Can i=
nstance variables be defined in the case of a servlet that extends WMS=
ervlet? (I mean is it safe? or its not a good practice without keeping=
 precautions?) Do you have any idea what can have caused this inconveni=
ence ? Is the use of methods inside the servlet thread-safe ? =
Please help!!! Nikolaos Papadakis </body></html>