[jboss-jira] [JBoss JIRA] (WFLY-12753) Intermittent failure in LastNodeToLeaveRemoteEJBTestCase

[Brian Stansberry (Jira)]

Brian Stansberry created WFLY-12753:
---------------------------------------

             Summary: Intermittent failure in LastNodeToLeaveRemoteEJBTestCase
                 Key: WFLY-12753
                 URL: https://issues.jboss.org/browse/WFLY-12753
             Project: WildFly
          Issue Type: Bug
          Components: Clustering
            Reporter: Brian Stansberry
            Assignee: Paul Ferraro


It's getting fairly common lately to see dozens/hundreds of failures like at https://ci.wildfly.org/viewLog.html?buildId=173641&buildTypeId=WF_PullRequest_LinuxSm&tab=buildResultsDiv

Problem is LastNodeToLeaveRemoteEJBTestCase, first test class run in a surefire execution, fails due to a port conflict, perhaps a leftover process.

{code}
[21:59:27][Step 2/3] [INFO] Running org.jboss.as.test.clustering.cluster.ejb.remote.byteman.LastNodeToLeaveRemoteEJBTestCase
[21:59:36][Step 2/3] [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 8.321 s <<< FAILURE! - in org.jboss.as.test.clustering.cluster.ejb.remote.byteman.LastNodeToLeaveRemoteEJBTestCase
[21:59:36][Step 2/3] [ERROR] testDNRContentsAfterLastNodeToLeave(org.jboss.as.test.clustering.cluster.ejb.remote.byteman.LastNodeToLeaveRemoteEJBTestCase)  Time elapsed: 6.8 s  <<< ERROR!
[21:59:36][Step 2/3] org.jboss.arquillian.container.spi.client.container.LifecycleException: 
[21:59:36][Step 2/3] The port 10090 is already in use. It means that either the server might be already running or there is another process using port 10090.
[21:59:36][Step 2/3] Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server.
[21:59:36][Step 2/3] Please stop server (or another process) before running, change to another type of container (e.g. remote) or use jboss.socket.binding.port-offset variable to change the default port.
[21:59:36][Step 2/3] To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
[21:59:36][Step 2/3] 	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:323)
[21:59:36][Step 2/3] 	at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:81)
[21:59:36][Step 2/3] 	at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:123)
[21:59:36][Step 2/3] 	at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:179)
{code}



--
This message was sent by Atlassian Jira
(v7.13.8#713008)