Bug 900361 (JBPAPP6-955)

Madhumita, I don't think this is related to IBM JDK. See AS7-4540. Can you try the workaround? The diagnostics addr can be some default value, it doesn't have to be unique across hudson jobs, you can use $MCAST_ADDR for the other multicast address for the testsuite run on hudson

Rajesh,

       Yes I am aware of AS7-4540 and I am already using workaround $MCAST_ADDR to run this job on IBM JDK.Infact with this workaround the tests do pass on SUN JDK.Probably the IBM JDK behaves differently while setting these values ...hence i have kept this assigned to myself to investigate further.

http://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-AS-Testsuite/job/eap-60-as-testsuite-RHEL6-zipbuiltonoracleJDK6_testrunIBMJDK16/configure

Assuming that the IBM JDK was behaving differently and not picking up the proper jgroups and mcast which has been currently handled in testsuite pom(workaround suggested in AS7-4540),I tried to set then from commandline:

mvn -fae -B -s settings.xml install -Pnormal -DallTests -Dmaven.test.failure.ignore=true -Dmaven.repo.local=local-repo -Djboss.dist=${WORKSPACE}/jboss-eap-6.0 -Dsurefire.forked.process.timeout=3800 -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2 -Dmcast=$MCAST_ADDR -Dmcast.jgroupsDiag=224.0.75.75 -Dmcast.modcluster=224.0.1.105 

However this did not help and I still see the same error diagnostics_addr / diagnostics_port and mcast_addr / mcast_port have to be different.

It is surprising why this problem occurs only on IBM JDK as workaround suggested in AS7-4540 does not seem to work for IBM JDK

http://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-AS-Testsuite/job/eap-60-as-testsuite-RHEL6-buildIBMJDK6_testrunIBMJDK16/62/testReport/org.jboss.as.test.clustering.cluster.ejb3/StatefulTimeoutTestCase%28UDP%29/testStatefulTimeout/

Ondra, do you have an explanation for these failures and do you think fix for JBPAPP-8400 will fix this?

Attachment: Added: standalone_IBM.xml
Attachment: Added: standalone_SUN.xml

Ondra,

        As discussed I have attached the standalone.xml files taken from testsuite/integration/clust/target... 
I have also generated a diff which shows as follows:

269c269
<             <wsdl-host>${jboss.bind.address:10.16.95.134}</wsdl-host>
---
>             <wsdl-host>${jboss.bind.address:10.16.94.118}</wsdl-host>

281c281
<             <inet-address value="10.16.95.134"/>
---
>             <inet-address value="10.16.94.118"/>

284c284
<             <inet-address value="${jboss.bind.address:10.16.95.134}"/>
---
>             <inet-address value="${jboss.bind.address:10.16.94.118}"/>

292c292
<             <inet-address value="${jboss.bind.address.unsecure:10.16.95.134}"/>
---
>             <inet-address value="${jboss.bind.address.unsecure:10.16.94.118}"/>

307c307
<             <remote-destination host="10.16.95.134" port="25"/>
---
>             <remote-destination host="10.16.94.118" port="25"/>

Command on sunJDK:

mvn -B -X -s settings.xml clean install -Pnormal -Ppublic-repositories -Ppublic-plugin-repositories -Dmaven.test.failure.ignore=true -Dsurefire.test.failure.ignore=true -Dmaven.repo.local=local-repo -Djboss.dist=/mnt/hudson_workspace/workspace/eap-60-as-testsuite-RHEL6-oracleJDK6_smoke_with_distproperty-with-gitrepo-IPV4/jboss-eap-6.0 -Dskip-download-sources -fae -DallTests -Dnode0=10.16.95.134 -Dnode1=10.16.95.135 -Dmcast=227.43.88.174 -Dsurefire.forked.process.timeout=1800

Command on IBM JDK:

+ mvn -fae -B -s settings.xml install -Pnormal -DallTests -Dmaven.test.failure.ignore=true -Dmaven.repo.local=local-repo -Djboss.dist=/mnt/hudson_workspace/workspace/eap-60-as-testsuite-RHEL6-buildIBMJDK6_testrunIBMJDK16/jboss-eap-6.0 -Dsurefire.forked.process.timeout=3800 -Dnode0=10.16.94.118 -Dnode1=10.16.94.119 -Dmcast=227.43.88.216 -Dmcast.jgroupsDiag=224.0.75.75 -Dmcast.modcluster=224.0.1.105

Those IPs are just different QA lab IPs.
Which shows that the harness works fine; seems like JGroups, or rather clustering module, has an IBM-JDK-specific bug in property processing.

Bela Ban is on wacation.
Assigned to Matej Briskar. (He doesn't have JBPAPP privileges yet.)
He will try to find where the value get's lost.

Richard, would you be able to help debug this issue with IBM JDK?

Link: Added: This issue is a dependency of JBPAPP-9188

OK, i'll look at it.

These tests seem to pass in CR1(Not sure if its because there was some fix after Beta2 or it worked because I increased timeout substantially.
I set -Dsurefire.forked.process.timeout=3800)


http://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-AS-Testsuite/job/eap-60-as-testsuite-RHEL6-buildIBMJDK6_testrunIBMJDK16/70/testReport/

No clustering tests seem to fail in EAP 6.0.1.ER2 due to above issue:

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-AS-Testsuite/job/eap-60-as-testsuite-RHEL6-buildIBMJDK6_testrunIBMJDK16/lastCompletedBuild/testReport/

Docs QE Status: Removed: NEW