[
https://issues.apache.org/jira/browse/GEODE-4934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417605#comment-16417605
]
Kenneth Howe edited comment on GEODE-4934 at 3/28/18 4:00 PM:
--------------------------------------------------------------
AcceptanceTest run #10 has a failure that's a little different but results in
the same error stack trace as shown in the description.
{code}
org.apache.geode.management.internal.cli.commands.DestroyIndexIfExistsTest >
destroyIndexIfExists FAILED
org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.test.junit.rules.gfsh.GfshScript.awaitIfNecessary(GfshScript.java:116)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:98)
at
org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:105)
at
org.apache.geode.management.internal.cli.commands.DestroyIndexIfExistsTest.destroyIndexIfExists(DestroyIndexIfExistsTest.java:45)
{code}
Underlying cause of all these failures is a BindException on a port while
starting either locators or servers.
{code}
[error 2018/03/27 23:46:10.810 UTC locator <locator request thread[1]>
tid=0x2b] Jmx manager could not be started because HTTP service failed to start
org.apache.geode.management.ManagementException: HTTP service failed to start
at
org.apache.geode.management.internal.ManagementAgent.startHttpService(ManagementAgent.java:324)
at
org.apache.geode.management.internal.ManagementAgent.startAgent(ManagementAgent.java:149)
at
org.apache.geode.management.internal.SystemManagementService.startManager(SystemManagementService.java:435)
at
org.apache.geode.management.internal.JmxManagerLocator.findJmxManager(JmxManagerLocator.java:103)
at
org.apache.geode.management.internal.JmxManagerLocator.processRequest(JmxManagerLocator.java:53)
at
org.apache.geode.distributed.internal.InternalLocator$PrimaryHandler.processRequest(InternalLocator.java:1183)
at
org.apache.geode.distributed.internal.tcpserver.TcpServer.processOneConnection(TcpServer.java:486)
at
org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:380)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.net.BindException: Address already in use
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:433)
at sun.nio.ch.Net.bind(Net.java:425)
at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at
org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:334)
at
org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:302)
at
org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
at
org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:238)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.server.Server.doStart(Server.java:397)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at
org.apache.geode.management.internal.JettyHelper.startJetty(JettyHelper.java:155)
at
org.apache.geode.management.internal.ManagementAgent.startHttpService(ManagementAgent.java:296)
... 10 more
{code}
was (Author: khowe):
AcceptanceTest run #10 has a failure that's a little different but results in
the same error stack trace as shown in the description.
{code}
org.apache.geode.management.internal.cli.commands.DestroyIndexIfExistsTest >
destroyIndexIfExists FAILED
org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.test.junit.rules.gfsh.GfshScript.awaitIfNecessary(GfshScript.java:116)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:98)
at
org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:105)
at
org.apache.geode.management.internal.cli.commands.DestroyIndexIfExistsTest.destroyIndexIfExists(DestroyIndexIfExistsTest.java:45)
{code}
Underlying cause of all these failures is a BindException on a port while
starting either locators or servers.
> CI Failure: GfshScript timing out intermittently waiting for execution to
> complete
> ----------------------------------------------------------------------------------
>
> Key: GEODE-4934
> URL: https://issues.apache.org/jira/browse/GEODE-4934
> Project: Geode
> Issue Type: Bug
> Components: gfsh
> Affects Versions: 1.5.0
> Reporter: Kenneth Howe
> Assignee: Kenneth Howe
> Priority: Major
> Labels: CI
>
> GfshScript.awaitIfNecessary native method call to determine if the process
> executing the script is alive hangs. This is not a hard failure, but it can
> be reproduced with frequently running selected tests from command line. This
> following set of tests produces failures when run on a Linux host (tested on
> CentOS 7).
> {code}
> ./gradlew clean geode-lucene:precheckin --parallel -x rat -x javadoc -x
> spotlessCheck{code}
> {code}
> {code:title=Typical failure stack}
> org.apache.geode.management.internal.cli.commands.StopServerAcceptanceTest >
> cannotStopServerByNameWhenNotConnected FAILED
> org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshScript.awaitIfNecessary(GfshScript.java:116)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:98)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:87)
> at
> org.apache.geode.management.internal.cli.commands.StopServerAcceptanceTest.startCluster(StopServerAcceptanceTest.java:35)
> {code}
> All failures show the same stack from {{at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:98)}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
