|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 1190 | major | random | 06-10-06 19:44 | 06-29-06 14:24 | |
|
|
|||||
| Reporter: | mpavel | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | urgent | OS Version: | |||
| Status: | closed | Product Version: | 3.0.18 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.0.20 | ||
|
|
|||||
| Summary: | 0001190: random 503 error codes | ||||
| Description: |
Have the following configuration: 4 RedHat AS 2.1 servers running apache 2.0.48 on the front-end (mod_caucho) and 2 RedHat AS 4.0 servers running resin 3.0.18 on the backend. We recently upgraded from resin 2.1.5 to 3.0.18 and started seing random 503 errors in apache logs. The errors do not seem to be correlated to load on the servers or any specific activity. Any help would be appreciated. |
||||
| Steps To Reproduce: | |||||
| Additional Information: |
from resin.conf on the backend: <thread-pool> <!-- Maximum number of threads. --> <thread-max>400</thread-max> <!-- Minimum number of spare connection threads. --> <spare-thread-min>25</spare-thread-min> </thread-pool> <keepalive-max>350</keepalive-max> <keepalive-timeout>120s</keepalive-timeout> <cluster> <client-live-time>110s</client-live-time> <client-read-timeout>120s</client-read-timeout> <client-dead-time>10s</client-dead-time> <srun id="a" host="10.24.217.1" port="6802" index="1" tcp-no-delay="true" read-timeout="120s"/> <srun id="b" host="10.24.217.2" port="6802" index="2" tcp-no-delay="true" read-timeout="120s"/> </cluster> |
||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||
|
|
|||||
|
|
||||
|
|
|||||
|
|
||||