JBAS-6390, JBNAME-25, IPv6 support

starksm64 Jan 21, 2009 1:32 AM

I have spent some time on the ipv6 address issue affecting the jndi implementation. A few changes are needed:

1. Change the Naming cache to use InetSocketAddress as the key rather than the host + ":" port string.
2. Add an alternate host + "@" port url syntax so that one can specify an ipv6 address and a port.
3. If there are multiple ':' in a provider url, we have to assume its an IPv6 address with no port. The only way a port can be specified with an IPv6 address is by using the '@' separator as in:
::ffff:127.0.0.1@1099

I have these changes in the naming project trunk with a simple IPv6UnitTest. What is the time frame this needs to be done for the 4.2.x branch?

1. Re: JBAS-6390, JBNAME-25, IPv6 support

dimitris Jan 21, 2009 6:23 AM (in response to starksm64)

We want to test this change in Branch_4_2, so we can backport it to the EAP branch. So the timeframe is really that of the next EAP CP release - I'll find out.

I think the emphasis here would be not to break what's working now.
Actions
2. Re: JBAS-6390, JBNAME-25, IPv6 support

dimitris Jan 21, 2009 8:13 AM (in response to starksm64)

Well, the cutoff date for the next CP is ... today (Jan/21st).
Actions
3. Re: JBAS-6390, JBNAME-25, IPv6 support

starksm64 Jan 21, 2009 1:55 PM (in response to starksm64)

I'm running the Branch_4_2 testsuite with the change. If it looks good I'll commit it, otherwise I'll hold it to the next release.
Actions
4. Re: JBAS-6390, JBNAME-25, IPv6 support

starksm64 Jan 21, 2009 8:39 PM (in response to starksm64)

All the tests passed, so I committed the change to the Branch_4_2.
Actions
5. Re: JBAS-6390, JBNAME-25, IPv6 support

dimitris Jan 22, 2009 8:04 AM (in response to starksm64)

Committed also to Branch_5_x, thanks!
Actions
6. Re: JBAS-6390, JBNAME-25, IPv6 support

dpospisil May 5, 2009 5:13 AM (in response to starksm64)

Still, it is not clear to me how to get the testsuite running with an IPV6 address. Even if I specify JNDI url using @ syntax (node0.jndi.url=jnp://::1@1099) lots of test cases are just ignoring this property and assuming jnp://$HOST:$PORT syntax. As far as I understand, it would be required to:

a) add support for standard IPV6 url in form: jnp://[$IPV6_ADDR]:$PORT
b) fix those test cases

Thanks,

Dominik
Actions

Go to original post