December 2017 - jboss-jira - Jboss List Archives

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

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1518?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1518: ----------------------------- Fix Version/s: 9.0.0.Final > 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 > Fix For: 9.0.0.Final > > 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 was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3241) KDC server does not bind to correct address

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3241?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-3241: ----------------------------- Fix Version/s: 9.0.0.Final > KDC server does not bind to correct address > ------------------------------------------- > > Key: WFLY-3241 > URL: https://issues.jboss.org/browse/WFLY-3241 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 8.1.0.CR1 > Reporter: Dominik Pospisil > Assignee: Dominik Pospisil > Fix For: 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1065) Update JBoss Transactions to 5.0.0.M3

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1065?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1065: ----------------------------- Fix Version/s: 9.0.0.Final > Update JBoss Transactions to 5.0.0.M3 > ------------------------------------- > > Key: WFLY-1065 > URL: https://issues.jboss.org/browse/WFLY-1065 > Project: WildFly > Issue Type: Feature Request > Components: Transactions > Affects Versions: 8.0.0.Alpha1 > Reporter: Ivo Studensky > Fix For: 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1750) Low level permissions for the useware kernel

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1750?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1750: ----------------------------- Fix Version/s: 9.0.0.Final > Low level permissions for the useware kernel > --------------------------------------------- > > Key: WFLY-1750 > URL: https://issues.jboss.org/browse/WFLY-1750 > Project: WildFly > Issue Type: Feature Request > Components: Web Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1240) Review Coverity reports for JBossWS integration

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1240?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1240: ----------------------------- Fix Version/s: 9.0.0.Final > Review Coverity reports for JBossWS integration > ----------------------------------------------- > > Key: WFLY-1240 > URL: https://issues.jboss.org/browse/WFLY-1240 > Project: WildFly > Issue Type: Task > Components: Web Services > Reporter: Rostislav Svoboda > Assignee: Jim Ma > Fix For: 9.0.0.Final > > > Please check reported items for WS integration in http://station5.brq.redhat.com:8080/reports.htm#v10037/p10007 - use prepared 'x WS issues' filter -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2156) Upgrade scannotation to 1.0.3

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2156?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-2156: ----------------------------- Fix Version/s: 9.0.0.Final > Upgrade scannotation to 1.0.3 > ----------------------------- > > Key: WFLY-2156 > URL: https://issues.jboss.org/browse/WFLY-2156 > Project: WildFly > Issue Type: Feature Request > Components: REST > Affects Versions: 8.0.0.Alpha4 > Reporter: Weinan Li > Assignee: Weinan Li > Fix For: 9.0.0.Final > > > RESTEasy has a dependency on 1.0.3 of scannotation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1394) Add resteasy-crypto to WildFly

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1394?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1394: ----------------------------- Fix Version/s: 9.0.0.Final > Add resteasy-crypto to WildFly > ------------------------------ > > Key: WFLY-1394 > URL: https://issues.jboss.org/browse/WFLY-1394 > Project: WildFly > Issue Type: Feature Request > Components: REST > Affects Versions: 8.0.0.Alpha1 > Reporter: Weinan Li > Assignee: Stuart Douglas > Priority: Minor > Fix For: 9.0.0.Final > > > Customers want to use resteasy-crypto inside WildFly. We may need to add this module in future releases. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3162) audit syslog handler should be able to automatically reconnect

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3162?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-3162: ----------------------------- Fix Version/s: 9.0.0.Final > audit syslog handler should be able to automatically reconnect > -------------------------------------------------------------- > > Key: WFLY-3162 > URL: https://issues.jboss.org/browse/WFLY-3162 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Tom Fonteyne > Assignee: Kabir Khan > Labels: EAP > Fix For: 9.0.0.Final > > > When the syslog server goes down, WF will retry (up to 10 times we believe) to reconnect but will then give up. You can manually force a reconnect by issuing: > /host=master/core-service=management/access=audit/syslog-handler=mysyslog:recycle > This request is to make it possible to automate this and make it configurable at which interval it should try and reconnect -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1671) org.apache.commons.configuration missing dependency on org.apache.commons.beanutils

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1671?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1671: ----------------------------- Fix Version/s: 9.0.0.Final > org.apache.commons.configuration missing dependency on org.apache.commons.beanutils > ----------------------------------------------------------------------------------- > > Key: WFLY-1671 > URL: https://issues.jboss.org/browse/WFLY-1671 > Project: WildFly > Issue Type: Bug > Components: Build System > Affects Versions: 8.0.0.Alpha2 > Reporter: James Livingston > Assignee: Paul Gier > Fix For: 9.0.0.Final > > > Apache commons configuration uses commons bean-utils in a few places, but the module.xml does not declare a dependency on it. > The POM (http://search.maven.org/#artifactdetails|commons-configuration|commons-co...) also suggests that digesters is also a dependency, but I haven't seen any issues from that being missing. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4201) Outdated Quickstarts Openshift instructions

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4201?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4201: ----------------------------- Fix Version/s: 9.0.0.Final > Outdated Quickstarts Openshift instructions > -------------------------------------------- > > Key: WFLY-4201 > URL: https://issues.jboss.org/browse/WFLY-4201 > Project: WildFly > Issue Type: Enhancement > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Fix For: 9.0.0.Final > > > Quickstarts which may be deployed at Openshift have related documentation outdated. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2017