10:28 p.m.
Ondrej Zizka created AS7-3819:
---------------------------------
Summary: 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
10:51 p.m.
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka commented on AS7-3819:
-----------------------------------
Should be -Dnode0=::1 . But the behavior is the same.
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
10:53 p.m.
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka commented on AS7-3819:
-----------------------------------
Also note that I haven't spent much on this so it might be anything from Arquillian
unable to deploy to HornetQ which has a zombie thread -
HornetQ-remoting-threads-HornetQServerImpl::serverUUID-...
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
9:37 a.m.
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz commented on AS7-3819:
------------------------------------------
By the way, [::1] is not an IP address. You should not be enclosing IP addresses in square
brackets to get around deficiencies in parsing of URLs (or anthing else) in the AS or the
testsuite framework.
.
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
9:37 a.m.
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz edited comment on AS7-3819 at 2/20/12 10:37 AM:
--------------------------------------------------------------------
By the way, [::1] is not an IP address. You should not be enclosing IP addresses in square
brackets to get around deficiencies in parsing of URLs (or anything else) in the AS or the
testsuite framework. If you have to, that's a bug.
.
was (Author: rachmato):
By the way, [::1] is not an IP address. You should not be enclosing IP addresses in
square brackets to get around deficiencies in parsing of URLs (or anthing else) in the AS
or the testsuite framework.
.
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
10:17 a.m.
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz commented on AS7-3819:
------------------------------------------
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)
ip.server.stack: sets -Djava.net.preferIPv4Stack=false
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
10:17 a.m.
[
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:17 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.
(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)
ip.server.stack: sets -Djava.net.preferIPv4Stack=false
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
10:19 a.m.
[
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
10:19 a.m.
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz commented on AS7-3819:
------------------------------------------
Once I changed the stack preferences, the tests passed.
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
12:16 a.m.
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka commented on AS7-3819:
-----------------------------------
Hi Richard,
1) There is a profile ts.ipv6 activated by -Dipv6.
2) ip.client.stack and ip.server.stack are not fixed. They are changed by the profile
mentioned above.
You can verify that it works in the respective boot.log.
This is excerpt from
{{testsuite/integration/clust/target/jbossas-clustering-udp-0/standalone/log/boot.log}}
after running {{./integration-tests.sh clean install -Dts.clust -Dts.noSmoke -Dipv6
-Dnode0=::1}} :
{code}
06:52:07,230 DEBUG [org.jboss.as.config] Configured system properties:
java.net.preferIPv4Stack = false
java.net.preferIPv6Addresses = true
...
06:52:07,447 DEBUG [org.jboss.as.config] VM Arguments: -Xmx512m -XX:MaxPermSize=256m
-Djboss.dist=/home/ondra/work/AS7/ozizka-git/testsuite/integration/clust/../../../build/target/jboss-as-7.1.1.Final-SNAPSHOT
-Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true -Dts.tr.fsio=100
-Dts.tr.netio=100 -Dts.tr.memio=100 -Dts.tr.db=100 -Dnode0=::1 -Dnode1=127.0.0.1
-DudpGroup=230.0.0.4 [...] -Djboss.node.name=node-udp-0 -ea
{code}
3) What do you mean by "they are scattered"? It basically works the way you are
suggesting.
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
12:18 a.m.
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka commented on AS7-3819:
-----------------------------------
By the way - {code:xml}<wsdl-host>${jboss.bind.address:::1}</wsdl-host>{code}
is okay?
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
12:18 a.m.
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka commented on AS7-3819:
-----------------------------------
Anyway, I found the reason for the failure - the server instances don't copy from
where they should - target/jbossas . Searching for some remnant of the old way of
copying.
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
12:30 a.m.
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka edited comment on AS7-3819 at 2/21/12 1:30 AM:
------------------------------------------------------------
Anyway, I found the reason for the failure - the server instances have 127.0.0.1 in their
interfaces. Searching for the cause.
was (Author: ozizka):
Anyway, I found the reason for the failure - the server instances don't copy from
where they should - target/jbossas . Searching for some remnant of the old way of
copying.
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
12:30 a.m.
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka commented on AS7-3819:
-----------------------------------
These are 127.0.0.1 in {{common-targets.xml}}
{code:xml}
<macrodef name="ts.config-as.ip-with-multicast" ...>
<param name="managementIPAddress"
expression="@{node}"/>
<param name="publicIPAddress"
expression="@{node}"/>
{code}
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
12:37 a.m.
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka commented on AS7-3819:
-----------------------------------
The {{node0}} and {{node1}} are not propagated to {{clustering-build.xml}}.
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
12:44 a.m.
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka commented on AS7-3819:
-----------------------------------
I have no idea how to get the properties to Ant. Or how they should be referred.
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
12:44 a.m.
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka edited comment on AS7-3819 at 2/21/12 1:44 AM:
------------------------------------------------------------
The {{node0}} and {{node1}} are not propagated to {{clustering-build.xml}}.
{code}
main:
[echo] In Maven: node0: ::1
[echo] In Maven: node1: 127.0.0.1
build-clustering-udp:
[echo] Building config clustering-udp-0
[echo] A node0: 127.0.0.1
[echo] A node1: 127.0.0.1
{code}
was (Author: ozizka):
The {{node0}} and {{node1}} are not propagated to {{clustering-build.xml}}.
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
12:53 a.m.
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka commented on AS7-3819:
-----------------------------------
{{inheritAll="true"}} in
{code:xml}
<ant antfile="${basedir}/../src/test/scripts/clustering-build.xml"
inheritAll="true">
{code}
didn't work. The properties must be named specifically.
Fixed.
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
3:48 a.m.
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka commented on AS7-3819:
-----------------------------------
Richard, how exactly did you make the test pass?
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
9:56 a.m.
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz commented on AS7-3819:
------------------------------------------
I must have a different file:
{noformat}
[nrla@lenovo OndraZizka-jboss-as-813b298]$ grep -R ts.ipv6 *
[nrla@lenovo OndraZizka-jboss-as-813b298]$ grep -R
"scripts/clustering-build.xml" *
testsuite/integration/pom.xml: <ant
antfile="${basedir}/src/test/scripts/clustering-build.xml">
[nrla@lenovo OndraZizka-jboss-as-813b298]$
{noformat}
My archive does not have those profiles. I zipped up a branch called TS-refactor. Your
original link listed above gives me a 404.
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
10:34 a.m.
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz commented on AS7-3819:
------------------------------------------
I do have the wrong file. Can you point me to the correct updated version?
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
7:43 p.m.
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz commented on AS7-3819:
------------------------------------------
Aslak can probably sort this out fast.
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
7:43 p.m.
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz commented on AS7-3819:
------------------------------------------
I'm seeing this whenh I run the tests as above:
{noformat}
<testcase time="0"
classname="org.jboss.as.test.smoke.embedded.demos.client.messaging.MessagingClientTestCase"
name="org.jboss.as.test.smoke.embedded.demos.client.messaging.MessagingClientTestCase">
<error message="Operation failed with status WAITING"
type="java.lang.RuntimeException">java.lang.RuntimeException: Operation
failed with status WAITING
at org.jboss.remoting3.jmx.RemotingConnector.connect(RemotingConnector.java:155)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
at
org.jboss.as.arquillian.container.ManagementClient.getConnection(ManagementClient.java:325)
at
org.jboss.as.arquillian.container.ManagementClient.getDeploymentMetaData(ManagementClient.java:113)
at
org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:144)
at
org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:156)
at
org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:123)
at
org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:266)
at
org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:122)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at
org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at
org.jboss.arquillian.container.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at
org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createDeploymentContext(ContainerDeploymentContextHandler.java:78)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at
org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114)
at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
at
org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:90)
at
org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:79)
at
org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:258)
at
org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachManagedDeployment(ContainerDeployController.java:234)
at
org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deployManaged(ContainerDeployController.java:78)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at
org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114)
at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
at
org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:101)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at
org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at
org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at
org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114)
at
org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80)
at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182)
at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
at
org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
at
org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68)
</error>
<system-out>20:27:41,436 INFO
[org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Starting
container with: [/opt/jdk-1.6.0_26/bin/java, -Xmx512m, -XX:MaxPermSize=256m,
-Djboss.dist=/home/nrla/projects/ozizka-jboss-as/testsuite/integration/smoke/../../../build/target/jboss-as-7.1.1.Final-SNAPSHOT,
-Djava.net.preferIPv4Stack=false, -Djava.net.preferIPv6Addresses=true, -Dts.tr.fsio=100,
-Dts.tr.netio=100, -Dts.tr.memio=100, -Dts.tr.db=100, -Dnode0=::1, -Dnode1=::1,
-DudpGroup=ff0e::1,
-Djbossas.ts.submodule.dir=/home/nrla/projects/ozizka-jboss-as/testsuite/integration/smoke,
-Djbossas.ts.integ.dir=/home/nrla/projects/ozizka-jboss-as/testsuite/integration/smoke/..,
-Djbossas.ts.dir=/home/nrla/projects/ozizka-jboss-as/testsuite/integration/smoke/../..,
-Djbossas.project.dir=/home/nrla/projects/ozizka-jboss-as/testsuite/integration/smoke/../../..,
-Djboss.dist=/home/nrla/projects/ozizka-jboss-as/testsuite/integration/smoke/../../../build/target/jboss-as-7.1.1.Final-SNAPSHOT,
-Djboss.inst=/home/nrla/projects/ozizka-jboss-as/testsuite/integration/smoke/target/jbossas,
-ea,
-Djboss.home.dir=/home/nrla/projects/ozizka-jboss-as/testsuite/integration/smoke/target/jbossas,
-Dorg.jboss.boot.log.file=/home/nrla/projects/ozizka-jboss-as/testsuite/integration/smoke/target/jbossas/standalone/log/boot.log,
-Dlogging.configuration=file:/home/nrla/projects/ozizka-jboss-as/testsuite/integration/smoke/target/jbossas/standalone/configuration/logging.properties,
-Djboss.modules.dir=/home/nrla/projects/ozizka-jboss-as/build/target/jboss-as-7.1.1.Final-SNAPSHOT/modules,
-Djboss.bundles.dir=/home/nrla/projects/ozizka-jboss-as/build/target/jboss-as-7.1.1.Final-SNAPSHOT/bundles,
-jar,
/home/nrla/projects/ozizka-jboss-as/testsuite/integration/smoke/target/jbossas/jboss-modules.jar,
-mp,
/home/nrla/projects/ozizka-jboss-as/testsuite/integration/smoke/../../../build/target/jboss-as-7.1.1.Final-SNAPSHOT/modules,
-jaxpmodule, javax.xml.jaxp-provider, org.jboss.as.standalone, -server-config,
standalone-full.xml]
20:27:41,522 INFO [org.xnio] (main) XNIO Version 3.0.3.GA
20:27:41,561 INFO [org.xnio.nio] (main) XNIO NIO Implementation Version 3.0.3.GA
20:27:41,580 INFO [org.jboss.remoting] (main) JBoss Remoting version 3.2.2.GA
20:27:41,848 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
20:27:42,037 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
20:27:42,086 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final-SNAPSHOT
"Thunder" starting
20:27:43,216 INFO [org.xnio] XNIO Version 3.0.3.GA
...
{noformat}
Looking at the logs, the server starts fine, with the correct IPv6 stack and IP addresses
and I can even connect to it myself using a browser. It looks as though Arquillian cannot
connect to the server for some reason. I also see surefire setting a lot of system
property variables, but not all of these appear in the JUnit test system properties, which
is odd.
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
11:02 a.m.
New subject: [JBoss JIRA] (AS7-3819) AS testsuite hangs when set to IPv6
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka updated AS7-3819:
------------------------------
Summary: AS testsuite hangs when set to IPv6 (was: AS hangs in the testsuite when set
to IPv6)
AS testsuite hangs 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
11:45 a.m.
New subject: [JBoss JIRA] (AS7-3819) AS testsuite hangs when set to IPv6
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka updated AS7-3819:
------------------------------
Attachment: testLog.txt
The attachment shows that {{mvn clean install -rf testsuite/ -Dnode0=127.0.0.2
-DtestLogToFile=false}} runs the server, but that fails with:
{code}
StartException in service jboss.network.public: JBAS015810: failed to resolve interface
public
...
StartException in service jboss.network.management: JBAS015810: failed to resolve
interface management
...
StartException in service jboss.network.management: JBAS015810: failed to resolve
interface management
{code}
AS testsuite hangs 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
Attachments: testLog.txt
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
4:42 p.m.
New subject: [JBoss JIRA] (AS7-3819) AS testsuite hangs when set to IPv6
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz commented on AS7-3819:
------------------------------------------
This issue was causing the testsuite to hang: https://issues.jboss.org/browse/AS7-3894
With that fixed, other issues are turning up but they seem more manageable.
AS testsuite hangs 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
Attachments: testLog.txt
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
5:43 p.m.
New subject: [JBoss JIRA] (AS7-3819) AS testsuite hangs when set to IPv6
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz commented on AS7-3819:
------------------------------------------
Aside from a few test cases in which there are hard coded 127.0.0.1 IP address literals,
the smoke tests have only the following failures:
{noformat}
[nrla@lenovo jboss-as-git-repo]$ ./integration-tests.sh clean install -Dnode0=::1
-Dnode1=::1 -DudpGroup=ff0e::1 -Dipv6
/home/nrla/projects/jboss-as-git-repo/tools/maven/bin/mvn -s
../tools/maven/conf/settings.xml clean install -Dnode0=::1 -Dnode1=::1
-DudpGroup=ff0e::1 -Dipv6 -Dts.smoke
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] JBoss Application Server Test Suite: Aggregator
[INFO] JBoss Application Server Test Suite: Integration
[INFO] JBoss Application Server Test Suite: Integration - Smoke
...
Results :
Failed tests:
testDistributeWebApp(org.jboss.as.test.smoke.jsr88.EnterpriseDeploymentTestCase):
expected:<Completed> but was:<Failed>
testDistributeEjbApp(org.jboss.as.test.smoke.jsr88.EnterpriseDeploymentTestCase):
expected:<Completed> but was:<Failed>
testDistributeEARApp(org.jboss.as.test.smoke.jsr88.EnterpriseDeploymentTestCase):
expected:<Completed> but was:<Failed>
Tests in error:
testDeploymentStreamApi(org.jboss.as.test.smoke.surefire.servermodule.ServerInModuleDeploymentTestCase):
Operation failed with status WAITING
testDeploymentFileApi(org.jboss.as.test.smoke.surefire.servermodule.ServerInModuleDeploymentTestCase):
Operation failed with status WAITING
testFilesystemDeployment_Marker(org.jboss.as.test.smoke.surefire.servermodule.ServerInModuleDeploymentTestCase):
Operation failed with status WAITING
testFilesystemDeployment_Auto(org.jboss.as.test.smoke.surefire.servermodule.ServerInModuleDeploymentTestCase):
Operation failed with status WAITING
testExplodedFilesystemDeployment(org.jboss.as.test.smoke.surefire.servermodule.ServerInModuleDeploymentTestCase):
Operation failed with status WAITING
Tests run: 122, Failures: 3, Errors: 5, Skipped: 4
{noformat}
AS testsuite hangs 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
Attachments: testLog.txt
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
5:58 p.m.
New subject: [JBoss JIRA] (AS7-3819) AS testsuite hangs when set to IPv6
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz edited comment on AS7-3819 at 2/23/12 6:57 PM:
-------------------------------------------------------------------
Aside from a few test cases in which there are hard coded 127.0.0.1 IP address literals,
the smoke tests have only the following failures:
{noformat}
[nrla@lenovo jboss-as-git-repo]$ ./integration-tests.sh clean install -Dnode0=::1
-Dnode1=::1 -DudpGroup=ff0e::1 -Dipv6
/home/nrla/projects/jboss-as-git-repo/tools/maven/bin/mvn -s
../tools/maven/conf/settings.xml clean install -Dnode0=::1 -Dnode1=::1
-DudpGroup=ff0e::1 -Dipv6 -Dts.smoke
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] JBoss Application Server Test Suite: Aggregator
[INFO] JBoss Application Server Test Suite: Integration
[INFO] JBoss Application Server Test Suite: Integration - Smoke
...
Results :
Failed tests:
testDistributeWebApp(org.jboss.as.test.smoke.jsr88.EnterpriseDeploymentTestCase):
expected:<Completed> but was:<Failed>
testDistributeEjbApp(org.jboss.as.test.smoke.jsr88.EnterpriseDeploymentTestCase):
expected:<Completed> but was:<Failed>
testDistributeEARApp(org.jboss.as.test.smoke.jsr88.EnterpriseDeploymentTestCase):
expected:<Completed> but was:<Failed>
Tests run: 122, Failures: 3, Errors: 0, Skipped: 4
{noformat}
was (Author: rachmato):
Aside from a few test cases in which there are hard coded 127.0.0.1 IP address
literals, the smoke tests have only the following failures:
{noformat}
[nrla@lenovo jboss-as-git-repo]$ ./integration-tests.sh clean install -Dnode0=::1
-Dnode1=::1 -DudpGroup=ff0e::1 -Dipv6
/home/nrla/projects/jboss-as-git-repo/tools/maven/bin/mvn -s
../tools/maven/conf/settings.xml clean install -Dnode0=::1 -Dnode1=::1
-DudpGroup=ff0e::1 -Dipv6 -Dts.smoke
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] JBoss Application Server Test Suite: Aggregator
[INFO] JBoss Application Server Test Suite: Integration
[INFO] JBoss Application Server Test Suite: Integration - Smoke
...
Results :
Failed tests:
testDistributeWebApp(org.jboss.as.test.smoke.jsr88.EnterpriseDeploymentTestCase):
expected:<Completed> but was:<Failed>
testDistributeEjbApp(org.jboss.as.test.smoke.jsr88.EnterpriseDeploymentTestCase):
expected:<Completed> but was:<Failed>
testDistributeEARApp(org.jboss.as.test.smoke.jsr88.EnterpriseDeploymentTestCase):
expected:<Completed> but was:<Failed>
Tests in error:
testDeploymentStreamApi(org.jboss.as.test.smoke.surefire.servermodule.ServerInModuleDeploymentTestCase):
Operation failed with status WAITING
testDeploymentFileApi(org.jboss.as.test.smoke.surefire.servermodule.ServerInModuleDeploymentTestCase):
Operation failed with status WAITING
testFilesystemDeployment_Marker(org.jboss.as.test.smoke.surefire.servermodule.ServerInModuleDeploymentTestCase):
Operation failed with status WAITING
testFilesystemDeployment_Auto(org.jboss.as.test.smoke.surefire.servermodule.ServerInModuleDeploymentTestCase):
Operation failed with status WAITING
testExplodedFilesystemDeployment(org.jboss.as.test.smoke.surefire.servermodule.ServerInModuleDeploymentTestCase):
Operation failed with status WAITING
Tests run: 122, Failures: 3, Errors: 5, Skipped: 4
{noformat}
AS testsuite hangs 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
Attachments: testLog.txt
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
6:34 p.m.
New subject: [JBoss JIRA] (AS7-3819) AS testsuite hangs when set to IPv6
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz commented on AS7-3819:
------------------------------------------
This last probl;em may be a bug or it may be a configuration building issue:
{noformat}
19:04:25,464 INFO [org.jboss.as.ee.deployment.spi] (Thread-37) JBAS016100: Begin deploy:
[target=http://org.jboss.as.ee.deployment/jsr88?targetType=as7,parent=null,type=ejb,id=file:/tmp/deployment-ejb.jar]
19:04:25,469 INFO [org.jboss.remoting.endpoint] (Thread-37) Connecting to destination
address /127.0.0.1:9999
19:04:25,475 INFO [org.jboss.remoting.endpoint] (Thread-37) Connecting to destination
address /127.0.0.1:9999
19:04:30,480 ERROR [org.jboss.as.ee.deployment.spi] (Thread-37) JBAS016153: Operation
Distribute failed on target:
org.jboss.as.ee.deployment.spi.DeploymentManagerTarget@b0014f0:
java.lang.RuntimeException: java.net.ConnectException: JBAS012144: Could not connect to
remote://127.0.0.1:9999. The connection timed out
at
org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeAsync(AbstractModelControllerClient.java:113)
at
org.jboss.as.controller.client.helpers.standalone.impl.ModelControllerClientServerDeploymentManager.executeOperation(ModelControllerClientServerDeploymentManager.java:47)
at
org.jboss.as.controller.client.helpers.standalone.impl.AbstractServerDeploymentManager.execute(AbstractServerDeploymentManager.java:79)
at
org.jboss.as.ee.deployment.spi.DeploymentManagerTarget.executeDeploymentPlan(DeploymentManagerTarget.java:195)
at
org.jboss.as.ee.deployment.spi.DeploymentManagerTarget.deploy(DeploymentManagerTarget.java:118)
at org.jboss.as.ee.deployment.spi.DeploymentWorker.run(DeploymentWorker.java:64)
Caused by: java.net.ConnectException: JBAS012144: Could not connect to
remote://127.0.0.1:9999. The connection timed out
at
org.jboss.as.protocol.ProtocolChannelClient.connectSync(ProtocolChannelClient.java:166)
at
org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:166)
at
org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:138)
at
org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:62)
at
org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:106)
at
org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:89)
at
org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:252)
at
org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:151)
at
org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeAsync(AbstractModelControllerClient.java:111)
... 5 more
{noformat}
ProtocolChannelClient is definitely being passed the wrong URI of
remote://127.0.0.1:9999.
AS testsuite hangs 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
Attachments: testLog.txt
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
10:06 a.m.
New subject: [JBoss JIRA] (AS7-3819) AS testsuite hangs when set to IPv6
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz commented on AS7-3819:
------------------------------------------
The issue above with EnterpriseDeploymentTestCase:
https://issues.jboss.org/browse/AS7-3901
AS testsuite hangs 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
Attachments: testLog.txt
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
10:25 a.m.
New subject: [JBoss JIRA] (AS7-3819) AS testsuite hangs when set to IPv6
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz edited comment on AS7-3819 at 2/24/12 11:24 AM:
--------------------------------------------------------------------
The issue above with EnterpriseDeploymentTestCase:
https://issues.jboss.org/browse/AS7-3901
With a fix for this in place, and changing 127.0.0.1 to localhost in about 5 test cases,
all the smoke tests now pass with IPv6 started as described above.
was (Author: rachmato):
The issue above with EnterpriseDeploymentTestCase:
https://issues.jboss.org/browse/AS7-3901
AS testsuite hangs 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
Attachments: testLog.txt
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
9:07 a.m.
New subject: [JBoss JIRA] (AS7-3819) AS testsuite hangs when set to IPv6
[
https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka closed AS7-3819.
-----------------------------
Assignee: Ondrej Zizka
Fix Version/s: 7.1.1.Final
Resolution: Done
AS testsuite hangs 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
Assignee: Ondrej Zizka
Fix For: 7.1.1.Final
Attachments: testLog.txt
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
4694
days inactive
4708
days old
31 comments
2 participants
participants (2)
-
Ondrej Zizka (JIRA) -
Richard Achmatowicz (JIRA)