[
https://issues.jboss.org/browse/JBTM-1156?page=com.atlassian.jira.plugin....
]
Michael Musgrove commented on JBTM-1156:
----------------------------------------
The unit tests all pass.
The QA test suite makes it as far as the JDBC tests which fail because there is only one
db which listens on IPv6 (I could disable the other db tests).
The WSTX11 INTEROP and local junit tests (XTS/localjunit/pom.xml) are failing.
The XTS CRASH RECOVERY TESTS are failing
The TXBRIDGE TESTS pass.
The latest in a long line of errors is when the XTS arquillian tests try to connect to
127.0.0.1 which obviously fails on a pure IPv6 node:
"Could not deploy to container: JBAS012144: Could not connect to
remote://127.0.0.1:9999. The connection timed out" I am still trying to figure out
which bit of code is configuring 127.0.0.1
Configure some CI jobs to run on ipv6 only nodes
------------------------------------------------
Key: JBTM-1156
URL:
https://issues.jboss.org/browse/JBTM-1156
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 4.16.4, 5.0.0.M1
Reporter: Paul Robinson
Assignee: Michael Musgrove
Fix For: 4.16.5, 5.0.0.M2
Bugs that only appear on an IPV6 node will currently slip through our pre-release QA as
we don't have a node in Hudson that is configured to only have an IPV6 interface. One
example of this is:
https://issues.jboss.org/browse/JBPAPP-8906
Need clones of:
http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-branch416-java6/co...
http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-branch416-java7/co...
http://172.17.131.2/view/Narayana+BlackTie/job/narayana-java6/configure
http://172.17.131.2/view/Narayana+BlackTie/job/narayana-java7/configure
--
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