-
1. Re: JBAS-6390, JBNAME-25, IPv6 support
Dimitris Andreadis Jan 21, 2009 6:23 AM (in response to Scott Stark)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. -
2. Re: JBAS-6390, JBNAME-25, IPv6 support
Dimitris Andreadis Jan 21, 2009 8:13 AM (in response to Scott Stark)Well, the cutoff date for the next CP is ... today (Jan/21st).
-
3. Re: JBAS-6390, JBNAME-25, IPv6 support
Scott Stark Jan 21, 2009 1:55 PM (in response to Scott Stark)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.
-
4. Re: JBAS-6390, JBNAME-25, IPv6 support
Scott Stark Jan 21, 2009 8:39 PM (in response to Scott Stark)All the tests passed, so I committed the change to the Branch_4_2.
-
5. Re: JBAS-6390, JBNAME-25, IPv6 support
Dimitris Andreadis Jan 22, 2009 8:04 AM (in response to Scott Stark)Committed also to Branch_5_x, thanks!
-
6. Re: JBAS-6390, JBNAME-25, IPv6 support
Dominik Pospisil May 5, 2009 5:13 AM (in response to Scott Stark)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