Could this be related to WW-1816 FitlerDispatcher not always calling ActionContextCleanUp.cleanUp(Request)?
--- John M Flinchbaugh <[EMAIL PROTECTED]> wrote: > Synopsis: > FilterDispatcher may not cleanup completely and causes the > StrutsRequestWrapper to be omitted in some executions (race condition). > Adding ActionContextCleanUp filter seems to alleviate the issue. As > advertized, I'd expect FilterDispatcher to be able to function on its > own. > > Long story: > In a previous message (which I linked/included below), I expressed my > trouble with accessing values from the ValueStack from JSP 2.0 EL. Upon > reloading, the EL values would come back null sometimes, and other times > populated. > > After a bit of debugging, I found that the StrutsRequestWrapper was not > always being wrapped around the request object we get from tomcat. When > this was missing, I'd obviously not have access to the value stack. > > It seemed to be a bit of a race condition where the FilterDispatcher > would decide we already had a Dispatcher (du) object (see > FilterDispatcher, line 311). Firefox requesting both the action and the > stylesheet (2 requests) seemed to trigger the race where one request > would initialize the null Dispatcher (possibly incompletely clean it up), > and the other request would get the old Dispatcher instance so it > would just proceed with the unwrapped request object. > > I was using the FilterDispatcher by itself, and I think it may have > failed to cleanup everything for itself and sometimes that incomplete > Dispatcher would leak into the other request. > > When I added the ActionContextCleanUp filter to the web.xml, the > StrutsRequestWrapper seems to be used reliably. > > -- > John M Flinchbaugh > [EMAIL PROTECTED] __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
