Mantis - Resin
|
|||||
Viewing Issue Advanced Details | |||||
|
|||||
ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
2264 | minor | always | 12-18-07 12:17 | 01-07-08 13:00 | |
|
|||||
Reporter: | sam | Platform: | |||
Assigned To: | ferg | OS: | |||
Priority: | urgent | OS Version: | |||
Status: | closed | Product Version: | 3.0.25 | ||
Product Build: | Resolution: | fixed | |||
Projection: | none | ||||
ETA: | none | Fixed in Version: | 3.0.26 | ||
|
|||||
Summary: | 0002264: isapi_srun timeout and 503 issues | ||||
Description: |
(rep by T Fukuda) I am having urgent troubles on 3.0.25. These problems have been marked fixed, but they are still occurring for me. It is necessary for them to be fixed in the 3.0 branch. (1) I can't set timeout value to more than one hour. <cluster> <client-read-timeout>8000s</client-read-timeout> <srun server-id="APP:192.168.108.28:6802" host="192.168.108.28" port="6802" index="1"/> </cluster> (2) IIS is not getting a 503 when a conneciton times out. <cluster> <client-read-timeout>1800s</client-read-timeout> <srun ... > <write-timeout>1810s</write-timeout> </srun> << Case of using IIS ... NG >>> The time-out was occurred 1800 seconds later. But, the server DID NOT return 503. (disconnected by the server) <<< Case of using Apache ... OK >>> The time-out was occurred 1800 seconds later. And the server returned 503. |
||||
Steps To Reproduce: | |||||
Additional Information: | |||||
Relationships | |||||
Attached Files: |
There are no notes attached to this issue. |