[omniORB] omniINSpoa and published endpoint

[Stephen Hansen]

Hi all. I'm using omniORB 4.1 and omniORBpy 3.

I have a servant that uses omniINSpoa on a specified port, with the ORB
configured via:

    args = ['-ORBendPoint', 'giop:tcp::41242']
    orb = CORBA.ORB_init(args, CORBA.ORB_ID)

There's a firewall between the server and the client, and 41242 is the only
port that's open. If I do a catior of the servant, I get:

    omniORB: Version: 4.1.1
    omniORB: Distribution date: Sun Oct  7 16:41:47 BST 2007 dgrisby
    omniORB: Information: the omniDynamic library is not linked.
    Type ID: "IDL:falcon.advpubtech.com/falcon/tunnel/TunnelServer:1.0"
    Profiles:
    1. IIOP 1.2 10.10.1.15 4265 "..u.H........."
                TAG_ORB_TYPE omniORB
                TAG_CODE_SETS char native code set: ISO-8859-1
                              char conversion code set: UTF-8
                              wchar native code set: UTF-16
                              wchar conversion code set: UTF-16

                TAG_ALTERNATE_IIOP_ADDRESS 10.10.1.15 41242

My problem is when I turn omniORB's tracelevel up high, I can see that time
is continually wasted in attempting to connect to 4265 first-- and then it
falls back on using 41242. Is there any way to specify that I *only* want a
specific endpoint published in the object reference?

Thanks in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20081016/11030c75/attachment.htm