|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 3630 | minor | always | 08-07-09 14:30 | 09-11-09 18:15 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 3.1.6 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.2 | ||
|
|
|||||
| Summary: | 0003630: ClientDisconnect with Comet servlet | ||||
| Description: |
(rep by Fiaz Hossain) I am using the CometServlet in Resin 3.1.6 and ResinPro. It seems like when I am using the JNI library from Pro the server is not getting any indication of when the client has disconnected. In partcular the call - controller.isClosed() never returns true even when the client has gone away. We have noticed similar issues with Regular servlet code too where the server keeps on writing data to an outputstream without any error when the client has actually terminated the connection. Seems like the IOException is being trapped and ignored even when I have the following specified <ignore-client-disconnect>false</ignore-client-disconnect> If I take the JNI library out we seem to get the IOException properly. Is there something wrong with the way we built the JNI library? |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |