Hello,
Your posts helped a lot. Thanks everybody!
Now I have a production level asynchronous servlet (a Santa Claus'
gift?), and I want to share some technical learned lessons:
- You must ensure the response be commited before asynchronous writes,
say on the BEGIN event, as said Filip and
ffd wrote:
I found the origin of the problem in my case. The problem was neither the
synchronization nor the connection gone. It was that the asynchronous
writing started too early, before the connection was completely established,
speaking losely...
just call response.flushBuffer() on the
I found the origin of the problem in my case. The problem was neither the
synchronization nor the connection gone. It was that the asynchronous
writing started too early, before the connection was completely established,
speaking losely...
When I made sure that the writing starts *after* all
