[omniORB] looks like the ORB is not listening on a given port

[Peter Klotz]

Hello Nicholas

A simple way to enforce an IPv4 listen is to just replace the hostname "WRON-VSAJN5" with its corresponding IPv4 address in your endpoint option.

Regards, Peter.
________________________________________
From: omniorb-list-bounces at omniorb-support.com [mailto:omniorb-list-bounces at omniorb-support.com] On Behalf Of Nicholas Rodomar
Sent: Tuesday, March 22, 2011 3:12 PM
To: Luke Deller; 'omniorb-list at omniorb-support.com'
Subject: RE: [omniORB] looks like the ORB is not listening on a given port

No, I don't think that's what we want. Good catch. Next question is why would that happen and how do I fix it (sorry, more programmer than network engineer)?

Thanks for your help.

Nicholas

From: Luke Deller [mailto:ldeller at iress.com.au] 
Sent: Monday, March 21, 2011 2:35 PM
To: Nicholas Rodomar; 'omniorb-list at omniorb-support.com'
Subject: Re: [omniORB] looks like the ORB is not listening on a given port

Hi Nicholas,

I see that your hostname WRON-VSAJN5 is resolving to an IPv6 address, so omniORB is listening on IPv6 rather than IPv4. Is that what you expect?

>From your log:
omniORB: Instantiate endpoint 'giop:tcp:WRON-VSAJN5:8101'
omniORB: Explicit bind to host WRON-VSAJN5.
omniORB: Bind to address fe80::9995:9a1d:5347:8584%11 port 8101.

Regards,
Luke

 
From: Nicholas Rodomar [mailto:nicholas.rodomar at ronin-capital.com] 
Sent: Tuesday, March 22, 2011 02:45 AM
To: omniorb-list at omniorb-support.com <omniorb-list at omniorb-support.com> 
Subject: [omniORB] looks like the ORB is not listening on a given port 
 
Hi all,

First time posting to this group so bear with me:

We are using the OMNI ORB to work with a CORBA implementation at the Chicago Board Options Exchange (CBOE). We have had our application running successfully on a number of machines but have encountered a problem with a recent install where messages sent from the CBOE in response to our calls seem to be making it to our client but they are not being read by our client ORB. 

The trace logs (attached) don't reveal anything unusual to my (untrained) eye.

Ordinarily, when the ORB is up and running with our client application one can telnet the client IP and port (in this case 8101) and establish a session but when we try on this client we can't telnet the machine and port so it seems to me that for some reason the ORB is not listening.

The system details are as follows:

. Operating system is Windows 7 64 bit
. omniORB version is 4.1.4-x86_win32-vs7
. the client sends to the CBOE over port 8102 and receives via port 8101

I have triple checked the settings (registry entry, ORB end point, host file entry etc.). There is no firewall enabled. We've tested this application on Windows 7 successfully before. 

If no-one has encountered this problem any suggestions on next steps for troubleshooting would be much appreciated. 

Thanks,

Nicholas
**********************************************************************************************
Important Note
This email (including any attachments) contains information which is confidential and may be subject to legal privilege.  If you are not the intended recipient you must not use, distribute or copy this email.  If you have received this email in error please notify the
sender immediately and delete this email. Any views expressed in this email are not necessarily the views of IRESS Market Technology Limited.

It is the duty of the recipient to virus scan and otherwise test the information provided before loading onto any computer system.
IRESS Market Technology Limited does not warrant that the information is free of a virus or any other defect or error.
**********************************************************************************************