Anonymous | Login | Signup for a new account | 12-17-2024 11:33 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0005121 | [Resin] | minor | always | 06-14-12 11:18 | 06-19-12 16:13 | ||||
Reporter | cowan | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | Platform | |||||
Status | closed | OS | |||||||
Projection | none | OS Version | |||||||
ETA | none | Fixed in Version | 4.0.29 | Product Version | 4.0.28 | ||||
Product Build | |||||||||
Summary | 0005121: server-default socket-timeout is ignored | ||||||||
Description |
<cluster id="app-tier"> <server-default> <socket-timeout>60s</socket-timeout> </server-default> socket-timeout is never used. I believe ClusterServer.createClusterPool purposely uses cluster-idle-time for the read timeout, and NetworkClusterSystem.startClusterListener uses cluster-idle-time + padding for the listen timeout. __This may be documentation fix only!__ |
||||||||
Steps To Reproduce | |||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
Notes | |
(0005894) ferg 06-19-12 16:13 |
See 0005022. The configuration item is cluster-socket-timeout, and should normally not be changed. |
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
30 total queries executed. 27 unique queries executed. |