You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Dan Smith (JIRA)" <ji...@apache.org> on 2018/08/22 23:01:00 UTC
[jira] [Created] (GEODE-5622) SUPERFLAKY:
AlterRuntimeCommandDUnitTest is flaky due to port conflicts
Dan Smith created GEODE-5622:
--------------------------------
Summary: SUPERFLAKY: AlterRuntimeCommandDUnitTest is flaky due to port conflicts
Key: GEODE-5622
URL: https://issues.apache.org/jira/browse/GEODE-5622
Project: Geode
Issue Type: Bug
Components: tests
Reporter: Dan Smith
All of the methods of this test are failing in CI with port conflicts:
{noformat}
org.apache.geode.management.internal.cli.commands.AlterRuntimeCommandDUnitTest: 5 failures (98.333% success rate)
| .alterLogFileSizeLimitNegative_errorCanNotSet(true): 2 failures (99.333% success rate)
| | Failed build 215 at https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/215
| | Failed build 79 at https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/79
| .testAlterUpdatesSharedConfig(false): 1 failures (99.667% success rate)
| | Failed build 232 at https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/232
| .alterMemberWithoutOptions_needsRelevantParameter(true): 1 failures (99.667% success rate)
| | Failed build 110 at https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/110
| .alterArchiveFileSizeLimitWithGroup_updatesSelectedServerConfigs(false): 1 failures (99.667% success rate)
| | Failed build 124 at https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/124
{noformat}
{noformat}
org.apache.geode.management.internal.cli.commands.AlterRuntimeCommandDUnitTest > alterLogFileSizeLimitNegative_errorCanNotSet(true) [0] FAILED java.lang.AssertionError: Suspicious strings were written to the log during this run. Fix the strings or use IgnoredException.addIgnoredException to ignore. ----------------------------------------------------------------------- Found suspect string in log4j
at line 43 [error 2018/08/17 09:26:45.259 UTC <RMI TCP Connection(1)-172.17.0.14> tid=32] Jmx manager could not be started because java.rmi.server.ExportException: Port already in use: 20961; nested exception is: java.net.BindException: Failed to create server socket on null[20,961] org.apache.geode.management.ManagementException: java.rmi.server.ExportException: Port already in use: 20961; nested exception is: java.net.BindException: Failed to create server socket on null[20,961]
at org.apache.geode.management.internal.ManagementAgent.startAgent(ManagementAgent.java:161)
at org.apache.geode.management.internal.SystemManagementService.startManager(SystemManagementService.java:435)
at org.apache.geode.management.internal.beans.ManagementAdapter.handleCacheCreation(ManagementAdapter.java:173)
at org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:118)
at org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2201)
at org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:591)
at org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1218)
at org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:793)
at org.apache.geode.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:779)
at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:177)
at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:224)
at org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:662)
at org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:649)
at org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:311)
at org.apache.geode.distributed.Locator.startLocator(Locator.java:253)
at org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:140)
at org.apache.geode.test.junit.rules.LocatorStarterRule.startLocator(LocatorStarterRule.java:87)
at org.apache.geode.test.junit.rules.LocatorStarterRule.before(LocatorStarterRule.java:68)
at org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startLocatorVM$1c67b668$1(ClusterStartupRule.java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at hydra.MethExecutor.executeObject(MethExecutor.java:244)
at org.apache.geode.test.dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:70)
at sun.reflect.GeneratedMethodAccessor82.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
at sun.rmi.transport.Transport$1.run(Transport.java:200)
at sun.rmi.transport.Transport$1.run(Transport.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:834)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687)
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.rmi.server.ExportException: Port already in use: 20961; nested exception is: java.net.BindException: Failed to create server socket on null[20,961]
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:346)
at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:254)
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:411)
at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:147)
at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:236)
at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:213)
at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:173)
at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:144)
at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:239)
at org.apache.geode.management.internal.ManagementAgent.configureAndStart(ManagementAgent.java:452)
at org.apache.geode.management.internal.ManagementAgent.startAgent(ManagementAgent.java:159)
... 40 more
Caused by: java.net.BindException: Failed to create server socket on null[20,961]
at org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:752)
at org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:709)
at org.apache.geode.management.internal.ManagementAgent$GemFireRMIServerSocketFactory.createServerSocket(ManagementAgent.java:611)
at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:666)
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:335)
... 50 more
Caused by: java.net.BindException: Address already in use (Bind failed)
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
at java.net.ServerSocket.bind(ServerSocket.java:375)
at org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:748)
... 54 more
{noformat}
Kirk and I looked into this. It looks like Brian fixed this rule to not have port conflicts in GEODE-5467, but his fix was lost with the changes in GEODE-5475. So now this test can end up using the same port for JMX and HTTP.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)