]
James Perkins commented on WFCORE-1120:
---------------------------------------
Actually my patch won't catch that either. I'll have to think about the best
solution to catch those. I'd rather not look for every JVM argument. The system
property one was quite easy, but this would be more complicated.
One solution would be to use {{setJavaOptions()}} rather than {{addJavaOption()}}. In fact
looking at the wildfly-arquillian code I'd say we should likely use the setter
instead. That would be the same behavior as [previous
Launcher sets "-Djava.net.preferIPv4Stack=true" also with
IPv6 profile
----------------------------------------------------------------------
Key: WFCORE-1120
URL:
https://issues.jboss.org/browse/WFCORE-1120
Project: WildFly Core
Issue Type: Bug
Components: Test Suite
Affects Versions: 2.0.1.Final
Reporter: Marek Kopecký
Assignee: James Perkins
*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/jav...
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:*
{noformat}
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
...
{noformat}
*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-T...