Read only archive ; use https://github.com/JacORB/JacORB/issues for new issues

Bug 1030

Summary:	Two IP-address, one internal and one external registers internal IP to naming service, making the service inaccessible from out side
Product:	JacORB	Reporter:	alka singh <alka.singh>
Component:	Naming Service	Assignee:	Mailinglist to track bugs <jacorb-bugs>
Status:	RESOLVED FIXED
Severity:	critical	CC:	jacorb
Priority:	P5
Version:	3.6
Hardware:	Sun
OS:	Solaris

Description alka singh 2016-04-25 07:42:39 UTC

I have system with two ip-ddresses one for external interface and another for internal interface. While binding to naming service it is some how using internal IP to bind. 

The same code base was working with, java6 and jacorb 3.5, it was binding to external IP. after upgrading to java8 and jacorb 3.6 code is using internal ip to bind. Is there any known bug related to this?

Comment 1 Nick Cross 2016-04-25 09:34:44 UTC

There has been modifications to the ordering of network interfaces returned in the codebase. Would it be possible to test with the latest GIT codebase (https://github.com/JacORB/JacORB/) ?

Comment 2 alka singh 2016-04-29 06:39:55 UTC

I will try to test with GIT codebase. How would this help me though?
Is there any way i can change the order of network interfaces?

Comment 3 Nick Cross 2016-05-19 04:38:04 UTC

Discussed with Alka and problem has been solved in >= 3.7 codebase (i.e. current git head).