-60 INF TIMEOUT (Magic xpa 2.x)
This error can occur in several low-level scenarios. In each scenario, it will be handled differently. For example:
A requester submits a request to the broker for an unsupported application, which does not exist, error -103; or is busy, error -104. The broker issues an acknowledgement message, and the requester continues to wait for an available enterprise server, according to the BrokerTimeout value in the Mgreq.ini file or its equivalent in the Servers table of the Magic.ini file. If no enterprise server becomes available in the specified period of time, the requester receives status -60 from the TCP/IP layer, which is then handled as status code -103 or -104.
A requester submits a request to the broker and does not receive any response from the broker, which is handled as error -105.
A requester contacts an enterprise server, submits a request to the enterprise server, and begins to wait for the response. If a Requester timeout was set and the enterprise server did not complete the request, the requester receives status -60 from the TCP/IP layer, which is then handled as status -110 (REQUEST-TIMEOUT).