If you get these errors in Plugin logs
ERROR: ServerIOTimeout fired. Time out 60. retry count 0. serverIOTimeoutRetry -1, retry YES, rc 10
The above error is due to low value of ServerIOtimeOut.
ServerIOtimeOut plugin property explanation from IBM:
The ServerIOTimeout attribute of a server element enables the
plug-in to set a time out value, in seconds, for sending requests
to and reading responses from the application server.
If you set the ServerIOTimeout attribute
to a positive value, this attempt to contact the server ends when
the timeout occurs. However, the server is not considered to be down
and future requests are still sent to the server on which the timeout
occurred..
If you set the ServerIOTimeout
attribute to a negative value, the server is considered to be down
whenever a timeout occurs, and no future requests are sent to the
server on which the timeout occurred.
If a value
is not set for the ServerIOTimeout attribute, the plug-in, by default,
uses blocked I/O to write requests to and read responses from the
application server, and does not time out the TCP connection. For
example, you might specify the following setting:
For example,
you might specify the following setting:
<Server Name="server1" ServerIOTimeout=300>
In
this situation, if an application server stops responding to requests,
the plug-in waits 300 seconds (5 minutes) before timing out the TCP
connection. Setting the ServerIOTimeout attribute to a reasonable
value enables the plug-in to time out the connection sooner, and transfer
requests to another application server when possible.
When
selecting a value for this attribute, remember that sometimes it might
take a couple of minutes for an application server to process a request.
Setting the value of the ServerIOTimeout attribute too low could cause
the plug-in to send a false server error response to the client.
Important: The ServerIOTimeout limits the amount
of time the plug-in will wait for each individual read or write operation
to return. ServerIOTimeout does not represent a timeout for
the overall request.
Increase the ServerIOtimeout value to solve the above issue.
