Re[2]: Long time processing in the DwrServlet.service()

Greetings, Mike

Could it be the same issue with
http://www.nabble.com/Dwr-2.0.3,-reverseAjaxEnabled-and-IE6-td16031191.html

>> MW> Use  request.getPathInfo() instead of getPath() in your next
>> MW> deploy as this is the value that DWR bases its decisions on. Just
>> MW> to be sure. (See UrlProcessor.handle)
>>
>> There is no equest.getPathInfo() in simple. And it returns in the
>> Adaptor between simple and servlet APIs.
>> 
>> Hm.. I will check the req.getPathInfo();

MW> Ah yes, my bad. It's the HttpServletRequest I was thinking about
MW> so use req.getPathInfo().

I did, but the situation is the same. The PathInfo() is correct.

>> MW> You could also make your JavaScript code count the number of 
>> MW> successful callback returns and error/exception callback returns
>> MW> resulting from your Client.send.
>> 
>> Ok, yes. it should give us new information. I will add the 
>> counter to the
>> JavaScript and counter of request with duration more than 30 sec and
>> will compare them.

MW> Yes, and also please count in error/exception callbacks as this may
MW> signal any error code returns.

I did the number of errors in the client side = number of long time
requests. Where target method is not executed.

--

-- 
Best regards,
Dmitry Kudrenko
ARDAS group (http://www.ardas.dp.ua)