Bug 53632 - The DispatchType is INCLUDE instead of ASYNC after a dispatch via AsyncContext
Summary: The DispatchType is INCLUDE instead of ASYNC after a dispatch via AsyncContext
Status: RESOLVED DUPLICATE of bug 53623
Alias: None
Product: Tomcat 7
Classification: Unclassified
Component: Catalina (show other bugs)
Version: 7.0.29
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
Depends on:
Reported: 2012-07-31 15:49 UTC by Rossen Stoyanchev
Modified: 2012-08-14 20:43 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Rossen Stoyanchev 2012-07-31 15:49:55 UTC
Code demonstrating the issue:

Checkout the 'tomcat-issue-repro' branch. From the home page of the deployed application, select the "Dispatch via AsyncContext" scenario. The scenario involves ServletA forwarding to ServletB and ServletC, which in turn creates a thread and dispatches to ServletD. The DispatchType in ServletD should be ASYNC but is INCLUDE instead.

FWIW when the request is wrapped (scenarion "Dispatch via AsyncContext and wrap request"), the DispatchType is correct.
Comment 1 Mark Thomas 2012-08-14 20:43:39 UTC
I assume at some point the debug logging was outputting the result of request.getDispatchType(). The version provided doesn't do this but I have added the line to do this in my local copy.

This issue has the same root cause as bug 53623 so I am marking it as a duplicate since it is really just a different symptom of the same underlying problem.

*** This bug has been marked as a duplicate of bug 53623 ***