Ted Goddard added a comment - 21/Jan/11 12:22 PM Looks like Tomcat 7 fails in the same way as GlassFish 3.0.1.

Mircea Toma added a comment - 26/Jan/11 5:13 PM Indeed ICEpush with Tomcat 7.0 and async. support enabled does not work. The responses on the blocking connection seem to have the correct content (fixed sized), but the content is marked as 'chunked' which confuses the browser.

Mircea Toma added a comment - 01/Feb/11 5:16 PM - edited The reason why ICEpush fails in Tomcat 7.06 is due to the HTTP headers missing in the blocking connection response. To find out more about how Tomcat 7 works I devised a simple test, a servlet that parks the request and then after 5 seconds responds. Setting the headers just before the response is sent does not succeed in actually sending the headers over the wire: protected void doGet(HttpServletRequest request, final HttpServletResponse r) throws ServletException, IOException { final AsyncContext ctx = request.startAsync(); ctx.start(new Runnable() { public void run() { try { Thread.sleep(5000); r.setHeader("bla", "fffff"); r.setContentType("text/plain"); r.setContentLength("------".getBytes().length); r.getWriter().print("------"); ctx.complete(); } catch (Exception e) { e.printStackTrace(); //To change body of catch statement use File | Settings | File Templates. } } }); } Setting the headers on the request thread before or after the AsyncContext is acquired succeeds in sending the headers over the wire: protected void doGet(HttpServletRequest request, final HttpServletResponse r) throws ServletException, IOException { final AsyncContext ctx = request.startAsync(); r.setHeader("bla", "fffff"); r.setContentType("text/plain"); r.setContentLength("------".getBytes().length); r.getWriter().print("------"); ctx.start(new Runnable() { public void run() { try { Thread.sleep(5000); ctx.complete(); } catch (Exception e) { e.printStackTrace(); //To change body of catch statement use File | Settings | File Templates. } } }); }

Ken Fyten added a comment - 03/Feb/11 4:44 PM Need to see if there's a Tomcat bug issue reported for this, and if not, report it.

Ted Goddard added a comment - 08/Feb/11 1:17 PM Setting the contentType prior to async operations seems to fix the problem: response.setContentType("text/xml"); asyncContext = request.isAsyncStarted() ? request.getAsyncContext() : request.startAsync();

Ted Goddard added a comment - 08/Feb/11 2:40 PM Since the contentType can likely be set twice, the recommended fix is to call setContentType as above, then rely on re-setting it in other cases. This will at least have the effect of supporting Servlet 3.0 except under error conditions.

Ted Goddard added a comment - 08/Feb/11 2:43 PM The current Tomcat implementation may be expecting that the headers are set prior to the return of the original service() method.

Mircea Toma added a comment - 09/Feb/11 4:18 PM Set default text/xml content type to workaround Tomcat's limitation (headers are sent only when added on the request thread).

Mircea Toma added a comment - 10/Feb/11 11:49 AM Issue recorded in Tomcat's bug tracking system: https://issues.apache.org/bugzilla/show_bug.cgi?id=50753

Mircea Toma added a comment - 10/Feb/11 3:54 PM Looks like the issue was already fix in Tomcat 7.0.8 version.