You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2015/03/10 16:30:38 UTC

[jira] [Updated] (OAK-2086) tarmk-failover: test failures in MBeanTest.testClientAndServerEmptyConfig

     [ https://issues.apache.org/jira/browse/OAK-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

angela updated OAK-2086:
------------------------
    Component/s: oak-tarmk-standby

> tarmk-failover: test failures in MBeanTest.testClientAndServerEmptyConfig
> -------------------------------------------------------------------------
>
>                 Key: OAK-2086
>                 URL: https://issues.apache.org/jira/browse/OAK-2086
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: oak-tarmk-standby
>            Reporter: Julian Reschke
>
> On a Win7 corei7 desktop machines, this test frequently fails; either:
> Failed tests:   testClientAndServerEmptyConfig(org.apache.jackrabbit.oak.plugins        .segment.failover.MBeanTest): expected:<2> but was:<1>
> or because later on, restarting the slave doesn't work (failure when checking the status). In that case I also see:
>             assertEquals(true, jmxServer.getAttribute(clientStatus, "Running"));
> and a
> java.net.ConnectException: Connection refused: no further information: /127.0.0.1:52808
> 	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) ~[na:1.7.0_40]
> 	at sun.nio.ch.SocketChannelImpl.finishConnect(Unknown Source) ~[na:1.7.0_40]
> 	at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:208) ~[netty-transport-4.0.23.Final.jar:4.0.23.Final]
> 	at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:287) ~[netty-transport-4.0.23.Final.jar:4.0.23.Final]
> 	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:528) ~[netty-transport-4.0.23.Final.jar:4.0.23.Final]
> 	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468) ~[netty-transport-4.0.23.Final.jar:4.0.23.Final]
> 	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382) ~[netty-transport-4.0.23.Final.jar:4.0.23.Final]
> 	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354) ~[netty-transport-4.0.23.Final.jar:4.0.23.Final]
> 	at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116) ~[netty-common-4.0.23.Final.jar:4.0.23.Final]
> 	at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137) ~[netty-common-4.0.23.Final.jar:4.0.23.Final]
> 	at java.lang.Thread.run(Unknown Source) ~[na:1.7.0_40]
> apparently thrown in FailoverClient:
>         try {
>             // Start the client.
>             running = true;
>             state = STATUS_RUNNING;
>             ChannelFuture f = b.connect(host, port).sync();
>             // Wait until the connection is closed.
>             f.channel().closeFuture().sync();
>         } catch (Exception e) {
>             log.error("Failed synchronizing state.", e);
>             stop();
>         }



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)