tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 53337] New: IllegalStateException when trying to render a JSP after startAsync
Date Thu, 31 May 2012 17:06:36 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=53337

          Priority: P2
            Bug ID: 53337
          Assignee: dev@tomcat.apache.org
           Summary: IllegalStateException when trying to render a JSP
                    after startAsync
          Severity: normal
    Classification: Unclassified
                OS: Linux
          Reporter: rstoyanchev@yahoo.com
          Hardware: PC
            Status: NEW
           Version: 7.0.27
         Component: Catalina
           Product: Tomcat 7

The scenario involves:

1. ServletA forwards to Servlet B
2. ServletB calls request.startAsync and starts thread
3. New thread attempts to render a JSP

I've tried JSP rendering via asyncContext.dispatch("") and via
request.getRequestDispatcher("") plus forward or include.

When using a RequestDispatcher, calling ServletA fails while calling ServletB
directly succeeds. 

When using AsyncContext.dispatch, both ServletA and ServletB fail.

The exception is always the same (while attempting to render the JSP):

java.lang.IllegalStateException: Cannot create a session after the response has
been committed

I've created a project at:
https://github.com/rstoyanchev/dispatch-test

The project page contains instructions and attached is a .war although you
might want to check the source out in order to try a couple of variations.

Beyond the specifics of the bug, the more general question is whether it is ok
to use request.getRequestDispatcher from an async thread? That seems to be the
case in Tomcat, aside from this bug, but in other containers (Jetty in
particular) it's clearly not recommended. 

Servlet Spec discussion on this question: 
http://java.net/projects/servlet-spec/lists/users/archive/2012-05/message/10.

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message