[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz edited comment on AS7-3819 at 2/20/12 11:18 AM:
--------------------------------------------------------------------
Problems:
(i) there is no profile named ipv6
(ii) the values ip.client.stack and ip.server.stack are used to pass JMV stack parameters
to both test clients and test servers respectively and these are fixed to start IPv4
stacks (java.net.preferIPv4Stack=true) So when you try and start a server using an IPv6
address on an IPv4 stack, the protocol is not recognized and the server will not complete
startup successfully.
(iii) there are settings for ip.client.stack and ip.server.stack scattered through various
poms. You might want to centralize their definition in the top-level pom (unless you need
to customize within modules).
Suggestion:
either by defining a profile or some other means, override the definitions of
ip.client.stack and ip.server.stack globally with two variations:
run the testsuite against IPv4:
ip.client.stack: sets -Djava.net.preferIPv4Stack=true
ip.server.stack: sets -Djava.net.preferIPv4Stack=true
run the testsuite against IPv6:
ip.client.stack: sets -Djava.net.preferIPv4Stack=false
-Djava.net.preferIPv6Addresses=true
ip.server.stack: sets -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addrsses=true
Once that is tested, and all tests pass, there are various interoperability combinations
to test (i.e. IPv4 clients with IPv6 servers, and vice versa)
was (Author: rachmato):
Problems:
(i) there is no profile named ipv6
(ii) the values ip.client.stack and ip.server.stack are used to pass JMV stack parameters
to both test clients and test servers respectively and these are fixed to start IPv4
stacks (java.net.preferIPv4Stack=true) So when you try and start a server using an IPv6
address on an IPv4 stack, the protocol is not recognized.
(iii) there are settings for ip.client.stack and ip.server.stack scattered through various
poms. You might want to centralize their definition in the top-level pom (unless you need
to customize within modules).
Suggestion:
either by defining a profile or some other means, override the definitions of
ip.client.stack and ip.server.stack globally with two variations:
run the testsuite against IPv4:
ip.client.stack: sets -Djava.net.preferIPv4Stack=true
ip.server.stack: sets -Djava.net.preferIPv4Stack=true
run the testsuite against IPv6:
ip.client.stack: sets -Djava.net.preferIPv4Stack=false
-Djava.net.preferIPv6Addresses=true
ip.server.stack: sets -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addrsses=true
Once that is tested, and all tests pass, there are various interoperability combinations
to test (i.e. IPv4 clients with IPv6 servers, and vice versa)
AS hangs in the testsuite when set to IPv6
------------------------------------------
Key: AS7-3819
URL:
https://issues.jboss.org/browse/AS7-3819
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.0.Final
Environment: Linux 32 bit
Reporter: Ondrej Zizka
STR:
1) Check out the latest
https://github.com/OndraZizka/jboss-as/TS-refactor
2) Rebuild
3) Run the testsuite with
{code}
./integration-tests.sh clean install -Dipv6 -Dnode0=[::1] -Ddebug
{code}
4) Attach a debugger to 8787
You might want to use -DtestLogToFile=false to see the output in terminal/IDE.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira