14 May 21:23
RE: Long time processing in the DwrServlet.service()
From: Mike Wilson <mikewse@...>
Subject: RE: Long time processing in the DwrServlet.service()
Newsgroups: gmane.comp.java.dwr.user
Date: 2008-05-14 19:23:58 GMT
Expires: This article expires on 2008-05-28
Subject: RE: Long time processing in the DwrServlet.service()
Newsgroups: gmane.comp.java.dwr.user
Date: 2008-05-14 19:23:58 GMT
Expires: This article expires on 2008-05-28
> 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(); Ah yes, my bad. It's the HttpServletRequest I was thinking about so use req.getPathInfo(). > 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. Yes, and also please count in error/exception callbacks as this may signal any error code returns. Best regards Mike
RSS Feed