[JBoss JIRA] (JBTM-3231) LRA testrecovery2 fails
by Anonymous (Jira)
[ https://issues.redhat.com/browse/JBTM-3231?page=com.atlassian.jira.plugin... ]
Issue was automatically transitioned when mayankkunwar created pull request #1560 in GitHub
-------------------------------------------------------------------------------------------
Status: Pull Request Sent (was: Reopened)
> LRA testrecovery2 fails
> -----------------------
>
> Key: JBTM-3231
> URL: https://issues.redhat.com/browse/JBTM-3231
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: LRA, Testing
> Affects Versions: 5.10.1.Final
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Priority: Minor
> Fix For: 5.10.3.Final
>
>
> CI testing:
> LRACoordinatorTestCase=testRecovery2 fails to restart the container after crashing via byteman. Seems to be intermittent on Amsterdam CI and more consistent on Upshift, for example:
> http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/552/
> https://ci-master-jenkins-csb-narayana.cloud.paas.psi.redhat.com/job/nara...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 10 months
- 1
- 0
[JBoss JIRA] (JBTM-3255) Intermittent failure of CI AS_TESTS in multinode module with error `The port 10090 is already in use`
by Ondrej Chaloupka (Jira)
[ https://issues.redhat.com/browse/JBTM-3255?page=com.atlassian.jira.plugin... ]
Ondrej Chaloupka edited comment on JBTM-3255 at 2/18/20 11:06 AM:
------------------------------------------------------------------
I created a WFLY issue which aims for the "stuck stop operation" being timeouted: WFLY-13123
was (Author: ochaloup):
I created a WFLY issue which for the stuck stop operation to be timeouted: WFLY-13123
> Intermittent failure of CI AS_TESTS in multinode module with error `The port 10090 is already in use`
> -----------------------------------------------------------------------------------------------------
>
> Key: JBTM-3255
> URL: https://issues.redhat.com/browse/JBTM-3255
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Testing
> Reporter: Ondrej Chaloupka
> Assignee: Ondrej Chaloupka
> Priority: Minor
> Attachments: JBTM-3255-occupied-port-10990.zip
>
>
> There could be observed intermittent failures of AS_TESTS in Narayana CI where the job fails with error {{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.}}[1]
> The reason seems to be there is probably unfinished application server running from the prior testsuite module.
> Here we talk about the second server which starts the port `10090` as the management port.
> The arquillian starts the `multinode` module and the first test fails with error that the WildFly can't be started as port can't be bound.
> It could be that there is either some process occupying the port `10090` on the Linux machine.
> But the more probable is that the prior test which is in `clustering` as `org.jboss.as.test.clustering.cluster.ejb2.stateful.failover.RemoteEJBClientStatefulBeanFailoverTestCase` was not finished properly.
> The log files does not show any particular trouble though.
> [1]
> {code}
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.818 s <<< FAILURE! - in org.jboss.as.test.multinode.clientinterceptor.multiple.MultipleClientInterceptorTestCase
> [ERROR] org.jboss.as.test.multinode.clientinterceptor.multiple.MultipleClientInterceptorTestCase Time elapsed: 3.818 s <<< ERROR!
> org.jboss.arquillian.container.spi.client.container.LifecycleException:
> 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.
> Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server.
> 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.
> To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
> at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:323)
> at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:81)
> at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:123)
> at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:179)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:137)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:133)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:208)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:133)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
> at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:54)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:105)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:62)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:64)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:181)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:64)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:105)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:62)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:83)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:69)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:105)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:71)
> at org.jboss.arquillian.junit.AdaptorManager.initializeAdaptor(AdaptorManager.java:23)
> at org.jboss.arquillian.junit.AdaptorManagerWithNotifier.initializeAdaptor(AdaptorManagerWithNotifier.java:19)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:109)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 10 months
- 1
- 0
[JBoss JIRA] (JBTM-3255) Intermittent failure of CI AS_TESTS in multinode module with error `The port 10090 is already in use`
by Ondrej Chaloupka (Jira)
[ https://issues.redhat.com/browse/JBTM-3255?page=com.atlassian.jira.plugin... ]
Ondrej Chaloupka commented on JBTM-3255:
----------------------------------------
I created a WFLY issue which for the stuck stop operation to be timeouted: WFLY-13123
> Intermittent failure of CI AS_TESTS in multinode module with error `The port 10090 is already in use`
> -----------------------------------------------------------------------------------------------------
>
> Key: JBTM-3255
> URL: https://issues.redhat.com/browse/JBTM-3255
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Testing
> Reporter: Ondrej Chaloupka
> Assignee: Ondrej Chaloupka
> Priority: Minor
> Attachments: JBTM-3255-occupied-port-10990.zip
>
>
> There could be observed intermittent failures of AS_TESTS in Narayana CI where the job fails with error {{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.}}[1]
> The reason seems to be there is probably unfinished application server running from the prior testsuite module.
> Here we talk about the second server which starts the port `10090` as the management port.
> The arquillian starts the `multinode` module and the first test fails with error that the WildFly can't be started as port can't be bound.
> It could be that there is either some process occupying the port `10090` on the Linux machine.
> But the more probable is that the prior test which is in `clustering` as `org.jboss.as.test.clustering.cluster.ejb2.stateful.failover.RemoteEJBClientStatefulBeanFailoverTestCase` was not finished properly.
> The log files does not show any particular trouble though.
> [1]
> {code}
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.818 s <<< FAILURE! - in org.jboss.as.test.multinode.clientinterceptor.multiple.MultipleClientInterceptorTestCase
> [ERROR] org.jboss.as.test.multinode.clientinterceptor.multiple.MultipleClientInterceptorTestCase Time elapsed: 3.818 s <<< ERROR!
> org.jboss.arquillian.container.spi.client.container.LifecycleException:
> 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.
> Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server.
> 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.
> To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
> at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:323)
> at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:81)
> at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:123)
> at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:179)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:137)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:133)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:208)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:133)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
> at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:54)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:105)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:62)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:64)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:181)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:64)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:105)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:62)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:83)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:69)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:105)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:71)
> at org.jboss.arquillian.junit.AdaptorManager.initializeAdaptor(AdaptorManager.java:23)
> at org.jboss.arquillian.junit.AdaptorManagerWithNotifier.initializeAdaptor(AdaptorManagerWithNotifier.java:19)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:109)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 10 months
- 1
- 0
[JBoss JIRA] (JBTM-3255) Intermittent failure of CI AS_TESTS in multinode module with error `The port 10090 is already in use`
by Ondrej Chaloupka (Jira)
[ https://issues.redhat.com/browse/JBTM-3255?page=com.atlassian.jira.plugin... ]
Ondrej Chaloupka commented on JBTM-3255:
----------------------------------------
[~tomjenkinson] agree. I investigated more deeper and what I can see it's really the trouble with the {{RemoteEJBClientStatefulBeanFailoverTestCase}} which does not finish the server properly. As there is long time when the test is inactive then the maven surefire (probably) comes and kills the forked JVM process.
The dump file says
{code}
# Created at 2019-12-04T12:07:17.504
Killing self fork JVM. Received SHUTDOWN command from Maven shutdown hook.
{code}
>From what I investigated the trouble is that server stopping for more than hour and it's not stopped. The test waits for the server to be stopped which never happens. The test is stuck and could not clean resources - aka. it's not able to finish with the second server which is still running and waiting for the command to be stopped.
I uploaded the wildfly {{server.log}}s for the both wildfly servers which are running for this test (https://issues.redhat.com/secure/attachment/12465753/JBTM-3255-occupied-p...).
The process seems to be that the test {{RemoteEJBClientStatefulBeanFailoverTestCase}} did some testing, in the middle of the testcase one of the servers should be stopped. In this case it tried to stop the server {{wildfly-1}}. But it failed to be finished. In the {{wildfly-2}} log we can see there is long time pause
{code}
2019-12-04 10:46:20,840 INFO [org.infinispan.CLUSTER] (remote-thread--p7-t1) [Context=RemoteEJBClientStatefulFailoverTestBase.jar/infinispan] ISPN100010: Finished rebalance with members [node-1, node-2], topology id 5
2019-12-04 10:46:21,093 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "RemoteEJBClientStatefulFailoverTestBase.jar" (runtime-name : "RemoteEJBClientStatefulFailoverTestBase.jar")
2019-12-04 10:46:21,455 INFO [org.infinispan.CLUSTER] (remote-thread--p7-t1) [Context=RemoteEJBClientStatefulFailoverTestBase.jar/infinispan] ISPN100008: Updating cache members list [node-2], topology id 6
2019-12-04 10:46:21,498 INFO [org.infinispan.CLUSTER] (remote-thread--p7-t1) [Context=client-mappings] ISPN100008: Updating cache members list [node-2], topology id 29
2019-12-04 12:07:36,409 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) WFLYMAIL0002: Unbound mail session [java:jboss/mail/Default]
2019-12-04 12:07:36,412 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-5) ISPN000080: Disconnecting JGroups channel ejb
2019-12-04 12:07:36,412 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000080: Disconnecting JGroups channel ejb
2019-12-04 12:07:36,414 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000080: Disconnecting JGroups channel ejb
2019-12-04 12:07:36,415 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0019: Host default-host stopping
{code}
The server log of {{wildfly-1}} says that it's stopping but it never says {{stopped}} (like is normal that WildFly report line {{WFLYSRV0050: WildFly Full 20.0.0.Beta1-SNAPSHOT (WildFly Core 11.0.0.Beta8) stopped in 230ms}}). The {{wildfly-1}} says only:
{code}
2019-12-04 10:46:21,509 INFO [org.apache.activemq.artemis.ra] (ServerService Thread Pool -- 35) AMQ151003: resource adaptor stopped
2019-12-04 10:46:22,601 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 35) AMQ221002: Apache ActiveMQ Artemis Message Broker version 2.10.1 [0fd79ee7-1682-11ea-8e07-0242ac11000a] stopped, uptime 19.343 seconds
2019-12-04 10:46:22,602 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0008: Undertow HTTP listener default suspending
2019-12-04 10:46:22,605 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080
2019-12-04 10:46:22,605 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0004: Undertow 2.0.28.Final stopping
{code}
> Intermittent failure of CI AS_TESTS in multinode module with error `The port 10090 is already in use`
> -----------------------------------------------------------------------------------------------------
>
> Key: JBTM-3255
> URL: https://issues.redhat.com/browse/JBTM-3255
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Testing
> Reporter: Ondrej Chaloupka
> Assignee: Ondrej Chaloupka
> Priority: Minor
> Attachments: JBTM-3255-occupied-port-10990.zip
>
>
> There could be observed intermittent failures of AS_TESTS in Narayana CI where the job fails with error {{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.}}[1]
> The reason seems to be there is probably unfinished application server running from the prior testsuite module.
> Here we talk about the second server which starts the port `10090` as the management port.
> The arquillian starts the `multinode` module and the first test fails with error that the WildFly can't be started as port can't be bound.
> It could be that there is either some process occupying the port `10090` on the Linux machine.
> But the more probable is that the prior test which is in `clustering` as `org.jboss.as.test.clustering.cluster.ejb2.stateful.failover.RemoteEJBClientStatefulBeanFailoverTestCase` was not finished properly.
> The log files does not show any particular trouble though.
> [1]
> {code}
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.818 s <<< FAILURE! - in org.jboss.as.test.multinode.clientinterceptor.multiple.MultipleClientInterceptorTestCase
> [ERROR] org.jboss.as.test.multinode.clientinterceptor.multiple.MultipleClientInterceptorTestCase Time elapsed: 3.818 s <<< ERROR!
> org.jboss.arquillian.container.spi.client.container.LifecycleException:
> 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.
> Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server.
> 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.
> To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
> at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:323)
> at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:81)
> at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:123)
> at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:179)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:137)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:133)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:208)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:133)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
> at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:54)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:105)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:62)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:64)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:181)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:64)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:105)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:62)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:83)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:69)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:105)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:71)
> at org.jboss.arquillian.junit.AdaptorManager.initializeAdaptor(AdaptorManager.java:23)
> at org.jboss.arquillian.junit.AdaptorManagerWithNotifier.initializeAdaptor(AdaptorManagerWithNotifier.java:19)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:109)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 10 months
- 1
- 0
[JBoss JIRA] (JBTM-3255) Intermittent failure of CI AS_TESTS in multinode module with error `The port 10090 is already in use`
by Ondrej Chaloupka (Jira)
[ https://issues.redhat.com/browse/JBTM-3255?page=com.atlassian.jira.plugin... ]
Ondrej Chaloupka updated JBTM-3255:
-----------------------------------
Attachment: JBTM-3255-occupied-port-10990.zip
> Intermittent failure of CI AS_TESTS in multinode module with error `The port 10090 is already in use`
> -----------------------------------------------------------------------------------------------------
>
> Key: JBTM-3255
> URL: https://issues.redhat.com/browse/JBTM-3255
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Testing
> Reporter: Ondrej Chaloupka
> Assignee: Ondrej Chaloupka
> Priority: Minor
> Attachments: JBTM-3255-occupied-port-10990.zip
>
>
> There could be observed intermittent failures of AS_TESTS in Narayana CI where the job fails with error {{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.}}[1]
> The reason seems to be there is probably unfinished application server running from the prior testsuite module.
> Here we talk about the second server which starts the port `10090` as the management port.
> The arquillian starts the `multinode` module and the first test fails with error that the WildFly can't be started as port can't be bound.
> It could be that there is either some process occupying the port `10090` on the Linux machine.
> But the more probable is that the prior test which is in `clustering` as `org.jboss.as.test.clustering.cluster.ejb2.stateful.failover.RemoteEJBClientStatefulBeanFailoverTestCase` was not finished properly.
> The log files does not show any particular trouble though.
> [1]
> {code}
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.818 s <<< FAILURE! - in org.jboss.as.test.multinode.clientinterceptor.multiple.MultipleClientInterceptorTestCase
> [ERROR] org.jboss.as.test.multinode.clientinterceptor.multiple.MultipleClientInterceptorTestCase Time elapsed: 3.818 s <<< ERROR!
> org.jboss.arquillian.container.spi.client.container.LifecycleException:
> 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.
> Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server.
> 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.
> To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
> at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:323)
> at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:81)
> at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:123)
> at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:179)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:137)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:133)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:208)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:133)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
> at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:54)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:105)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:62)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:64)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:181)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:64)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:105)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:62)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:83)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:69)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:105)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:71)
> at org.jboss.arquillian.junit.AdaptorManager.initializeAdaptor(AdaptorManager.java:23)
> at org.jboss.arquillian.junit.AdaptorManagerWithNotifier.initializeAdaptor(AdaptorManagerWithNotifier.java:19)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:109)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 10 months
- 1
- 0
[JBoss JIRA] (JBTM-3255) Intermittent failure of CI AS_TESTS in multinode module with error `The port 10090 is already in use`
by Thomas Jenkinson (Jira)
[ https://issues.redhat.com/browse/JBTM-3255?page=com.atlassian.jira.plugin... ]
Thomas Jenkinson commented on JBTM-3255:
----------------------------------------
[~ochaloup] could it be that the dump file (you can find one in either http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/553/PROFILE=AS_TE... or http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/549/PROFILE=AS_TE... depending on which run you are looking it) relates to RemoteEJBClientStatefulBeanFailoverTestCase in both cases? That might explain why the following tests find a running server; perhaps the first process had to be killed and so it did not clean up?
> Intermittent failure of CI AS_TESTS in multinode module with error `The port 10090 is already in use`
> -----------------------------------------------------------------------------------------------------
>
> Key: JBTM-3255
> URL: https://issues.redhat.com/browse/JBTM-3255
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Testing
> Reporter: Ondrej Chaloupka
> Assignee: Ondrej Chaloupka
> Priority: Minor
>
> There could be observed intermittent failures of AS_TESTS in Narayana CI where the job fails with error {{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.}}[1]
> The reason seems to be there is probably unfinished application server running from the prior testsuite module.
> Here we talk about the second server which starts the port `10090` as the management port.
> The arquillian starts the `multinode` module and the first test fails with error that the WildFly can't be started as port can't be bound.
> It could be that there is either some process occupying the port `10090` on the Linux machine.
> But the more probable is that the prior test which is in `clustering` as `org.jboss.as.test.clustering.cluster.ejb2.stateful.failover.RemoteEJBClientStatefulBeanFailoverTestCase` was not finished properly.
> The log files does not show any particular trouble though.
> [1]
> {code}
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.818 s <<< FAILURE! - in org.jboss.as.test.multinode.clientinterceptor.multiple.MultipleClientInterceptorTestCase
> [ERROR] org.jboss.as.test.multinode.clientinterceptor.multiple.MultipleClientInterceptorTestCase Time elapsed: 3.818 s <<< ERROR!
> org.jboss.arquillian.container.spi.client.container.LifecycleException:
> 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.
> Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server.
> 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.
> To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
> at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:323)
> at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:81)
> at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:123)
> at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:179)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:137)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:133)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:208)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:133)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
> at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:54)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:105)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:62)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:64)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:181)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:64)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:105)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:62)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:83)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:69)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:105)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:71)
> at org.jboss.arquillian.junit.AdaptorManager.initializeAdaptor(AdaptorManager.java:23)
> at org.jboss.arquillian.junit.AdaptorManagerWithNotifier.initializeAdaptor(AdaptorManagerWithNotifier.java:19)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:109)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 10 months
- 1
- 0
[JBoss JIRA] (JBTM-3255) Intermittent failure of CI AS_TESTS in multinode module with error `The port 10090 is already in use`
by Ondrej Chaloupka (Jira)
[ https://issues.redhat.com/browse/JBTM-3255?page=com.atlassian.jira.plugin... ]
Ondrej Chaloupka commented on JBTM-3255:
----------------------------------------
[~tomjenkinson] I can see in the console output and the same in the artifacts that the test did not output the results. See e.g.
{code}
....
[INFO] Running org.jboss.as.test.clustering.cluster.ejb.xpc.StatefulWithXPCFailoverTestCase
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 41.514 s - in org.jboss.as.test.clustering.cluster.ejb.xpc.StatefulWithXPCFailoverTestCase
[INFO] Running org.jboss.as.test.clustering.cluster.ejb2.stateful.failover.RemoteEJBClientStatefulBeanFailoverTestCase
[INFO]
[INFO] Results:
[INFO]
[WARNING] Tests run: 37, Failures: 0, Errors: 0, Skipped: 5
{code}
it can be seen that the {{StatefulWithXPCFailoverTestCase}} ran 2 tests in 41 seconds. This output is not shown for the {{RemoteEJBClientStatefulBeanFailoverTestCase}}. There is no test output saved artifact under `target/surefire...` folder for the test. I'm not sure why it's so unfortunately.
> Intermittent failure of CI AS_TESTS in multinode module with error `The port 10090 is already in use`
> -----------------------------------------------------------------------------------------------------
>
> Key: JBTM-3255
> URL: https://issues.redhat.com/browse/JBTM-3255
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Testing
> Reporter: Ondrej Chaloupka
> Assignee: Ondrej Chaloupka
> Priority: Minor
>
> There could be observed intermittent failures of AS_TESTS in Narayana CI where the job fails with error {{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.}}[1]
> The reason seems to be there is probably unfinished application server running from the prior testsuite module.
> Here we talk about the second server which starts the port `10090` as the management port.
> The arquillian starts the `multinode` module and the first test fails with error that the WildFly can't be started as port can't be bound.
> It could be that there is either some process occupying the port `10090` on the Linux machine.
> But the more probable is that the prior test which is in `clustering` as `org.jboss.as.test.clustering.cluster.ejb2.stateful.failover.RemoteEJBClientStatefulBeanFailoverTestCase` was not finished properly.
> The log files does not show any particular trouble though.
> [1]
> {code}
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.818 s <<< FAILURE! - in org.jboss.as.test.multinode.clientinterceptor.multiple.MultipleClientInterceptorTestCase
> [ERROR] org.jboss.as.test.multinode.clientinterceptor.multiple.MultipleClientInterceptorTestCase Time elapsed: 3.818 s <<< ERROR!
> org.jboss.arquillian.container.spi.client.container.LifecycleException:
> 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.
> Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server.
> 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.
> To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
> at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:323)
> at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:81)
> at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:123)
> at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:179)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:137)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:133)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:208)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:133)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
> at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:54)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:105)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:62)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:64)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:181)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:64)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:105)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:62)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:83)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:69)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:105)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:71)
> at org.jboss.arquillian.junit.AdaptorManager.initializeAdaptor(AdaptorManager.java:23)
> at org.jboss.arquillian.junit.AdaptorManagerWithNotifier.initializeAdaptor(AdaptorManagerWithNotifier.java:19)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:109)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 10 months
- 1
- 0
[JBoss JIRA] (JBTM-3256) Reduce memory limit for docker containers in CI
by Thomas Jenkinson (Jira)
[ https://issues.redhat.com/browse/JBTM-3256?page=com.atlassian.jira.plugin... ]
Thomas Jenkinson commented on JBTM-3256:
----------------------------------------
jtax
{code}
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.20:test (surefire-jacorb) on project jtax: There are test failures.
[ERROR]
[ERROR] Please refer to /home/jenkins/workspace/narayana/PROFILE/JACOCO/jdk/jdk8.latest/label/linux/ArjunaJTS/jtax/target/surefire-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] ExecutionException The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ERROR] Command was /bin/sh -c cd /home/jenkins/workspace/narayana/PROFILE/JACOCO/jdk/jdk8.latest/label/linux/ArjunaJTS/jtax/target/test-classes && /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.181-3.b13.el7_5.x86_64/jre/bin/java -javaagent:/home/jenkins/.m2/repository/org/jacoco/org.jacoco.agent/0.8.3/org.jacoco.agent-0.8.3-runtime.jar=destfile=/home/jenkins/workspace/narayana/PROFILE/JACOCO/jdk/jdk8.latest/label/linux/ArjunaJTS/jtax/target/coverage-reports/jacoco-ut.exec -Djdk.attach.allowAttachSelf=true -jar /home/jenkins/workspace/narayana/PROFILE/JACOCO/jdk/jdk8.latest/label/linux/ArjunaJTS/jtax/target/surefire/surefirebooter4780163676044108109.jar /home/jenkins/workspace/narayana/PROFILE/JACOCO/jdk/jdk8.latest/label/linux/ArjunaJTS/jtax/target/surefire 2019-11-13T22-51-07_912-jvmRun1 surefire3039402205093478853tmp surefire_6686281639749406541782tmp
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 137
[ERROR] Crashed tests:
[ERROR] com.hp.mwtests.ts.jta.jts.subordinate.SubordinateTestCase
[ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: ExecutionException The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ERROR] Command was /bin/sh -c cd /home/jenkins/workspace/narayana/PROFILE/JACOCO/jdk/jdk8.latest/label/linux/ArjunaJTS/jtax/target/test-classes && /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.181-3.b13.el7_5.x86_64/jre/bin/java -javaagent:/home/jenkins/.m2/repository/org/jacoco/org.jacoco.agent/0.8.3/org.jacoco.agent-0.8.3-runtime.jar=destfile=/home/jenkins/workspace/narayana/PROFILE/JACOCO/jdk/jdk8.latest/label/linux/ArjunaJTS/jtax/target/coverage-reports/jacoco-ut.exec -Djdk.attach.allowAttachSelf=true -jar /home/jenkins/workspace/narayana/PROFILE/JACOCO/jdk/jdk8.latest/label/linux/ArjunaJTS/jtax/target/surefire/surefirebooter4780163676044108109.jar /home/jenkins/workspace/narayana/PROFILE/JACOCO/jdk/jdk8.latest/label/linux/ArjunaJTS/jtax/target/surefire 2019-11-13T22-51-07_912-jvmRun1 surefire3039402205093478853tmp surefire_6686281639749406541782tmp
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 137
[ERROR] Crashed tests:
[ERROR] com.hp.mwtests.ts.jta.jts.subordinate.SubordinateTestCase
[ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494)
[ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441)
[ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:292)
[ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:243)
[ERROR] at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1077)
[ERROR] at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:907)
[ERROR] at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:785)
[ERROR] at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
[ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
[ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
[ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
[ERROR] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
[ERROR] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
[ERROR] at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
[ERROR] at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
[ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
[ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
[ERROR] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
[ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)
[ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
[ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:192)
[ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[ERROR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[ERROR] at java.lang.reflect.Method.invoke(Method.java:498)
[ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
[ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
[ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
[ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
[ERROR] Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ERROR] Command was /bin/sh -c cd /home/jenkins/workspace/narayana/PROFILE/JACOCO/jdk/jdk8.latest/label/linux/ArjunaJTS/jtax/target/test-classes && /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.181-3.b13.el7_5.x86_64/jre/bin/java -javaagent:/home/jenkins/.m2/repository/org/jacoco/org.jacoco.agent/0.8.3/org.jacoco.agent-0.8.3-runtime.jar=destfile=/home/jenkins/workspace/narayana/PROFILE/JACOCO/jdk/jdk8.latest/label/linux/ArjunaJTS/jtax/target/coverage-reports/jacoco-ut.exec -Djdk.attach.allowAttachSelf=true -jar /home/jenkins/workspace/narayana/PROFILE/JACOCO/jdk/jdk8.latest/label/linux/ArjunaJTS/jtax/target/surefire/surefirebooter4780163676044108109.jar /home/jenkins/workspace/narayana/PROFILE/JACOCO/jdk/jdk8.latest/label/linux/ArjunaJTS/jtax/target/surefire 2019-11-13T22-51-07_912-jvmRun1 surefire3039402205093478853tmp surefire_6686281639749406541782tmp
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 137
[ERROR] Crashed tests:
[ERROR] com.hp.mwtests.ts.jta.jts.subordinate.SubordinateTestCase
[ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:679)
[ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:533)
[ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.access$600(ForkStarter.java:117)
[ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter$2.call(ForkStarter.java:429)
[ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter$2.call(ForkStarter.java:406)
[ERROR] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[ERROR] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[ERROR] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[ERROR] at java.lang.Thread.run(Thread.java:748)
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :jtax
{code}
messaging-actitvemq
{code}
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on project wildfly-messaging-activemq: There are test failures.
[ERROR]
[ERROR] Please refer to /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/messaging-activemq/target/surefire-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ERROR] Command was /bin/sh -c cd /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/messaging-activemq && /home/jenkins/jdk-11/bin/java --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED --add-modules=java.se -ea -Duser.region=US -Duser.language=en -XX:MaxMetaspaceSize=256m -jar /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/messaging-activemq/target/surefire/surefirebooter7374613155138347717.jar /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/messaging-activemq/target/surefire 2019-11-13T22-06-58_276-jvmRun1 surefire8024652247313178174tmp surefire_519929637302128098477tmp
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 1
[ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ERROR] Command was /bin/sh -c cd /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/messaging-activemq && /home/jenkins/jdk-11/bin/java --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED --add-modules=java.se -ea -Duser.region=US -Duser.language=en -XX:MaxMetaspaceSize=256m -jar /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/messaging-activemq/target/surefire/surefirebooter7374613155138347717.jar /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/messaging-activemq/target/surefire 2019-11-13T22-06-58_276-jvmRun1 surefire8024652247313178174tmp surefire_519929637302128098477tmp
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 1
[ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:671)
[ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:533)
[ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:278)
[ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:244)
[ERROR] at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1194)
[ERROR] at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1022)
[ERROR] at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:868)
[ERROR] at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
[ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
[ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
[ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
[ERROR] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
[ERROR] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
[ERROR] at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
[ERROR] at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
[ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
[ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
[ERROR] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
[ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
[ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
[ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
[ERROR] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ERROR] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[ERROR] at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[ERROR] at java.base/java.lang.reflect.Method.invoke(Method.java:566)
[ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
[ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
[ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
[ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
[ERROR] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ERROR] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[ERROR] at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[ERROR] at java.base/java.lang.reflect.Method.invoke(Method.java:566)
[ERROR] at org.apache.maven.wrapper.BootstrapMainStarter.start(BootstrapMainStarter.java:39)
[ERROR] at org.apache.maven.wrapper.WrapperExecutor.execute(WrapperExecutor.java:122)
[ERROR] at org.apache.maven.wrapper.MavenWrapperMain.main(MavenWrapperMain.java:50)
[ERROR] -> [Help 1]
[ERROR] Failed to execute goal org.jboss.galleon:galleon-maven-plugin:4.1.1.Final:provision (server-provisioning) on project wildfly-servlet-build: Provisioning failed: Failed to resolve org.wildfly.core:wildfly-cli:jar:client:11.0.0.Beta2: Could not find artifact org.wildfly.core:wildfly-cli:jar:client:11.0.0.Beta2 -> [Help 1]
[ERROR] Failed to execute goal org.jboss.galleon:galleon-maven-plugin:4.1.1.Final:provision (server-provisioning) on project wildfly-servlet-dist: Provisioning failed: Failed to resolve org.wildfly.core:wildfly-cli:jar:client:11.0.0.Beta2: Could not find artifact org.wildfly.core:wildfly-cli:jar:client:11.0.0.Beta2 -> [Help 1]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (ws-integration-default.surefire) on project wildfly-ts-integ-ws: There are test failures.
[ERROR]
[ERROR] Please refer to /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/ws/target/surefire-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] -> [Help 2]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on project wildfly-ts-integ-web: There are test failures.
[ERROR]
[ERROR] Please refer to /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/web/target/surefire-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] -> [Help 2]
[ERROR] Failed to execute goal org.jboss.galleon:galleon-maven-plugin:4.1.1.Final:provision (server-provisioning) on project wildfly-ts-integ-smoke: Provisioning failed: Failed to resolve org.wildfly:wildfly-galleon-pack:zip:19.0.0.Beta1-SNAPSHOT: Could not find artifact org.wildfly:wildfly-galleon-pack:zip:19.0.0.Beta1-SNAPSHOT -> [Help 1]
[ERROR] Failed to execute goal org.jboss.galleon:galleon-maven-plugin:4.1.1.Final:provision (fault-tolerance-provisioning) on project wildfly-ts-integ-microprofile: Provisioning failed: Failed to resolve org.wildfly:wildfly-galleon-pack:zip:19.0.0.Beta1-SNAPSHOT: Could not find artifact org.wildfly:wildfly-galleon-pack:zip:19.0.0.Beta1-SNAPSHOT -> [Help 1]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on project wildfly-ts-integ-mp-config: There are test failures.
[ERROR]
[ERROR] Please refer to /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/microprofile-tck/config/target/surefire-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] -> [Help 2]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on project wildfly-ts-integ-mp-health: There are test failures.
[ERROR]
[ERROR] Please refer to /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/microprofile-tck/health/target/surefire-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] -> [Help 2]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on project wildfly-ts-integ-mp-metrics: There are test failures.
[ERROR]
[ERROR] Please refer to /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/microprofile-tck/metrics/target/surefire-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] -> [Help 2]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on project wildfly-ts-integ-mp-opentracing: There are test failures.
[ERROR]
[ERROR] Please refer to /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/microprofile-tck/opentracing/target/surefire-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] -> [Help 2]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (all-standalone) on project wildfly-ts-integ-vdx: There are test failures.
[ERROR]
[ERROR] Please refer to /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/vdx/target/surefire-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] -> [Help 2]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run (build-iiop.server) on project wildfly-ts-integ-iiop: An Ant BuildException has occured: The following error occurred while executing this line:
[ERROR] /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/src/test/scripts/iiop-build.xml:15: The following error occurred while executing this line:
[ERROR] /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/src/test/scripts/common-targets.xml:177: no resources specified
[ERROR] around Ant part ...<ant antfile="/home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/iiop/../src/test/scripts/iiop-build.xml">... @ 4:168 in /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/iiop/target/antrun/build-main.xml
[ERROR] -> [Help 1]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run (default) on project wildfly-ts-integ-xts: An Ant BuildException has occured: The following error occurred while executing this line:
[ERROR] /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/src/test/scripts/xts-build.xml:17: The following error occurred while executing this line:
[ERROR] /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/src/test/scripts/common-targets.xml:132: no resources specified
[ERROR] around Ant part ...<ant antfile="/home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/xts/../src/test/scripts/xts-build.xml">... @ 4:166 in /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/xts/target/antrun/build-main.xml
[ERROR] -> [Help 1]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on project wildfly-ts-integ-rts: There are test failures.
[ERROR]
[ERROR] Please refer to /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/rts/target/surefire-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] -> [Help 2]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (access-integration-default-full.surefire) on project wildfly-ts-integ-rbac: There are test failures.
[ERROR]
[ERROR] Please refer to /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/rbac/target/surefire-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] -> [Help 2]
[ERROR] Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.2.1.Final:execute-commands (ts.config-as.configure-lb) on project wildfly-ts-integ-clustering: Invalid JBoss Home directory is not valid: /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/clustering/target/wildfly -> [Help 2]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run (default) on project wildfly-ts-integ-multinode: An Ant BuildException has occured: The following error occurred while executing this line:
[ERROR] /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/src/test/scripts/multinode-build.xml:36: The following error occurred while executing this line:
[ERROR] /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/src/test/scripts/common-targets.xml:222: no resources specified
[ERROR] around Ant part ...<ant antfile="/home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/multinode/../src/test/scripts/multinode-build.xml">... @ 4:178 in /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/multinode/target/antrun/build-main.xml
[ERROR] -> [Help 1]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run (build-manual-mode-servers) on project wildfly-ts-integ-manualmode: An Ant BuildException has occured: The following error occurred while executing this line:
[ERROR] /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/src/test/scripts/manualmode-build.xml:33: The following error occurred while executing this line:
[ERROR] /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/src/test/scripts/common-targets.xml:501: The following error occurred while executing this line:
[ERROR] /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/src/test/scripts/common-targets.xml:523: no resources specified
[ERROR] around Ant part ...<ant antfile="/home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/manualmode/../src/test/scripts/manualmode-build.xml">... @ 4:180 in /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/manualmode/target/antrun/build-main.xml
[ERROR] -> [Help 1]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on project wildfly-ts-integ-picketlink: There are test failures.
[ERROR]
[ERROR] Please refer to /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/picketlink/target/surefire-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] -> [Help 2]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on project wildfly-ts-integ-secman: There are test failures.
[ERROR]
[ERROR] Please refer to /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/secman/target/surefire-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] -> [Help 2]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on project wildfly-ts-integ-legacy: There are test failures.
[ERROR]
[ERROR] Please refer to /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/legacy/target/surefire-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] -> [Help 2]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on project wildfly-ts-integ-legacy-ejb-client: There are test failures.
[ERROR]
[ERROR] Please refer to /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/integration/legacy-ejb-client/target/surefire-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] -> [Help 2]
[ERROR] Failed to execute goal org.jboss.galleon:galleon-maven-plugin:4.1.1.Final:provision (server-provisioning) on project wildfly-ts-integ-elytron: Provisioning failed: Failed to resolve org.wildfly:wildfly-galleon-pack:zip:19.0.0.Beta1-SNAPSHOT: Could not find artifact org.wildfly:wildfly-galleon-pack:zip:19.0.0.Beta1-SNAPSHOT -> [Help 1]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on project wildfly-testsuite-compat: There are test failures.
[ERROR]
[ERROR] Please refer to /home/jenkins/workspace/narayana/PROFILE/AS_TESTS/jdk/jdk11.latest/label/linux/jboss-as/testsuite/compat/target/surefire-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] -> [Help 2]
[ERROR] Failed to execute goal org.jboss.galleon:galleon-maven-plugin:4.1.1.Final:provision (cloud-server-provisioning-test) on project wildfly-ts-layers: Provisioning failed: Failed to resolve org.wildfly:wildfly-galleon-pack:zip:19.0.0.Beta1-SNAPSHOT: Could not find artifact org.wildfly:wildfly-galleon-pack:zip:19.0.0.Beta1-SNAPSHOT -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :wildfly-messaging-activemq
{code}
> Reduce memory limit for docker containers in CI
> -----------------------------------------------
>
> Key: JBTM-3256
> URL: https://issues.redhat.com/browse/JBTM-3256
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: CI
> Reporter: Thomas Jenkinson
> Assignee: Thomas Jenkinson
> Priority: Major
> Attachments: jtax.zip, messaging-activemq.zip
>
>
> Some failures might be the OOM killer or some other memory related cause (looking at the dumpstreams).
> We want parallelism but don't want too many failures so reducing the number of agents is not ideal.
> Memory limit (configure/ "Cloud" "Container settings") was set to 8000 mb, set it to 4000 mb
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 10 months
- 1
- 0
[JBoss JIRA] (JBTM-3256) Reduce memory limit for docker containers in CI
by Thomas Jenkinson (Jira)
[ https://issues.redhat.com/browse/JBTM-3256?page=com.atlassian.jira.plugin... ]
Thomas Jenkinson updated JBTM-3256:
-----------------------------------
Description:
Some failures might be the OOM killer or some other memory related cause (looking at the dumpstreams).
We want parallelism but don't want too many failures so reducing the number of agents is not ideal.
Memory limit (configure/ "Cloud" "Container settings") was set to 8000 mb, set it to 4000 mb
was:Currently set to 8000 mb, will try setting it to 4000 mb
> Reduce memory limit for docker containers in CI
> -----------------------------------------------
>
> Key: JBTM-3256
> URL: https://issues.redhat.com/browse/JBTM-3256
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: CI
> Reporter: Thomas Jenkinson
> Assignee: Thomas Jenkinson
> Priority: Major
> Attachments: jtax.zip, messaging-activemq.zip
>
>
> Some failures might be the OOM killer or some other memory related cause (looking at the dumpstreams).
> We want parallelism but don't want too many failures so reducing the number of agents is not ideal.
> Memory limit (configure/ "Cloud" "Container settings") was set to 8000 mb, set it to 4000 mb
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 10 months
- 1
- 0
[JBoss JIRA] (JBTM-3256) Reduce memory limit for docker containers in CI
by Thomas Jenkinson (Jira)
[ https://issues.redhat.com/browse/JBTM-3256?page=com.atlassian.jira.plugin... ]
Thomas Jenkinson updated JBTM-3256:
-----------------------------------
Attachment: jtax.zip
messaging-activemq.zip
> Reduce memory limit for docker containers in CI
> -----------------------------------------------
>
> Key: JBTM-3256
> URL: https://issues.redhat.com/browse/JBTM-3256
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: CI
> Reporter: Thomas Jenkinson
> Assignee: Thomas Jenkinson
> Priority: Major
> Attachments: jtax.zip, messaging-activemq.zip
>
>
> Some failures might be the OOM killer or some other memory related cause (looking at the dumpstreams).
> We want parallelism but don't want too many failures so reducing the number of agents is not ideal.
> Memory limit (configure/ "Cloud" "Container settings") was set to 8000 mb, set it to 4000 mb
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 10 months
- 1
- 0