|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 4725 | minor | always | 08-24-11 10:08 | 08-26-11 11:24 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | urgent | OS Version: | |||
| Status: | closed | Product Version: | 3.1.6 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.22 | ||
|
|
|||||
| Summary: | 0004725: slow post limits | ||||
| Description: |
(rep by Santosh Rau) We saw a lot of slow clients dribbling in requests that day. So even if we use JNI libraries for the sockets, there is still a chance that we could exhaust the 200 threads we had. Is there any way we can protect our service from such clients other than keep increasing max threads? Would it be possible to break a connection if the request duration has taken over a preconfigured 'n' seconds? And finally, is it possible for you guys to add this to the 3.1.6 code? |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||