There is a limit to the number of connections that can be established between the RAP-processing client and the RAP-processing server. If calling the function dc_rpc_call() causes the number of connections to exceed this limit, OpenTP1 automatically releases the least recently used connection among those used by the RAP-processing client process, and then establishes a new connection.

However, OpenTP1 cannot release a connection which is being used by a chained RPC. When OpenTP1 cannot release any connection due to this restriction, the UAP that issued the API goes down.

The running of a chained RPC may encounter one of the following events: the calling of the function dc_rap_disconnect() and failure or communication error of the UAP that issued the API function. In such a case, the RAP-processing server that is performing remote execution of the API terminates abnormally and restarts. The purpose of this momentary termination is to reset the connection with the SPP that is processing the chained RPC and clear the status.