-
Bug
-
Resolution: Done
-
Major
-
2.0.1.Final
-
None
Description of problem:
Domain tests "-Djava.net.preferIPv4Stack=true" also with IPv6 profile. This property is set in AbstractCommandBuilder of WildFly-Core:
https://github.com/wildfly/wildfly-core/blob/master/launcher/src/main/java/org/wildfly/core/launcher/AbstractCommandBuilder.java#L50
There should be option for disable of this option in arquillian.xml file. And testsuite should use this option with IPv6 profile.
How reproducible:
Always
Steps to Reproduce:
- ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIPV6_1 -Dnode1=$MYTESTIPV6_2 -Dipv6 -Dts.manualmode -Dtest=OutboundLdapConnectionTestCase -DtestLogToFile=false -Djboss.dist=$JBOSS_DIST -Dts.noSmoke
Actual results:
07:04:26,054 INFO [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Starting container with: [/qa/tools/opt/jdk1.8.0_last/bin/java, ... -Djava.net.preferIPv4Stack=true, -Djava.net.preferIPv4Stack=false ...
Expected results:
EAP is not started with "-Djava.net.preferIPv4Stack=true" property with IPv6 profile
Additional info:
Jenkins reproducer job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP7/view/EAP7-AS-Testsuite/view/EAP7-AS-Testsuite-Reproducers/job/eap-7x-as-ts-ipv6-arqillian/jdk=java18_default,label_exp=eap-sustaining&&RHEL6&&x86_64&&ipv6/2/console
- clones
-
JBEAP-1861 Arquillian use "-Djava.net.preferIPv4Stack=true" also with IPv6 profile
- Closed
- is cloned by
-
ARQ-1997 Arquillian use "-Djava.net.preferIPv4Stack=true" also with IPv6
- Resolved
- is related to
-
WFLY-5675 Upgrade wildfly-arquillian from 1.0.1.Final to 1.0.2.Final
- Closed