|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 3294 | minor | always | 01-23-09 09:18 | 10-29-09 16:02 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 3.2.1 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.2 | ||
|
|
|||||
| Summary: | 0003294: comet timeout issues | ||||
| Description: |
(rep by Caleb Richardson) We're considering using Resin's comet implementation in an HTTP idle scenario (probably 30 minute wait period), where an HTTP client creates a connection and then waits up to 30 minutes for a response. I understand that one of the idle connections takes up a socket on the server but not a thread. However, does this mean that the server will never receive a close event from the client (since nothing is blocking on read)? If this is the case, then any background worker threads (spawned by me) responsible for calling CometController#wake will continue to work on behalf of that connection until the wait period is up. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |