[omniORB] Multiple end point and Omni 2.8 client

[Wernke zur Borg]

Hi,
 
the easiest way to achieve this would be to specify:
 
-ORBendPoint giop:tcp::
-ORBendPointPublishAllIFs 1
 
This would cause all non-loopback interfaces to be published in IORs.
Alternatively you can list all interfaces with separate -ORBendPoint
options.
 
For omniORB 4.0 this is described in chapter 8.6.1 of the manual.
 
Regards, Wernke
 



________________________________

	From: Olivier Thiboutot [mailto:Olivier.Thiboutot at voxco.com] 
	Sent: 23 October 2006 16:26
	To: Wernke zur Borg; omniorb-list  Subject: RE: [omniORB]
Multiple end point and Omni 2.8 client
	
	

	Hi,

	 

	Thanks for that answer...

	 

	It doesn't exist into OmniOrb 2.8... I only found that into
OmniOrb 4.0.7

	 

	Is it possible for you to specify a brief way or a web page for
more information on how to use it...?

	 

	Best regards, Olivier

	
________________________________


	From: Wernke zur Borg [mailto:wernke.zur.borg at vega.de] 
	Sent: 23 octobre 2006 04:56
	To: Olivier Thiboutot
	Cc: OmniOrb
	Subject: RE: [omniORB] Multiple end point and Omni 2.8 client

	 

	 

		Hi,

		 

		We use a server that publish more than one profile like

		 

		Profile

		1. IIOP 1.0 Public_IP 3661

		2. IIOP 1.0 Local_IP 3661

		 

		When we are behind the firewall with NAT, no problem but
when we are local and not using the NAT to get back on the network, it
fails. If I reverse the profiles, the opposite problem rises... I
conclude that OmniOrb 2.8 client are not trying all endpoint for
establishing a connection. Is there a way to handle that?

		 

		Thanks in advance...

		 

		Olivier Thiboutot

		Voxco Canada

		 

	 

	OmniORB indeed only uses the first IIOP profile and ignores the
second one.

	 

	In a recent mail with subject "Problem connecting naming
service" (09 Oct) Duncan justified this behaviour and explained that
rather than using multiple profiles for the same protocol you should use
only one profile for IIOP with multiple alternate address tags
(TAG_ALTERNATE_IIOP_ADDRESS), which omniORB clients should respect.

	 

	I have not tried it with an omniORB client but from own
experience I can only warn you that other clients (example: Sun Java)
may not respect the alternate tags.

	 

	Regards, Wernke

	 

	 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20061023/c5442626/attachment-0001.htm