geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jared Stewart <jstew...@pivotal.io>
Subject Re: ExportConfigCommandDUnitTest
Date Thu, 05 Oct 2017 00:25:22 GMT
That test uses AvailablePortFinder to choose a random available port.  It’s possible that
you hit a race condition in between the time port was chosen and the time it the server attempted
to bind to it.  

> On Oct 4, 2017, at 5:20 PM, Kirk Lund <klund@apache.org> wrote:
> 
> It passes when I run it in IntelliJ. The cause was:
> 
> Caused by: java.net.BindException: Address already in use
> 
> So, I'm assuming the test tried to use a port that was in use. Is the test
> using a random port or a default port?
> 
> On Wed, Oct 4, 2017 at 5:14 PM, Jared Stewart <jstewart@pivotal.io> wrote:
> 
>> I haven’t seen that test fail before.  If you rerun the precheckin does it
>> still fail?
>> 
>> 
>>> On Oct 4, 2017, at 4:55 PM, Kirk Lund <klund@apache.org> wrote:
>>> 
>>> ExportConfigCommandDUnitTest failed in my latest precheckin but my
>> changes
>>> don't involve the code this test is testing. Did someone commit break
>> this
>>> test or is it failing intermittently?
>>> 
>>> Thanks,
>>> Kirk
>>> 
>>> :geode-web:distributedTest
>>> 
>>> org.apache.geode.management.internal.cli.commands.
>> ExportConfigCommandDUnitTest
>>>> testExportConfig(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 336
>>> 
>>>   [error 2017/10/04 23:34:54.964 UTC <RMI TCP Connection(1)-172.17.0.5>
>>> tid=0x1b] 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:314)
>>>   at
>>> org.apache.geode.management.internal.ManagementAgent.
>> startAgent(ManagementAgent.java:143)
>>>   at
>>> org.apache.geode.management.internal.SystemManagementService.
>> startManager(SystemManagementService.java:427)
>>>   at
>>> org.apache.geode.management.internal.beans.ManagementAdapter.
>> handleCacheCreation(ManagementAdapter.java:173)
>>>   at
>>> org.apache.geode.management.internal.beans.ManagementListener.
>> handleEvent(ManagementListener.java:106)
>>>   at
>>> org.apache.geode.distributed.internal.InternalDistributedSystem.
>> notifyResourceEventListeners(InternalDistributedSystem.java:2198)
>>>   at
>>> org.apache.geode.distributed.internal.InternalDistributedSystem.
>> handleResourceEvent(InternalDistributedSystem.java:585)
>>>   at
>>> org.apache.geode.internal.cache.GemFireCacheImpl.
>> initialize(GemFireCacheImpl.java:1207)
>>>   at
>>> org.apache.geode.internal.cache.GemFireCacheImpl.
>> basicCreate(GemFireCacheImpl.java:768)
>>>   at
>>> org.apache.geode.internal.cache.GemFireCacheImpl.create(
>> GemFireCacheImpl.java:754)
>>>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:175)
>>>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:222)
>>>   at
>>> org.apache.geode.test.junit.rules.ServerStarterRule.
>> startServer(ServerStarterRule.java:147)
>>>   at
>>> org.apache.geode.test.junit.rules.ServerStarterRule.
>> before(ServerStarterRule.java:76)
>>>   at
>>> org.apache.geode.test.dunit.rules.LocatorServerStartupRule.lambda$
>> startServerAsEmbededLocator$207b7110$1(LocatorServerStartupRule.java:230)
>>>   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:245)
>>>   at
>>> org.apache.geode.test.dunit.standalone.RemoteDUnitVM.
>> executeMethodOnObject(RemoteDUnitVM.java:70)
>>>   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 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:568)
>>>   at
>>> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(
>> TCPTransport.java:826)
>>>   at
>>> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$
>> 0(TCPTransport.java:683)
>>>   at java.security.AccessController.doPrivileged(Native Method)
>>>   at
>>> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(
>> TCPTransport.java:682)
>>>   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.open(ServerConnector.java:317)
>>>   at
>>> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(
>> AbstractNetworkConnector.java:80)
>>>   at
>>> org.eclipse.jetty.server.ServerConnector.doStart(
>> ServerConnector.java:235)
>>>   at
>>> org.eclipse.jetty.util.component.AbstractLifeCycle.
>> start(AbstractLifeCycle.java:68)
>>>   at org.eclipse.jetty.server.Server.doStart(Server.java:390)
>>>   at
>>> org.eclipse.jetty.util.component.AbstractLifeCycle.
>> start(AbstractLifeCycle.java:68)
>>>   at
>>> org.apache.geode.management.internal.JettyHelper.
>> startJetty(JettyHelper.java:149)
>>>   at
>>> org.apache.geode.management.internal.ManagementAgent.startHttpService(
>> ManagementAgent.java:286)
>>>   ... 37 more
>>> 
>>>   ------------------------------------------------------------
>> -----------
>>>   Found suspect string in log4j at line 392
>>> 
>>>   [error 2017/10/04 23:34:54.971 UTC <RMI TCP Connection(1)-172.17.0.5>
>>> tid=0x1b] org.apache.geode.management.ManagementException: HTTP service
>>> failed to start
>>> 
>>> org.apache.geode.management.internal.cli.commands.
>> ExportConfigCommandDUnitTest
>>>> testExportConfig(false) [1] FAILED
>>>   org.junit.ComparisonFailure: [Could not read command response. Error
>>> occurred while executing "export config
>>> --dir=/tmp/junit2331171051443593975/all-members" on manager.
>>> 
>>>   ] expected:<[OK]> but was:<[ERROR]>
>>>       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.GfshShellConnectionRule.
>> executeAndVerifyCommand(GfshShellConnectionRule.java:255)
>>>       at
>>> org.apache.geode.management.internal.cli.commands.
>> ExportConfigCommandDUnitTest.testExportConfig(
>> ExportConfigCommandDUnitTest.java:76)
>>> 
>>> 79 tests completed, 2 failed
>>> :geode-web:distributedTest FAILED
>> 
>> 


Mime
View raw message