Difference between revisions of "Talk:FAQ:Applications 04"
(Another cause for the "agent does not respond" symptom) |
|||
| Line 4: | Line 4: | ||
As a special case, is it also possible that the client retransmits its request after time-out, so the agent, which was already very slow, becomes even slower because it needs to process new requests while it has not yet processed the previous requests. Is this possible? | As a special case, is it also possible that the client retransmits its request after time-out, so the agent, which was already very slow, becomes even slower because it needs to process new requests while it has not yet processed the previous requests. Is this possible? | ||
| + | |||
| + | :You're absolutely right that this information should be added to the page. Feel free to add it! [[User:Wes|Wes]] 14:24, 10 December 2008 (UTC) | ||
Latest revision as of 14:24, 10 December 2008
To diagnosis the "why doesn't the agent respond" problem, I belief that the problem is more delicate than is explained here - but please correct me if I'm wrong.
Another possible cause is that the client has requested something that takes the agent relatively long to process. For instance, the client has requested a GETBULK, and/or the agent is running on a poor CPU, and/or ..... In such case, the client times out the response, after which it receives the response (too late). The user may observe this as "the agent does not respond", while in fact the agent is too slow, or the timeout is too small. To solve this, improve the agent speed, or lower the timeout of the client.
As a special case, is it also possible that the client retransmits its request after time-out, so the agent, which was already very slow, becomes even slower because it needs to process new requests while it has not yet processed the previous requests. Is this possible?
- You're absolutely right that this information should be added to the page. Feel free to add it! Wes 14:24, 10 December 2008 (UTC)
