RPC Session Delays
The RPC session delay exceeds the critical value set in Expert Thresholds. The "session delay" metric combines network latency (i.e., the time spent waiting for data to traverse the network) and application processing time (i.e., the time spent waiting for the server or application to respond to a request). Application Response Time for RPC is tracked with a separate Expert Threshold.
Possible reasons for the event:
If application processing time is within reasonable limits, network latency must account for the bulk of the session delay. You should look for problems with the network. Do you have enough bandwidth between the application server and the clients that use it? Are the routers between the systems configured correctly?
If the Expert Threshold for application processing time is also being exceeded, the slowdown is probably the result of a server or application configuration issue. Perhaps the server hardware is overloaded with disk I/0 requests, or some other system component (for example, the CPU or NIC) is too slow given the traffic it is expected to handle.
The client and server that use RPC to communicate might also be a problem, either in the way that they have been configured by the user, or in the underlying source code.