|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 4250 | minor | always | 10-07-10 15:57 | 01-10-11 14:30 | |
|
|
|||||
| Reporter: | emil | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 4.0.10 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.14 | ||
|
|
|||||
| 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: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||