[omniORB] Differences with omniINSPOA

[Kevin Wooten]

I found the problem, I was using a this for the endpoint in the server "giop:tcp:localhost:1001". I was connecting from a process on the local machine as "corbaloc::machine:1001/loginObject". When I switched to using this corbaloc, "corbaloc::localhost:1001/loginObject", (also using localhost instead of machine name), it started to work!

Why would this make a difference, it used to work and now it doesn't??

By the way, I only have one network card, if that makes a difference.

>> -----Original Message-----
>> From: Kevin Wooten 
>> Sent: Monday, July 29, 2002 3:29 PM
>> To: omniorb-list@realvnc.com
>> Subject: [omniORB] Differences with omniINSPOA
>> 
>> 
>> I am using omniINSPOA to get an object reference from a 
>> corbaloc IOR. When I was using the developer preview that 
>> Duncan created, some time ago, I had everything working 
>> fine. I have upgraded to the latest snapshot, and now I 
>> cannot connect to my object. It appears as if the omniINSPOA 
>> is listening on the port I gave it using the orb's endpoint 
>> option, port 1001.
>> 
>> Kevin Wooten
>> iTRACS Corporation
>> email: kwooten@itracs.com
>> phone: 480-557-8000 ext. 132
>>  
>> 
>> 
>> _______________________________________________
>> omniORB-list mailing list
>> omniORB-list@realvnc.com
>> http://www.realvnc.com/mailman/listinfo/omniorb-list
>>