Hi Wes, Thanks for that information. It helped to confirm the way I was thinking about the problem. It turns out that the customer has tried out a scenario in which they omit the "execAndWait" interceptor, and it appears to be working fine now with no new thread being created, so the crisis has been averted :)
On Tue, Oct 19, 2010 at 10:28 AM, Wes Wannemacher <[email protected]> wrote: > On Tue, Oct 19, 2010 at 8:07 AM, Phil Adams <[email protected]> wrote: > > Is there a reason why the customer's action is using the > ExecuteAndWaitInterceptor? I guess what I am saying is that I am hearing > conflicting information. You want the action to execute in the container's > request handling thread, but you are using exec&wait. You can't have both... > Remove the exec&wait interceptor from the action's interceptor stack and see > if you get the results you are looking for... However, (warning), if the > original developer configured the action to use exec&wait, he/she may have > had a reason and removing the interceptor may have unintended side effects. > > > -Wes > > -- > Wes Wannemacher > > Head Engineer, WanTii, Inc. > Need Training? Struts, Spring, Maven, Tomcat... > Ask me for a quote! > -- Phil Adams Cedar Park, TX --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
