[Ace-users] [tao-bugs] : Problem using multiple endpoints

[Milan Cvetkovic]

Steve,

How are you transferring IOR to clients? Are you using corbaloc?

I had similar problem when I wanted to use 127.0.0.1 for clients on the
same machine, and network interface catrd address for clients on
remaining machines. I believe corbaloc is implemented as forwarding, and
in these cases it always forwards to the first endpoint.

As a workaround, I had the ORB listen on network interface card and us
UIOP endpoints for same machine clients. This seemed to work properly.

Milan.

Steve Carlucci wrote:
> I upgraded our application to use the latest beta kit, and I am still
> seeing the same behavior regarding multiple endpoints. Any ideas on the
> problem that I described in my original e-mail? Thanks in advance for
> any help.
> 
> Steve
> 
> 
> -----Original Message-----
> From: schmidt at dre.vanderbilt.edu [mailto:schmidt at dre.vanderbilt.edu] 
> Sent: Wednesday, October 10, 2007 11:57 AM
> To: Steve Carlucci
> Cc: tao-bugs at cs.wustl.edu
> Subject: Re: [tao-bugs] : Problem using multiple endpoints 
> 
> 
> Hi Steve,
> 
>    Thanks for using the PRF.
> 
> 
>>    TAO VERSION: 1.4.7
>>
>>    ACE VERSION: 5.4.7
> 
> 
> You are using a very old version of TAO.  Please upgrade to ACE+TAO+CIAO
> x.6.1 (i.e., ACE 5.6.1, TAO 1.6.1, and CIAO 0.6.1), which you can
> download from
> 
> http://download.dre.vanderbilt.edu
> 
> under the heading: "Latest Beta Kit."
> 
> The DOC groups at Washington University, UC Irvine, and Vanderbilt
> University only provide "best effort" support for non-sponsors for the
> latest release, as described in
> 
> http://www.dre.vanderbilt.edu/~schmidt/DOC_ROOT/ACE/docs/ACE-bug-process
> .html
> 
> Thus, if you need more "predictable" help for earlier versions of
> ACE+TAO, I recommend that you check out
> 
> http://www.dre.vanderbilt.edu/support.html
> 
> for a list of companies that will provide you with ACE+TAO commercial
> support.
> 
> Thanks,
> 
>         Doug
> 
> 
> 
>>    HOST MACHINE and OPERATING SYSTEM:
>>
>>            Windows XP Professional (using Winsock2)
>>
>>            RedHat Enterprise Linux 3.0, 4.0
>>
>>    COMPILER NAME AND VERSION (AND PATCHLEVEL):
>>
>>            On Windows:
>>
>>            Microsoft Visual Studio .NET 2003
>>
>>            On Linux:
>>
>>            gcc 4.0.2
>>
>>    THE $ACE_ROOT/ace/config.h FILE [if you use a link to a platform-
>>
>>    specific file, simply state which one]:
>>
>>            On Windows:
>>
>>            config-win32.h
>>
>>            On Linux:
>>
>>            config-linux.h
>>
>>    THE $ACE_ROOT/include/makeinclude/platform_macros.GNU FILE [if you
>>
>>    use a link to a platform-specific file, simply state which one
>>
>>    (unless this isn't used in this case, e.g., with Microsoft Visual
>>
>>    C++)]:
>>
>>    DOES THE PROBLEM AFFECT:
>>
>>        EXECUTION
>>
>>[Please indicate whether ACE/TAO, your application, or both are
> 
> affected.]
> 
>>Both
>>
>>    SYNOPSIS:
>>
>>I am seeing unexpected behavior when configuring my ORB to bind to
> 
> multiple endpoints. It appears that information about
> 
>>the first endpoint is always sent to clients, even if the client
> 
> attempted to connect to the ORB on a different endpoint.
> 
>>    DESCRIPTION:
>>
>>We are having a problem with the server component of our application
> 
> when we configure the ORB with multiple endpoints. We
> 
>>discovered this problem when one of our customers was attempting to
> 
> connect to our application's server through a proxy. In
> 
>>order to get this to work, we needed to add an additional endpoint and
> 
> use the hostname_in_ior option to specify the
> 
>>external IP address of the proxy. . This allowed the customer to
> 
> successfully connect through the proxy, but then was
> 
>>unable to connect from within the network because the ORB was
> 
> returning information that was specified in the first
> 
>>endpoint, namely the external IP address of the proxy that was
> 
> specified in the hostname_in_ior option. Here are the
> 
>>command line arguments that we were initializing the ORB with:
>>
>>"-ORBEndpoint iiop://192.168.1.100:13100/hostname_in_ior=10.10.1.1
> 
> -ORBEndpoint iiop://192.168.1.100:13200
> 
>>-ORBDottedDecimalAddresses 1"
>>
>>The first endpoint was intended to allow clients to connect to the ORB
> 
> through the proxy, the second endpoint was intended
> 
>>to allow clients to connect to the ORB from within the same network.
> 
> However, when a client attempts to connect to the ORB
> 
>>on port 13200 (the second endpoint) from within the same network, the
> 
> ORB returns information to the client indicating that
> 
>>it should be talking to 10.10.1.1, which obviously fails since the
> 
> client cannot see the external IP address of the proxy.
> 
>>By switching the order of the endpoints on the command line, we can
> 
> get it to work one way or the other, but not both. I
> 
>>understand that we are using an old version, and we are looking at
> 
> upgrading in our next release, but is this a
> 
>>configuration problem, or a known bug/limitation? If this is a known
> 
> bug/limitation, has it been fixed in a later release?
> 
>>It is very possible that I don't have a full understanding of what is
> 
> going on here and that I am missing something simple,
> 
>>so I apologize in advance if that is the case. Any help is
> 
> appreciated.
> 
>>_______________________________________________
>>tao-bugs mailing list
>>tao-bugs at mail.cse.wustl.edu
>>http://mail.cse.wustl.edu/mailman/listinfo/tao-bugs
> 
> 
> _______________________________________________
> tao-bugs mailing list
> tao-bugs at mail.cse.wustl.edu
> http://mail.cse.wustl.edu/mailman/listinfo/tao-bugs
> 
>