[
https://issues.jboss.org/browse/AS7-5288?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on AS7-5288:
------------------------------------
I've already got the access to EC2. In the output of IIOP tests I can see failures
like:
{noformat}
10:54:19,507 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed
to start service jboss.serverManagement.controller.management.http:
org.jboss.msc.service.StartException in service
jboss.serverManagement.controller.management.http: Address already in use /127.0.0.1:9990
at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:214)
[jboss-as-server.jar:7.1.2.Final-redhat-1]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
[jboss-msc.jar:1.0.2.GA-redhat-1]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
[jboss-msc.jar:1.0.2.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[rt.jar:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
[rt.jar:1.6.0_24]
at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24]
Caused by: java.net.BindException: Address already in use
{noformat}
Also according to the following snippet of job console it looks like node0 and node1 are
both set to 127.0.0.1, am I right?
{noformat}
[xslt] Processing
/mnt/workspace/EAP6-EC2/jboss-as/testsuite/integration/iiop/target/jbossas-iiop-client/standalone/configuration/standalone.xml
to
/mnt/workspace/EAP6-EC2/jboss-as/testsuite/integration/iiop/target/jbossas-iiop-client/standalone/configuration/standalone.xml.mod
[move] Moving 3 files to
/mnt/workspace/EAP6-EC2/jboss-as/testsuite/integration/iiop/target/jbossas-iiop-client/standalone/configuration
[echo] === Changing IP addresses for config jbossas-iiop-client ===
[echo] node: 127.0.0.1
[echo] ant.mcast: @{ant.mcast}
.
.
[xslt] Processing
/mnt/workspace/EAP6-EC2/jboss-as/testsuite/integration/iiop/target/jbossas-iiop-server/standalone/configuration/standalone.xml
to
/mnt/workspace/EAP6-EC2/jboss-as/testsuite/integration/iiop/target/jbossas-iiop-server/standalone/configuration/standalone.xml.mod
[move] Moving 3 files to
/mnt/workspace/EAP6-EC2/jboss-as/testsuite/integration/iiop/target/jbossas-iiop-server/standalone/configuration
[echo] === Changing IP addresses for config jbossas-iiop-server ===
[echo] node: 127.0.0.1
[echo] ant.mcast: @{ant.mcast}
{noformat}
Multinode transaction tests failed because of
{noformat}
The server is already running! Managed containers does not support connecting to running
server instances due to the possible harmful effect of connecting to the wrong server.
Please stop server before running or change to another type of container. To disable this
check and allow Arquillian to connect to a running server, set
allowConnectingToRunningServer to true in the container configuration
{noformat}
Isn't this just an configuration issue?
Tests failing Intermittently on slow machines -
iiop.basic.BasicIIOPInvocationTestCase
--------------------------------------------------------------------------------------
Key: AS7-5288
URL:
https://issues.jboss.org/browse/AS7-5288
Project: Application Server 7
Issue Type: Bug
Components: Test Suite
Affects Versions: 7.1.2.Final (EAP)
Reporter: Ondrej Zizka
Assignee: Stuart Douglas
These tests fail intermittently on really slow machines.
To reproduce, try to run in EC2 on 32-bit "small" instance type.
https://jenkins-jbossqa.rhcloud.com/job/EAP6-EC2/61/#showFailuresLink
org.jboss.as.test.iiop.basic.BasicIIOPInvocationTestCase.testRemoteIIOPInvocation
org.jboss.as.test.iiop.basic.BasicIIOPInvocationTestCase.testHomeHandle
org.jboss.as.test.iiop.basic.BasicIIOPInvocationTestCase.testHandle
org.jboss.as.test.iiop.basic.BasicIIOPInvocationTestCase.testWrappedHandle
org.jboss.as.test.iiop.basic.BasicIIOPInvocationTestCase.testEjbMetadata
org.jboss.as.test.iiop.basic.BasicIIOPInvocationTestCase.testIsIdentical
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira