[jboss-jira] [JBoss JIRA] (WFLY-1518) HornetQBackupActivationTestCase runs into intermittent failures

RH Bugzilla Integration (JIRA) jira-events at lists.jboss.org
Mon Jun 17 04:17:21 EDT 2013


    [ https://issues.jboss.org/browse/WFLY-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781984#comment-12781984 ] 

RH Bugzilla Integration commented on WFLY-1518:
-----------------------------------------------

Ivo Studensky <istudens at redhat.com> made a comment on [bug 974942|https://bugzilla.redhat.com/show_bug.cgi?id=974942]

Description of problem:
On EAP 6.1.x HornetQBackupActivationTestCase intermittently fails. This has been fixed in upstream by WFLY-1518 recently. The EAP 6.1.x branch needs the same fix as well.

Version-Release number of selected component (if applicable):
6.1.x
                
> HornetQBackupActivationTestCase runs into intermittent failures
> ---------------------------------------------------------------
>
>                 Key: WFLY-1518
>                 URL: https://issues.jboss.org/browse/WFLY-1518
>             Project: WildFly
>          Issue Type: Bug
>          Components: Test Suite
>    Affects Versions: 8.0.0.Alpha1
>            Reporter: jaikiran pai
>            Assignee: Jeff Mesnil
>         Attachments: log.txt
>
>
> The HornetQBackupActivationTestCase#testPassiveBackupReload() failed on TeamCity environment against latest upstream/master. I haven't yet had a detailed look at it. The exception stacktrace looks like:
> {code}
> Caused by: java.util.concurrent.ExecutionException: Operation failed
>     at org.jboss.threads.AsyncFutureTask.operationFailed(AsyncFutureTask.java:74)
>     at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:268)
>     at org.jboss.as.controller.client.impl.AbstractDelegatingAsyncFuture.get(AbstractDelegatingAsyncFuture.java:100)
>     at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)
>     ... 93 more
> Caused by: java.io.IOException: Channel closed
>     at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleChannelClosed(AbstractMessageHandler.java:381)
>     at org.jboss.as.controller.client.impl.RemotingModelControllerClient$2.handleClose(RemotingModelControllerClient.java:137)
>     at org.jboss.as.controller.client.impl.RemotingModelControllerClient$2.handleClose(RemotingModelControllerClient.java:134)
>     at org.jboss.remoting3.spi.SpiUtils.safeHandleClose(SpiUtils.java:54)
>     at org.jboss.remoting3.spi.AbstractHandleableCloseable$CloseHandlerTask.run(AbstractHandleableCloseable.java:501)
>     at org.jboss.remoting3.spi.AbstractHandleableCloseable.runCloseTask(AbstractHandleableCloseable.java:406)
>     at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeComplete(AbstractHandleableCloseable.java:277)
>     at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:531)
>     at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:359)
>     at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAllChannels(RemoteConnectionHandler.java:399)
>     at org.jboss.remoting3.remote.RemoteConnectionHandler.handleConnectionClose(RemoteConnectionHandler.java:108)
>     at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:78)
>     at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:45)
>     at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:91)
>     at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:195)
>     at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:109)
>     at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:91)
>     at org.xnio.ChannelListeners$DelegatingChannelListener.handleEvent(ChannelListeners.java:1052)
>     at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:91)
>     at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:61)
>     at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:85)
>     at org.xnio.nio.WorkerThread.run(WorkerThread.java:528)
> {code}
> There's also some complaints about connection leaks in those logs:
> {code}
> 13:17:26,866 WARN  [org.jboss.as.controller.client] (Finalizer) JBAS010600: Closing leaked controller client: JBAS010649: Allocation stack trace:
>     at java.lang.Thread.getStackTrace(Thread.java:1567)
>     at org.jboss.as.controller.client.impl.RemotingModelControllerClient.<init>(RemotingModelControllerClient.java:76)
>     at org.jboss.as.controller.client.ModelControllerClient$Factory.create(ModelControllerClient.java:337)
>     at org.jboss.as.controller.client.ModelControllerClient$Factory.create(ModelControllerClient.java:147)
>     at org.jboss.as.test.manualmode.messaging.HornetQBackupActivationTestCase.createBackupClient(HornetQBackupActivationTestCase.java:107)
>     at org.jboss.as.test.manualmode.messaging.HornetQBackupActivationTestCase.waitForBackupServerToReload(HornetQBackupActivationTestCase.java:297)
>     at org.jboss.as.test.manualmode.messaging.HornetQBackupActivationTestCase.testActiveBackupReload(HornetQBackupActivationTestCase.java:224)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> {code}
> The entire log has been attached to the JIRA.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jboss-jira mailing list