On 9/6/05, Leon Rosenberg <[EMAIL PROTECTED]> wrote: > > Heh :-) > > It explains some ugly side-effects I've seen from time to time in last > years > with struts, but never bothered to investigate. > However, we actually do have application hang-ups because of > thread-unsafity > of session.getAttribute() / session.setAttribute(). > It also seem possible to hang a webapp (not our:-)) just by hitting f5 > (reload) quick enough. > I understand that this is a tomcat (or JSP Spec) issue, rather than > struts, > but struts could at least provide thread-safe methods for attribute > handling > in actions and taglibs (and it would be about 20 lines of code...).
If your servlet container has a broken implementation of get/set attributes on an HttpSession, there is nothing that Struts can do to protect you from problems ... even providing synchronized locks around get/set calls would still not avoid problems caused by application logic, or logic inside the container itself, that would bypass it. Sounds like you need to get after the folks providing your container to fix this. Regards > Leon Craig > -----Ursprüngliche Nachricht----- > > Von: Martin Cooper [mailto:[EMAIL PROTECTED] > > Gesendet: Mittwoch, 7. September 2005 00:16 > > An: Struts Developers List > > Betreff: Re: How ThreadSafe are struts-taglibs, or do we want > > them threadsafe? > > > > On 9/6/05, Leon Rosenberg <[EMAIL PROTECTED]> wrote: > > > > > > I just looked through 1.27 and 1.3 taglibs, and they aren't > > > threadsafe, or I don't see it. > > > > > > Question: > > > Is it my personal issue, or is someone else worried that bean:write > > > can hang the application? > > > > > > Or is there really a problem? ;-) It's been the way it is for > > about 5 years now, and I don't recall a bug submitted against > > this before. But we'd definitely like to know about it if > > there really is a problem. > > > > -- > > Martin Cooper > > > > > > regards > > > Leon > > > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
