RE: Long time processing in the DwrServlet.service()

> MW> You need to provide a lot more information about your scenario:
> MW> - DWR version?
> Oops. Forgot to write. dwr-2.0.3

There have been some small changes to thread wake-up for 2.0.4 so you
could try the Release Candidate 1 at
https://dwr.dev.java.net/servlets/ProjectDocumentList?folderID=9081

>           StatisticManager.addValue(request.getPath(), duration);

Nice explanation of your tests, and yes they make sense I think.
Use
  request.getPathInfo()
instead of getPath() in your next deploy as this is the value that
DWR bases its decisions on. Just to be sure.
(See UrlProcessor.handle)

That's interesting. I wonder if DWR somehow could be picking up the
wrong handler for these 105 calls, and this is when you see the delay
(would make sense with the Avg time you are seeing). Normally your
Client.send calls should be routed through PlainCallHandler.

It would be interesting to see the response data being returned
for these delayed requests. It would be great if you could use
Wireshark or some other HTTP tracer to examine this.

You could also make your JavaScript code count the number of
successful callback returns and error/exception callback returns
resulting from your Client.send.

> MW> - Could you be hitting the Two Connections Limit?
> Certainly I could, but it is client side issue, but we have long time
> processing request in server side. Am I right?

Yes, with the information you have now provided it seems this should
not be the cause of your problem.

Best regards
Mike

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...