Quantcast
Channel:
Viewing all articles
Browse latest Browse all 43849

Wiki Page: Client got CORBA::OBJECT_NO_EXIST exception after restarting of server

$
0
0
Problem: Product Name: VisiBroker Product Version: 7.0 Product Component: ORB Platform/OS Version: All Client got CORBA::OBJECT_NOT_EXIST exception when calling a method after the client binds to the object which was hosted by a remote server. There were several CORBA servers running on the server machine. The directory service used is osagent, which was running on the server. This occurs intermittently after restarting of the server machine. Resolution: Result of analysis on the CORBA servers' and client's logs, it is revealed that the client bound to the server which did not host the object. Here is the scenario: client was invoking server process A listening at [addr=/111.222.333.444, port=49328] successfully. server machine (and its server processes) was restarted. Client invocation failed with CORBA::TRANSIENT exception. The reason is because A is no longer listening at [addr=/111.222.333.444,port=49328] . When server process B is started and on rare occassion, server process B is now listening at port 49328, the previous port used by server process A . After the rebind, the client thinks that it is invoking server process A at [addr=/111.222.333.444,port=49328] , however, this port is alreay taken over by server process B . Since server process B does not host the same objects as server process A , the former returns an OBJECT_NOT_EXIST exception. To prevent this, please specify the different listening port of each CORBA server by VisiBroker"s property vbroker.se.iiop_tp.scm.iiop_tp.listener.port , if thread pool model vbroker.se.iiop_ts.scm.iiop_ts.listener.port , if thread session model Author: Naoki Kawasumi Old KB# 30491

Viewing all articles
Browse latest Browse all 43849

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>