[omniORB] Problem with command line parameters from omniORB
403to407 - it works!
janssen.h at atlas.de
janssen.h at atlas.de
Wed Jan 18 14:30:30 GMT 2006
Thank you! Now it works :)
-----Original Message-----
From: Duncan Grisby [mailto:duncan at grisby.org]
Sent: Wednesday, January 18, 2006 2:17 PM
To: Janssen, Heiko
Cc: omniorb-list at omniorb-support.com
Subject: Re: [omniORB] Problem with command line parameters from omniORB
403to407
On Wednesday 18 January, janssen.h at atlas.de wrote:
> I have another question, which could help to solve the problem. I use
> the following command line parameters:
>
> Test.exe o -ORBInitRef
> NameService=corbaloc::192.168.0.42:10001/NameService -ORBendPoint
> giop:tcp:192.168.0.42:10001 -ORBgiopMaxMsgSize 50000000
>
> I'm not sure what the option -ORBendPoint giop:tcp:...:10001 does, I
> just take these parameters from the existent project.
You have told your Test.exe program that its naming service is at
address 192.168.0.42 port 10001. You have also told it that it should
listen on address 192.168.0.43 port 10001. In other words, you have told
it that its naming service is itself. It is not the naming service, so
trying to use it as the naming service fails.
Where is your naming service running? That is the address you need to
use in the corbaloc URI. It is most likely that you do not need to give
the -ORBendPoint argument at all.
Cheers,
Duncan.
--
-- Duncan Grisby --
-- duncan at grisby.org --
-- http://www.grisby.org --
More information about the omniORB-list
mailing list