[jboss-jira] [JBoss JIRA] (WFLY-4786) Clustering integration tests fails once -Dnode0 and -Dnode1 are used

[Radoslav Husar (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-4786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096554#comment-13096554 ] 

Radoslav Husar commented on WFLY-4786:
--------------------------------------

Well, the bugzilla for EAP6 was related to the JDK8 handling, should not play any role now...

I have found the culprit [1] and working on a fix. For workaround, use the same address (i.e. -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_1) and different ports (default testsuite behavior).

[1] https://github.com/wildfly/wildfly/commit/46cdc917600156cbb6c7e628826b5e2fccbab4a0

> Clustering integration tests fails once -Dnode0 and -Dnode1 are used
> --------------------------------------------------------------------
>
>                 Key: WFLY-4786
>                 URL: https://issues.jboss.org/browse/WFLY-4786
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering, Test Suite
>    Affects Versions: 10.0.0.Alpha3
>            Reporter: Petr Kremensky
>            Assignee: Radoslav Husar
>         Attachments: results.zip
>
>
> Tests from wildfly-ts-integ-clustering module fails once we change default binding interfaces by -Dnode0 and -Dnode1 properties.
> See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-as-testsuite-clustering/
> * build 5 binds to localhost (no -Dnode*)
> * build 6 uses -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2
> Similar failures were addressed for EAP 6 by https://bugzilla.redhat.com/show_bug.cgi?id=1076015



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)