At the moment when we use execandwait we¹re finding that that the production
thread doesn¹t even start until after the delay period is over. For example
I did a simple test with the following configuration:
<action name="view" class="viewAction" method="view">
<interceptor-ref name="standardAuthStack"/>
<interceptor-ref name="execAndWait">
<param name="delay">2000</param>
<param name="delaySleepInterval">50</param>
</interceptor-ref>
<result name="wait">/WEB-INF/pages/execAndWait.jsp</result>
<result name="success">/WEB-INF/pages/View.jsp</result>
</action>
>
The view action checks for the existence of legacy data and if it exists
retrieves it ad appends to the current data. If no legacy data exists the
action is done in no time, but if legacy data is present it can take up to a
couple of minutes to extract and combine.
I was of the impression the above configuration would skip the
execAndWait.jsp page if the thread was done within 2000 milliseconds with
a check every 50 milliseconds, but what actually happens is that the action
pauses for 2000 milliseconds and then starts the main thread, so we always
get the execandWait page. I tried increasing the delay to 10000 and the same
happens with just a 10 second delay.
I¹m hoping that I just haven¹t understood the configuration options, but I
haven¹t been able to find more detailed information.
Z.
>
> Zoran Avtarovski wrote:
>> > For what it¹s worth, the I18n and the execandwait areas are the two areas I
>> > find that S2 falls down the most.
>
> Do you have any specific suggestions for how execandwait should work?
>
> -Dale
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
> For additional commands, e-mail: user-h...@struts.apache.org
>
