| Title: | DCE Product Information |
| Notice: | Kit Info - See 2.*-4.* |
| Moderator: | TUXEDO::MAZZAFERRO |
| Created: | Fri Jun 26 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2269 |
| Total number of notes: | 10003 |
Under what conditions can an rpc_x_comm_failure error be returned ? We are seeing this occur after the application has been stable for some hours. The RPC client and server are on the same system and therefore I also doubt a network failure! Error always shows at client. Could this just be a certificate expiring and not being renewed in time ? This is Digital UNIX V4.0A with DCE V2.0A ECO1. Thanks for any insights. -gerry
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2225.1 | check in the server for problems | FOUNDR::WOODRUFF | Tue Apr 22 1997 14:43 | 9 | |
>Under what conditions can an rpc_x_comm_failure error be returned ? i've seen this error happen when there was a problem in the server code such as a thread termination due to some fault (though you normally get another error code). garry | |||||
| 2225.2 | check endpoints | TUXEDO::CHUBB | Wed Apr 23 1997 12:24 | 4 | |
You may also make sure that the endpoints in the endpoint database are
correct for the server.
-- brandon
| |||||
| 2225.3 | server could be busy | FOUNDR::WOODRUFF | Wed Apr 23 1997 15:48 | 10 | |
also, i did some checking -- this exception code can be produced if you are using a datagram protocol such UDP and the server is busy processing other requests. You might try to increase the number of listen threads for the server and see if you still get the error. garry | |||||
| 2225.4 | Fixed..thanks | MUFFIT::gerry | Gerry Reilly | Fri May 02 1997 10:27 | 6 |
RE: -.1 Increasing the number of listener threads appears to have fixed the problem. Thanks for the suggestion. -gerry | |||||