Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
From: bugzilla@apache.org
To: dev@tomcat.apache.org
Subject: [Bug 53337] IllegalStateException when trying to render a JSP after
 startAsync
Date: Sun, 03 Jun 2012 15:58:09 +0000
Message-ID: <bug-53337-78-5w9U5z5yD9@https.issues.apache.org/bugzilla/>
In-Reply-To: <bug-53337-78@https.issues.apache.org/bugzilla/>
References: <bug-53337-78@https.issues.apache.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Auto-Submitted: auto-generated
MIME-Version: 1.0

https://issues.apache.org/bugzilla/show_bug.cgi?id=53337

Mark Thomas <markt@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #6 from Mark Thomas <markt@apache.org> ---
The bug (forwarding to an async servlet always failed) has been fixed in trunk
and 7.0.x and will be included in 7.0.28 onwards.

Re-reading the spec, it appears that the intention was that dispatches from an
async thread should always be via the AsyncContext. No mention is made of
dispatching via a RequestDispatcher. This is going to be one of those grey
areas that different containers do different ways. I believe - but haven't
tested to check all the edge cases - that in Tomcat the two would be equivalent
based on which objects Tomcat uses internally. Other containers may well be
different.

My personal recommendation would be to stick with dispatching via the
AsyncContext.

-- 
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