Anonymous | Login | Signup for a new account | 12-17-2024 10:53 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0004250 | [Resin] | minor | always | 10-07-10 15:57 | 01-10-11 14:30 | ||||
Reporter | emil | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | Platform | |||||
Status | closed | OS | |||||||
Projection | none | OS Version | |||||||
ETA | none | Fixed in Version | 4.0.14 | Product Version | 4.0.10 | ||||
Product Build | |||||||||
Summary | 0004250: AsyncListener.onComplete called at end of service(), not after AsyncContext.complete | ||||||||
Description |
(rep by baoqinye via forums) We are testing the Servlet 3.0 implementation in Resin 4.0.10 (open source version) here. We add one AsyncListener to the request's AsyncContext. When it's ready to send the response back, we call AsyncContext.complete(). What we noticed is that the AsyncListener.onComplete() method is actually called at the end of the doGet or doPost method rather than after AsyncContext.complete() is called. We performed the same test in Tomcat and Tomcat seems to handle it properly (AsyncListener.onComplete() is called after AsyncContext.complete() is called). |
||||||||
Steps To Reproduce | |||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
29 total queries executed. 26 unique queries executed. |