Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WFLY-3246 Upgrade JGroups to 3.5.1.Final #6777

Closed
wants to merge 3 commits into from

Conversation

pferraro
Copy link
Contributor

@pferraro pferraro commented Oct 2, 2014

https://issues.jboss.org/browse/WFLY-3246
Includes protocol stack tweaks, most notably:

  • Uses new default transfer-queue bundler
  • Use MERGE3 for tcp-based stack
  • Disabling the infamous stdout messages from GMS.print_local_addr (WFLY-270)

Also, WFLY-3445 Allow custom protocol types in jgroups stack
https://issues.jboss.org/browse/WFLY-3445

@wildfly-ci
Copy link

Linux with security manager Build 154 is now running using a merge of 876fbbd

@wildfly-ci
Copy link

Linux Build 5119 is now running using a merge of 876fbbd

@wildfly-ci
Copy link

Windows Build 267 is now running using a merge of 876fbbd

@wildfly-ci
Copy link

Linux with security manager Build 154 outcome was SUCCESS using a merge of 876fbbd
Summary: Tests passed: 790, ignored: 242 Build time: 0:06:50

@wildfly-ci
Copy link

Windows Build 267 outcome was SUCCESS using a merge of 876fbbd
Summary: Tests passed: 3084, ignored: 260, muted: 1 Build time: 0:55:05

@wildfly-ci
Copy link

Linux Build 5119 outcome was FAILURE using a merge of 876fbbd
Summary: Tests failed: 2 (2 new), passed: 3083, ignored: 260 Build time: 0:56:35

Build problems:

Failed tests detected

Failed tests

org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutRelayedToBackups: java.lang.AssertionError: expected:<200> but was:<500>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

org.jboss.as.test.manualmode.ejb.client.cluster.EJBClientClusterConfigurationTestCase.testServerToServerClusterFormation: javax.ejb.EJBException: java.lang.IllegalStateException: EJBCLIENT000029: No cluster context available for cluster named ejb
    at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:191)
    at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:276)

@pferraro
Copy link
Contributor Author

pferraro commented Oct 3, 2014

There's seems to be a regression with some aspect of the UDP stack (it's what these 2 failing tests have in common) and ipv6 on Linux. Investigating...

@wildfly-ci
Copy link

Linux Build 5121 is now running using a merge of 876fbbd

@wildfly-ci
Copy link

Linux Build 5121 outcome was FAILURE using a merge of 876fbbd
Summary: Tests failed: 78 (76 new), passed: 3176, ignored: 273 Build time: 1:30:15

Build problems:

Failed tests detected

Failed tests

org.jboss.as.test.integration.deployment.structure.ear.EarJBossDeploymentStructureTestCase: org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: deployment-structure.ear
    at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:83)
    at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64)

org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-udp).failoverOnStop: java.lang.AssertionError: expected:<3> but was:<1>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-udp).nestedBeanFailover: java.lang.AssertionError: expected:<20030303> but was:<20010101>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-udp).jmsConnectionFactoryFailover: java.lang.AssertionError: expected:<3> but was:<1>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-udp).noFailover: java.lang.AssertionError: expected:<0> but was:<1>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-udp).simpleFailover: java.lang.AssertionError: expected:<3> but was:<1>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulTimeoutTestCase(SYNC-udp).timeout: java.lang.AssertionError: expected:<3> but was:<1>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

org.jboss.as.test.clustering.cluster.ejb.xpc.StatefulWithXPCFailoverTestCase(SYNC-udp).testBasicXPC: java.lang.AssertionError: expected:<200> but was:<500>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

org.jboss.as.test.clustering.cluster.ejb.xpc.StatefulWithXPCFailoverTestCase(SYNC-udp).testSecondLevelCache: org.junit.ComparisonFailure: expected:<[1]> but was:<[0]>
    at org.junit.Assert.assertEquals(Assert.java:115)
    at org.junit.Assert.assertEquals(Assert.java:144)

org.jboss.as.test.clustering.cluster.ejb.remote.RemoteFailoverTestCase(SYNC-udp).testSecureStatelessFailover: java.lang.AssertionError: 0 invocations were routed to node-1
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.assertTrue(Assert.java:41)

org.jboss.as.test.clustering.cluster.ejb.remote.RemoteFailoverTestCase(SYNC-udp).testStatelessFailover: java.lang.AssertionError: 0 invocations were routed to node-1
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.assertTrue(Assert.java:41)


##### there are 68 more failed tests, see build details

@pferraro
Copy link
Contributor Author

pferraro commented Oct 4, 2014

As I suspected - all udp-based tests fail on Linux (ipv6 only). Still investigating...

@wildfly-ci
Copy link

Windows Build 274 is now running using a merge of 876fbbd

@wildfly-ci
Copy link

Windows Build 274 outcome was FAILURE using a merge of 876fbbd
Summary: Exit code 1 (new) Build time: 0:00:27

Build problems:

Process exited with code 1

@wildfly-ci
Copy link

Windows Build 275 is now running using a merge of 876fbbd

@wildfly-ci
Copy link

Windows Build 275 outcome was FAILURE using a merge of 876fbbd
Summary: Tests failed: 3 (3 new), passed: 3254, ignored: 273, muted: 1 Build time: 1:31:39

Build problems:

Failed tests detected

Failed tests

org.jboss.as.test.clustering.extended.ejb2.stateful.passivation.dd.ClusterPassivationDDTestCase(SYNC-tcp-extended).defineMaps: java.lang.RuntimeException: Provider for type class java.net.URL returned a null value: org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider@1eb195f
    at org.jboss.arquillian.test.impl.enricher.resource.ArquillianResourceTestEnricher.lookup(ArquillianResourceTestEnricher.java:115)
    at org.jboss.arquillian.test.impl.enricher.resource.ArquillianResourceTestEnricher.resolve(ArquillianResourceTestEnricher.java:91)

org.jboss.as.test.clustering.extended.ejb2.stateless.RemoteStatelessFailoverTestCase(SYNC-tcp-extended).testLoadbalanceSpecifiedByDescriptor: java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:stateless-ejb2-failover-dd-test, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@1498552
    at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:749)
    at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:112)

org.jboss.as.test.clustering.extended.ejb2.stateless.RemoteStatelessFailoverTestCase(SYNC-tcp-extended).testLoadbalanceAnnotatedBean: java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:stateless-ejb2-failover-test, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@fd6b59
    at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:749)
    at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:112)

@wildfly-ci
Copy link

Linux Build 5127 is now running using a merge of 876fbbd

@wildfly-ci
Copy link

Linux Build 5128 is now running using a merge of 876fbbd

@wildfly-ci
Copy link

Linux Build 5129 is now running using a merge of 876fbbd

@wildfly-ci
Copy link

Linux Build 5130 is now running using a merge of 876fbbd

@wildfly-ci
Copy link

Linux Build 5128 outcome was FAILURE using a merge of 876fbbd
Summary: Tests failed: 2, passed: 3083, ignored: 260 Build time: 0:56:10

Build problems:

Failed tests detected

Failed tests

org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutRelayedToBackups: java.lang.AssertionError: expected:<200> but was:<500>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

org.jboss.as.test.manualmode.ejb.client.cluster.EJBClientClusterConfigurationTestCase.testServerToServerClusterFormation: javax.ejb.EJBException: java.lang.IllegalStateException: EJBCLIENT000029: No cluster context available for cluster named ejb
    at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:191)
    at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:276)

@wildfly-ci
Copy link

Linux Build 5127 outcome was FAILURE using a merge of 876fbbd
Summary: Tests failed: 2, passed: 3083, ignored: 260 Build time: 0:56:18

Build problems:

Failed tests detected

Failed tests

org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutRelayedToBackups: java.lang.AssertionError: expected:<200> but was:<500>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

org.jboss.as.test.manualmode.ejb.client.cluster.EJBClientClusterConfigurationTestCase.testServerToServerClusterFormation: javax.ejb.EJBException: java.lang.IllegalStateException: EJBCLIENT000029: No cluster context available for cluster named ejb
    at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:191)
    at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:276)

@wildfly-ci
Copy link

Linux Build 5129 outcome was FAILURE using a merge of 876fbbd
Summary: Tests failed: 2, passed: 3083, ignored: 260 Build time: 0:59:48

Build problems:

Failed tests detected

Failed tests

org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutRelayedToBackups: java.lang.AssertionError: expected:<200> but was:<500>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

org.jboss.as.test.manualmode.ejb.client.cluster.EJBClientClusterConfigurationTestCase.testServerToServerClusterFormation: javax.ejb.EJBException: java.lang.IllegalStateException: EJBCLIENT000029: No cluster context available for cluster named ejb
    at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:191)
    at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:276)

@wildfly-ci
Copy link

Linux Build 5130 outcome was FAILURE using a merge of 876fbbd
Summary: Tests failed: 2, passed: 3083, ignored: 260 Build time: 0:56:24

Build problems:

Failed tests detected

Failed tests

org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutRelayedToBackups: java.lang.AssertionError: expected:<200> but was:<500>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

org.jboss.as.test.manualmode.ejb.client.cluster.EJBClientClusterConfigurationTestCase.testServerToServerClusterFormation: javax.ejb.EJBException: java.lang.IllegalStateException: EJBCLIENT000029: No cluster context available for cluster named ejb
    at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:191)
    at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:276)

@wildfly-ci
Copy link

Linux with security manager Build 170 is now running using a merge of c2e1c75

@wildfly-ci
Copy link

Linux Build 5139 is now running using a merge of c2e1c75

@wildfly-ci
Copy link

Windows Build 285 is now running using a merge of c2e1c75

@wildfly-ci
Copy link

Linux with security manager Build 170 outcome was SUCCESS using a merge of c2e1c75
Summary: Tests passed: 790, ignored: 242 Build time: 0:06:19

@pferraro
Copy link
Contributor Author

pferraro commented Oct 7, 2014

OK - I've figured out what has changed in JGroups 3.5 to cause multicast discovery to break in the CI.

In the UDP protocol of JGroups 3.4, multicasts are sent and received via a MulticastSocket, while unicasts are sent and received via a DatagramSocket. On Linux, we would bind the MulticastSocket to the mcast_addr to eliminate cross-talking (see https://issues.jboss.org/browse/JBPAPP-1539), while the DatagramSocket is bound to the configured bind_addr (i.e. the loopback interface).
In the UDP protocol of JGroups 3.5, however, multicasts are only received via the multicast socket, and are sent via the same DatagramSocket that sends/receives unicasts. See:
https://issues.jboss.org/browse/JGRP-1765
belaban/JGroups@89440e0

Since this socket is bound to the loopback interface, datagram packets sent to the destination multicast (node-local) address are never received on the MulticastSocket - thus discovery doesn't work.

@ctomc @n1hility I suggest we modify the default parameters for the Linux agents on TC to use a valid non-loopback interface. Our testsuite sets the TTL for multicasts to 0, so network chatter shouldn't be an issue.

@wildfly-ci
Copy link

Linux Build 5139 outcome was FAILURE using a merge of c2e1c75
Summary: Tests failed: 2, passed: 3083, ignored: 260 Build time: 0:55:50

Build problems:

Failed tests detected

Failed tests

org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutRelayedToBackups: java.lang.AssertionError: expected:<200> but was:<500>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

org.jboss.as.test.manualmode.ejb.client.cluster.EJBClientClusterConfigurationTestCase.testServerToServerClusterFormation: javax.ejb.EJBException: java.lang.IllegalStateException: EJBCLIENT000028: No EJB receiver contexts available in cluster ejb
    at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:191)
    at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:276)

@wildfly-ci
Copy link

Linux Build 5161 is now running using a merge of 5702319

@wildfly-ci
Copy link

Linux Build 5162 is now running using a merge of 5702319

@wildfly-ci
Copy link

Linux Build 5162 outcome was FAILURE using a merge of 5702319
Summary: Exit code 143 (new); org.wildfly:wildfly-naming Build time: 0:00:21

Build problems:

Process exited with code 143

@wildfly-ci
Copy link

Linux Build 5163 is now running using a merge of 5702319

@wildfly-ci
Copy link

Linux Build 5163 outcome was FAILURE using a merge of 5702319
Summary: Tests failed: 37, passed: 877, ignored: 182 Build time: 0:19:16

Build problems:

Failed tests detected

Failed tests

org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).failoverOnStop: java.lang.AssertionError: expected:<3> but was:<1>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).nestedBeanFailover: java.lang.AssertionError: expected:<20030303> but was:<20010101>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).jmsConnectionFactoryFailover: java.lang.AssertionError: expected:<3> but was:<1>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).noFailover: java.lang.AssertionError: expected:<0> but was:<1>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).simpleFailover: java.lang.AssertionError: expected:<3> but was:<1>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulTimeoutTestCase(SYNC-tcp).timeout: java.lang.AssertionError: expected:<3> but was:<1>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

org.jboss.as.test.clustering.cluster.ejb.xpc.StatefulWithXPCFailoverTestCase(SYNC-tcp).testBasicXPC: java.lang.AssertionError: expected:<200> but was:<500>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

org.jboss.as.test.clustering.cluster.ejb.xpc.StatefulWithXPCFailoverTestCase(SYNC-tcp).testSecondLevelCache: org.junit.ComparisonFailure: expected:<[1]> but was:<[0]>
    at org.junit.Assert.assertEquals(Assert.java:115)
    at org.junit.Assert.assertEquals(Assert.java:144)

org.jboss.as.test.clustering.cluster.ejb.remote.RemoteFailoverTestCase(SYNC-tcp).testSecureStatelessFailover: java.lang.AssertionError: 0 invocations were routed to node-1
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.assertTrue(Assert.java:41)

org.jboss.as.test.clustering.cluster.ejb.remote.RemoteFailoverTestCase(SYNC-tcp).testStatelessFailover: java.lang.AssertionError: 0 invocations were routed to node-1
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.assertTrue(Assert.java:41)

org.jboss.as.test.clustering.cluster.ejb.remote.RemoteFailoverTestCase(SYNC-tcp).testStatefulFailover: java.lang.IllegalStateException: EJBCLIENT000029: No cluster context available for cluster named ejb
    at org.jboss.ejb.client.EJBClientContext.requireClusterEJBReceiverContext(EJBClientContext.java:989)
    at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:84)


##### there are 27 more failed tests, see build details

@wildfly-ci
Copy link

Linux Build 5164 is now running using a merge of 5702319

@wildfly-ci
Copy link

Linux Build 5164 outcome was FAILURE using a merge of 5702319
Summary: Tests failed: 1, passed: 913, ignored: 182 Build time: 0:19:33

Build problems:

Failed tests detected

Failed tests

org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutRelayedToBackups: java.lang.AssertionError: expected:<200> but was:<500>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

@wildfly-ci
Copy link

Linux Build 5165 is now running using a merge of 5702319

@wildfly-ci
Copy link

Linux Build 5166 is now running using a merge of 5702319

@wildfly-ci
Copy link

Linux Build 5166 outcome was SUCCESS using a merge of 5702319
Summary: Tests passed: 994, ignored: 180 Build time: 0:18:30

@wildfly-ci
Copy link

Windows Build 301 is now running using a merge of b346323

@wildfly-ci
Copy link

Linux Build 5169 is now running using a merge of b346323

@wildfly-ci
Copy link

Linux with security manager Build 186 is now running using a merge of b346323

@wildfly-ci
Copy link

Linux Build 5170 is now running using a merge of b346323

@wildfly-ci
Copy link

Linux Build 5171 is now running using a merge of 8e87a5c

@wildfly-ci
Copy link

Linux with security manager Build 187 is now running using a merge of 8e87a5c

@wildfly-ci
Copy link

Windows Build 302 is now running using a merge of 8e87a5c

@wildfly-ci
Copy link

Linux with security manager Build 187 outcome was SUCCESS using a merge of 8e87a5c
Summary: Tests passed: 755, ignored: 243 Build time: 0:30:11

@wildfly-ci
Copy link

Linux Build 5170 outcome was FAILURE using a merge of 8e87a5c
Summary: Tests failed: 7 (7 new), passed: 3077, ignored: 261 Build time: 0:56:22

Build problems:

Failed tests detected

Failed tests

org.jboss.as.test.integration.ws.wsse.signencrypt.EJBSignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromAlice: javax.xml.ws.WebServiceException: Could not send Message.
    at java.net.SocketInputStream.socketRead0(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:152)

org.jboss.as.test.integration.domain.management.cli.DomainDeploymentOverlayTestCase.testSimpleOverrideWithRedeployAffected: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:9990
    at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
    at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)

org.jboss.as.test.integration.domain.management.cli.DomainDeploymentOverlayTestCase.testWildcardOverrideWithRedeployAffected: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:9990
    at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
    at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)

org.jboss.as.test.integration.domain.management.cli.DomainDeploymentOverlayTestCase.testSimpleOverride: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:9990
    at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
    at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)

org.jboss.as.test.integration.domain.management.cli.DomainDeploymentOverlayTestCase.testWildcardOverride: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:9990
    at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
    at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)

org.jboss.as.test.integration.domain.management.cli.DomainDeploymentOverlayTestCase.testMultipleLinks: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:9990
    at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
    at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)

org.jboss.as.test.integration.domain.management.cli.DomainDeploymentOverlayTestCase.testRedeployAffected: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:9990
    at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
    at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)

@wildfly-ci
Copy link

Windows Build 302 outcome was SUCCESS using a merge of 8e87a5c
Summary: Tests passed: 3084, ignored: 261 Build time: 0:58:20

@wildfly-ci
Copy link

Linux Build 5171 outcome was FAILURE using a merge of 8e87a5c
Summary: Tests failed: 38 (38 new), passed: 3046, ignored: 261 Build time: 1:00:18

Build problems:

Failed tests detected

Failed tests

org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).failoverOnStop: java.lang.AssertionError: expected:<3> but was:<1>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).nestedBeanFailover: java.lang.AssertionError: expected:<20030303> but was:<20010101>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).jmsConnectionFactoryFailover: java.lang.AssertionError: expected:<3> but was:<1>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).noFailover: java.lang.AssertionError: expected:<0> but was:<1>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).simpleFailover: java.lang.AssertionError: expected:<3> but was:<1>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulTimeoutTestCase(SYNC-tcp).timeout: java.lang.AssertionError: expected:<3> but was:<1>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

org.jboss.as.test.clustering.cluster.ejb.xpc.StatefulWithXPCFailoverTestCase(SYNC-tcp).testBasicXPC: java.lang.AssertionError: expected:<200> but was:<500>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

org.jboss.as.test.clustering.cluster.ejb.xpc.StatefulWithXPCFailoverTestCase(SYNC-tcp).testSecondLevelCache: org.junit.ComparisonFailure: expected:<[1]> but was:<[0]>
    at org.junit.Assert.assertEquals(Assert.java:115)
    at org.junit.Assert.assertEquals(Assert.java:144)

org.jboss.as.test.clustering.cluster.ejb.remote.RemoteFailoverTestCase(SYNC-tcp).testSecureStatelessFailover: java.lang.AssertionError: 0 invocations were routed to node-1
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.assertTrue(Assert.java:41)

org.jboss.as.test.clustering.cluster.ejb.remote.RemoteFailoverTestCase(SYNC-tcp).testStatelessFailover: java.lang.AssertionError: 0 invocations were routed to node-1
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.assertTrue(Assert.java:41)

org.jboss.as.test.clustering.cluster.ejb.remote.RemoteFailoverTestCase(SYNC-tcp).testStatefulFailover: java.lang.IllegalStateException: EJBCLIENT000029: No cluster context available for cluster named ejb
    at org.jboss.ejb.client.EJBClientContext.requireClusterEJBReceiverContext(EJBClientContext.java:989)
    at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:84)


##### there are 28 more failed tests, see build details

@wildfly-ci
Copy link

Linux Build 5175 is now running using a merge of 8e87a5c

@wildfly-ci
Copy link

Linux Build 5175 outcome was FAILURE using a merge of 8e87a5c
Summary: Tests failed: 8 (8 new), passed: 3075, ignored: 261, muted: 1 Build time: 0:55:56

Build problems:

Failed tests detected

Failed tests

org.jboss.as.test.manualmode.web.ssl.CertificateRolesLoginModuleTestCase.startAndSetupContainer: java.io.IOException: java.util.concurrent.CancellationException: Operation was cancelled
    at org.jboss.threads.AsyncFutureTask.operationCancelled(AsyncFutureTask.java:70)
    at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:267)

org.jboss.as.test.manualmode.web.ssl.CertificateRolesLoginModuleTestCase.testDatabaseCertLoginModule: java.net.ConnectException: Connection refused
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)

org.jboss.as.test.integration.domain.management.cli.DomainDeploymentOverlayTestCase.testSimpleOverrideWithRedeployAffected: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:9990
    at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
    at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)

org.jboss.as.test.integration.domain.management.cli.DomainDeploymentOverlayTestCase.testWildcardOverrideWithRedeployAffected: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:9990
    at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
    at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)

org.jboss.as.test.integration.domain.management.cli.DomainDeploymentOverlayTestCase.testSimpleOverride: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:9990
    at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
    at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)

org.jboss.as.test.integration.domain.management.cli.DomainDeploymentOverlayTestCase.testWildcardOverride: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:9990
    at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
    at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)

org.jboss.as.test.integration.domain.management.cli.DomainDeploymentOverlayTestCase.testMultipleLinks: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:9990
    at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
    at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)

org.jboss.as.test.integration.domain.management.cli.DomainDeploymentOverlayTestCase.testRedeployAffected: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:9990
    at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
    at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)

@pferraro
Copy link
Contributor Author

Superseded by #6805 which contains environment changes needed for tests to pass w/ipv6. Closing.

@pferraro pferraro closed this Oct 11, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants