Re: COMM_FAILURE

[Katherine Goude <katherine goude baesystems com>]

Dan Kegel wrote:

>  Katherine Goude wrote:
> >
> > I'm trying to run a test client and server over a network between two
> > machines. If I run the server on one machine and the client on the
> > other, everything works fine. However if I swap these over and run the
> > server on the second machine, when I start the client on the first
> > machine I get the exception: "IDL:CORBA/COMM_FAILURE:1.0".
> >
> > Anyone know what might be causing this? Both machines contain a
> > ~/.orbitrc file containing the line ORBIIOPIPv4=1. And it shouldn't be a
> > problem with the IOR passing between server and client because I'm still
> > using the highly technical method of cut and paste at the moment. The
> > lack of online help for ORBit has left me a bit stuck. Any ideas?
>
> I've seen funny problems if you try to run corba servers on machines
> where /bin/hostname produced a hostname that was not well known
> to the world... make sure both machines can ping the server at the
> address returned by /bin/hostname on the server.
> - Dan

>From the machine A client I _can_ ping the machine B server using the result
of /bin/hostname on machine B (and vice versa) so it doesn't look like this is
the problem.

I tried running ior-decode-2 on the IORs produced by the server on each
machine. With the IOR produced by the server on machine B, ior-decode-2 does
not output the section IOP_TAG_INTERNET_IOP wheras with the IOR produced by
machine A it does.
I have no idea what this means - could this be the cause of the comm failure?
And if so how do I fix it?

    Machine A                                            Machine B
        server    <--------------------------    client            works!
        client     --------------------------->   server           fails!

regards,
Katherine