[omniORB] No connection to Naming Service from omniORB client

[Lai, Patrick]

I've seen such "connection to giop:tcp:255.255.255.255:65535" message.
There was a bug in tcpAddress::connect() that could cause such behavior if
clientCallTimeOutPeriod was non-zero.  See
http://www.omniorb-support.com/pipermail/omniorb-list/2002-December/022642.h
tml.  I think the current code in CVS has this fixed.

-- Patrick

> -----Original Message-----
> From: Christoph Thomalla [mailto:tho@iitb.fhg.de]
> Sent: Friday, March 07, 2003 7:20 AM
> To: omniorb-list@omniorb-support.com
> Subject: [omniORB] No connection to Naming Service from omniORB client
> 
> 
> Hi,
> 
> it seems to me I encountered quite the same problem as Ron 
> (Win2K, VC++6.0).
> I tried tnameserv.exe (JDK 1.3) and omniORB name service at different 
> ports with the same result.
> I am doing things like:
> ...
> omniORB: Client opened connection to giop:tcp:255.255.255.255:65535
> omniORB: sendChunk: to giop:tcp:255.255.255.255:65535 100 bytes
> ...