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

> MW> I would suggest you try your application in a regular 
> servlet engine,
> MW> like f ex Tomcat or Jetty, and report back if you still have any 
> MW> problems. Reproducing your error in a "standard" 
> environment will make
> MW> it much easier for other developers on the list to help you.
> 
> Certainly it will be good, but unfortunately, I have not chance to do
> it easily. And it is why I ask you for ideas (potential solutions)
> about reason why/where DwrServlet keeps (can keep) request for a long
> time. And have not chance to debug it because of it is hard to
> reproduce this issue locally (with good network connection).

Ok, but be aware that you will get less help with an unknown 
environment. It could be helpful if you deployed some of the DWR demo 
apps on your custom environment, to see if you get the same problem 
there (that would rule out one unknown variable = your application).

> I have no ideas how to localize the problem in a short term and why
> processing time the same with Comet request maximum connection time.

You need to provide a lot more information about your scenario:
- DWR version?
- Which request are you talking about? (Originating from a call on
  a JavaScript proxy object or from a DWR Reverse Ajax poll?)
- Describe more about the call that you are timing, sequence of
  operations, normal behaviour and expected times.
- Can you snoop and provide a HTTP log from when the problem appears?

Also think about this:
- DWR's Reverse Ajax request is designed to "hang" in the server
  for one minute when in Full Streaming Mode. Is this what you are
  seeing?
- Can you try the app with Reverse Ajax disabled, or try other 
  Reverse Ajax modes (Early Closing, Polling) ?
- Could you be hitting the Two Connections Limit?

> Maybe it is question to the developer mailing list, not sure...

No, the user list is appropriate for this.

> MW> BTW: What is your impression of Simple framework? (There 
> doesn't seem
> MW> to have been much activity the last years.)
> 
> Simple framework was an engine of the original application I started
> to support/rebuild several months ago. So, Simple framework was
> inherited from previous developers. But, as for me, it is a good
> solutions for project where you have a lot of _small_ requests to
> server. For example, JBoss creates separate thread for every
> connection and it is rather expensive operation if you have a lot of
> small AJAX requests from 1000 and more clients.

Yes, that makes sense. Although, JBOSS bundles Tomcat and Tomcat 6
supports non-blocking I/O which gets rid of the thread-per-connection
problem.

> Simple framework provides the article with comparisons of Simple's
> vs Apache and Resin. 
> http://www.simpleframework.org/performance/comparison.php

Yes, I saw this article but all the software versions are quite
outdated so it would be interesting to see a comparison with modern
versions like Apache 2.2 Event MPM, Tomcat 6 NIO, etc.

Best regards
Mike