| Anonymous | Login | Signup for a new account | 04-26-2024 06:47 PDT |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0001939 | [Resin] | minor | always | 08-13-07 16:19 | 09-06-07 10:43 | ||||
| Reporter | ferg | View Status | public | ||||||
| Assigned To | ferg | ||||||||
| Priority | normal | Resolution | fixed | ||||||
| Status | closed | Product Version | 3.0.23 | ||||||
| Summary | 0001939: load balancer timeouts | ||||||||
| Description |
(rep by Bradley Van Cleave) We made these changes on the Load Balancer, but we are still seeing the Broken Pipe Exception in the logs. <!-- Did not change value --> <client-read-timeout>120s</client-read-timeout> <!-- Added value --> <client-live-time>135s</client-live-time> <!-- Added read-timeout --> <srun server-id="..." host="..." port="6880" read-timeout="180s"/> <srun server-id="..." host="..." port="6880" read-timeout="180s"/> I didn't change the value for the client-read-timeout. Should this value be the same as the client-live-time? I didn't see any large GCs. |
||||||||
| Additional Information | |||||||||
| Attached Files | |||||||||
|
|
|||||||||
 Relationships |
|
| There are no notes attached to this issue. |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 08-13-07 16:19 | ferg | New Issue | |
| 09-06-07 10:43 | ferg | Assigned To | => ferg |
| 09-06-07 10:43 | ferg | Status | new => closed |
| 09-06-07 10:43 | ferg | Resolution | open => fixed |
| 09-06-07 10:43 | ferg | Fixed in Version | => 3.1.3 |
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
26 total queries executed. 24 unique queries executed. |  |
