Home | The Company | Publications | Products | Links | Tips | Jobs |
---|
RPC Server - Troubleshooting - Time OutsLast update: 21 September 2008 |
QuestionIn a constellation .NET / Net-work / EntireX Broker / EntireX RPC Server, some of the RPC Servers on the mainframe terminate with the following message. What could cause the problem? ### TERMINATE MESSAGE M *** RC 3 from listen request. Server terminates 02150254 NET: Connection error subcode 30C00003 NAT9995 Natural session terminated normally. The Broker also displays the user-gone message. 05:16:12 XCO0053W 00212 MPM36-OK, USER GONE. 05:16:16 XCO0053W 00212 MPM36-OK, USER GONE. 05:17:59 XCO0053W 00212 MPM36-OK, USER GONE. The Broker is up and running because a 'ping' using another RPC Server was successful. Answer02150254: DB215 received RC254. This is similar as the Adabas response code 254 (CT parameter) Check the following:
See also http://tech.forums.softwareag.com, where this issue was discussed. Back to EntireX Tips, Tricks, Techniques -- Overview |