Getting OBJECT_NOT_EXIST exception when binding from an Orbix 6 client to an Orbix 3 server.

Dominique Sacre · 2013-05-17T17:43:00+00:00

Summary Getting OBJECT_NOT_EXIST exception when binding from an Orbix 6 client to an Orbix 3 server. Article Number 13334 Environment The server IOR is valid. The server is correctly registered at the Orbix daemon. All Supported Operating Systems Orbix 6.x Orbix 3.x Question/Problem Description Orbix 6 client raises CORBA.OBJECT_NOT_EXIST when trying to invoke on Orbix 3.3 server.Orbix 6 client fails to invoke on Orbix 3 server withIDL:omg.org/CORBA/OBJECT_NOT_EXIST:1.0: minor = 0x49540100 (IT_Core:OBJECT_NOT_FOUND), completion status = NOOrbix 6 client cannot invoke on Orbix 3 server. Clarifying Information Error Message Defect/Enhancement Number Cause An Orbix 3 client will always send the CORBA principal along with the request. Orbix 5 and Orbix 6 implement the CORBA 2.4 specification where principals are already deprecated. As a result, they don’t send any principal information by default.If a request to invoke on a particular server arrives at the Orbix 3 daemon, the daemon will also check if the sender has appropriate permissions to invoke or launch the server. Unless other users are explicitly allowed to invoke on the server, only the user under which the daemon runs, will be allowed.As Orbix 6 clients do not send any principal information, the request will be rejected by the daemon. Resolution Run the following commands chmodit l all <registered_server_name> chmodit i all <registered_server_name> in order to grant access to the Orbix 3 server to everyone. The Orbix 6 client will then be able to invoke on and launch the Orbix 3 server. The settings can be verified by running catit <registered_server_name> If this does not help to resolve the OBJECT_NOT_EXIST exception in the Orbix 6 client, then also check solution P149338: "Trying to invoke on Orbix 3 server from Orbix 6 client raises OBJECT_NOT_EXIST error in client" Workaround Notes Attachment Created date: 06 September 2011 Last Modified: 13 February 2013 Last Published: 23 June 2012 First Published date: 09 September 2011 #Orbix#KnowledgeDocs

Forum|Forum|12 years ago
May 17, 2013
0 replies
0 views

D

Dominique Sacre
Rocketeer

Summary	Getting OBJECT_NOT_EXIST exception when binding from an Orbix 6 client to an Orbix 3 server.
Article Number	13334
Environment	The server IOR is valid. The server is correctly registered at the Orbix daemon. All Supported Operating Systems Orbix 6.x Orbix 3.x
Question/Problem Description	Orbix 6 client raises CORBA.OBJECT_NOT_EXIST when trying to invoke on Orbix 3.3 server. Orbix 6 client fails to invoke on Orbix 3 server with IDL:omg.org/CORBA/OBJECT_NOT_EXIST:1.0: minor = 0x49540100 (IT_Core:OBJECT_NOT_FOUND), completion status = NO Orbix 6 client cannot invoke on Orbix 3 server.
Clarifying Information
Error Message
Defect/Enhancement Number
Cause	An Orbix 3 client will always send the CORBA principal along with the request. Orbix 5 and Orbix 6 implement the CORBA 2.4 specification where principals are already deprecated. As a result, they don’t send any principal information by default. If a request to invoke on a particular server arrives at the Orbix 3 daemon, the daemon will also check if the sender has appropriate permissions to invoke or launch the server. Unless other users are explicitly allowed to invoke on the server, only the user under which the daemon runs, will be allowed. As Orbix 6 clients do not send any principal information, the request will be rejected by the daemon.
Resolution	Run the following commands chmodit l all <registered_server_name> chmodit i all <registered_server_name> in order to grant access to the Orbix 3 server to everyone. The Orbix 6 client will then be able to invoke on and launch the Orbix 3 server. The settings can be verified by running catit <registered_server_name> If this does not help to resolve the OBJECT_NOT_EXIST exception in the Orbix 6 client, then also check solution P149338: "Trying to invoke on Orbix 3 server from Orbix 6 client raises OBJECT_NOT_EXIST error in client"
Workaround
Notes
Attachment