How can agents prevent message and/or connection rejection?
An agent can decrease the number of messages it rejects by increasing the size of its message buffer. Similarly, it can increase its connection buffer to reduce the number of connections it rejects. Increasing buffer sizes can make sense for service-providing agents, that potentially have to cope with bursts in the requests they receive. Although it is possible to give agents “infinitely” sized message and/or connection buffers, this should not be done except maybe for debugging. With infinite buffer sizes, there is no protection against overload. Latency can go up unacceptably and the system can run out of memory. See also #WhyMessageAndConnectionRejection.
Related Questions
- When I try to use sftp or scp2, I get a message like this: Received message too long (or "Bad packet length") 1416586337 and the connection fails. Whats wrong?
- What does the error SMTP data timeout (message abandoned) on connection from... mean?
- How should agents cope with message and/or connection rejection?
