March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-31) QE Git Repository for SWS

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-31?page=com.atlassian.jira.plugin.s... ] Matt Mahoney updated SWSQE-31: ------------------------------ Sprint: SWS QE Sprint 2 (was: SWS QE Sprint 1) > QE Git Repository for SWS > -------------------------- > > Key: SWSQE-31 > URL: https://issues.jboss.org/browse/SWSQE-31 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-48) Test Service Mesh's

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-48?page=com.atlassian.jira.plugin.s... ] Matt Mahoney updated SWSQE-48: ------------------------------ Sprint: SWS QE Sprint 2 > Test Service Mesh's > ------------------- > > Key: SWSQE-48 > URL: https://issues.jboss.org/browse/SWSQE-48 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Michael Foley > > "As a SWS UI developer I want to make sure that we can visualize various different network topology meshes in the service graph" > "As a SWS backend developer I want to make sure that we can generate correct JSON from various network topology meshes" > We need to be able to quickly and easily deploy a bunch of different network topography examples in various namespaces in OpenShift/K8S for testing purposes. > There are a bunch of different posible combinations of how things can be arranged and we need to be able to verify that they are render correctly in our UI and that our backend JSON is generating them correctly. > We should be able to easily just generate these different types of setups by deploying a template in a namespace. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-10) Reserve equipment in RH Scale Lab

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-10?page=com.atlassian.jira.plugin.s... ] Matt Mahoney updated SWSQE-10: ------------------------------ Sprint: (was: SWS QE Sprint 2) > Reserve equipment in RH Scale Lab > --------------------------------- > > Key: SWSQE-10 > URL: https://issues.jboss.org/browse/SWSQE-10 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-16) Set Up Confluence Board

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-16?page=com.atlassian.jira.plugin.s... ] Matt Mahoney resolved SWSQE-16. ------------------------------- Resolution: Done > Set Up Confluence Board > ----------------------- > > Key: SWSQE-16 > URL: https://issues.jboss.org/browse/SWSQE-16 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Matt Mahoney > Priority: Minor > > * We could have meeting notes, sprint retrospective notes, we could reference JIRAs (QE and Dev board), create pages for tasks documentation even test plans could be created on Confluence -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-48) Test Service Mesh's

by Matt Mahoney (JIRA)

Matt Mahoney created SWSQE-48: --------------------------------- Summary: Test Service Mesh's Key: SWSQE-48 URL: https://issues.jboss.org/browse/SWSQE-48 Project: Swift Sunshine QE Issue Type: Task Reporter: Matt Mahoney Assignee: Michael Foley "As a SWS UI developer I want to make sure that we can visualize various different network topology meshes in the service graph" "As a SWS backend developer I want to make sure that we can generate correct JSON from various network topology meshes" We need to be able to quickly and easily deploy a bunch of different network topography examples in various namespaces in OpenShift/K8S for testing purposes. There are a bunch of different posible combinations of how things can be arranged and we need to be able to verify that they are render correctly in our UI and that our backend JSON is generating them correctly. We should be able to easily just generate these different types of setups by deploying a template in a namespace. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AG-60) Change default value of autocommit to 'true'

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-60?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro resolved AG-60. ----------------------------- Resolution: Done > Change default value of autocommit to 'true' > -------------------------------------------- > > Key: AG-60 > URL: https://issues.jboss.org/browse/AG-60 > Project: Agroal > Issue Type: Bug > Components: api > Affects Versions: 0.4 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 0.5 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AG-60) Change default value of autocommit to 'true'

by Luis Barreiro (JIRA)

Luis Barreiro created AG-60: ------------------------------- Summary: Change default value of autocommit to 'true' Key: AG-60 URL: https://issues.jboss.org/browse/AG-60 Project: Agroal Issue Type: Bug Components: api Affects Versions: 0.4 Reporter: Luis Barreiro Assignee: Luis Barreiro Fix For: 0.5 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1534) Release WildFly Elytron 1.2.3.Final

by Farah Juma (JIRA)

Farah Juma created ELY-1534: ------------------------------- Summary: Release WildFly Elytron 1.2.3.Final Key: ELY-1534 URL: https://issues.jboss.org/browse/ELY-1534 Project: WildFly Elytron Issue Type: Release Reporter: Farah Juma Assignee: Farah Juma -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9941) :shutdown cli operation throws java.util.concurrent.CancellationException: Operation was cancelled

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9941?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-9941: ---------------------------------------- If you are using the CLI do not use the low level ':shutdown' operation, use the high level 'shutdown' command. It's analogous to "do not use the low level ':reload' operation, use the high level 'reload' command." > :shutdown cli operation throws java.util.concurrent.CancellationException: Operation was cancelled > -------------------------------------------------------------------------------------------------- > > Key: WFLY-9941 > URL: https://issues.jboss.org/browse/WFLY-9941 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 12.0.0.Final > Reporter: Miroslav Novak > Assignee: Jean-Francois Denise > Attachments: manu-trace.log > > > There is intermittent failure on CLI client when CLI operation {{ :shutdown() }} is called. Sometimes happens that CancellationException is thrown: > {code} > 2018-03-01 09:36:59,188 ERROR pool-1-thread-1 org.jboss.manu.eap.services.server.EapModularServerBase - Can't stop server gracefully > java.io.IOException: java.util.concurrent.CancellationException: Operation was cancelled > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149) ~[wildfly-controller-client-2.0.0.CR5.jar:2.0.0.CR5] > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75) ~[wildfly-controller-client-2.0.0.CR5.jar:2.0.0.CR5] > at org.wildfly.extras.creaper.core.online.OnlineManagementClientImpl.execute(OnlineManagementClientImpl.java:180) ~[creaper-core-1.6.1.jar:na] > at org.jboss.manu.eap.services.server.EapModularServerBase.executeOnlineManagementOperation(EapModularServerBase.java:600) ~[manu-eap-lib-1.1.54.jar:na] > at org.jboss.manu.eap.services.server.EapModularServerBase.executeOnlineManagementOperation(EapModularServerBase.java:638) ~[manu-eap-lib-1.1.54.jar:na] > at org.jboss.manu.eap.services.server.EapServerStandalone.executeStopOperation(EapServerStandalone.java:348) ~[manu-eap-lib-1.1.54.jar:na] > at org.jboss.manu.eap.services.server.EapModularServerBase.stop(EapModularServerBase.java:238) ~[manu-eap-lib-1.1.54.jar:na] > at org.jboss.manu.eap.units.server.StopServer.execute(StopServer.java:57) [manu-eap-lib-1.1.54.jar:na] > at org.jboss.manu.core.execute.UnitExecuteTask.call(UnitExecuteTask.java:33) [manu-core-impl-1.1.43.jar:na] > at org.jboss.manu.core.execute.UnitExecuteTask.call(UnitExecuteTask.java:14) [manu-core-impl-1.1.43.jar:na] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_151] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_151] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_151] > at java.lang.Thread.run(Thread.java:748) [na:1.8.0_151] > Caused by: java.util.concurrent.CancellationException: Operation was cancelled > at org.jboss.threads.AsyncFutureTask.operationCancelled(AsyncFutureTask.java:70) ~[jboss-threads-2.2.1.Final.jar:2.2.1.Final] > at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:267) ~[jboss-threads-2.2.1.Final.jar:2.2.1.Final] > at org.jboss.as.controller.client.impl.AbstractDelegatingAsyncFuture.get(AbstractDelegatingAsyncFuture.java:57) ~[wildfly-controller-client-2.0.0.CR5.jar:2.0.0.CR5] > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147) ~[wildfly-controller-client-2.0.0.CR5.jar:2.0.0.CR5] > ... 13 common frames omitted > {code} > WF12 server shutdowns but it seems that it does not send response for {{:shutdown}} call to client before shutdwon and closes connection. This causes that AsyncFutureTask on client is cancelled. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2361) Use of System.identityHashCode in org.drools.core.common.DefaultFactHandle

by Sidi Mohamed EL AATIFI (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2361?page=com.atlassian.jira.plugi... ] Sidi Mohamed EL AATIFI updated DROOLS-2361: ------------------------------------------- Description: This is a JVM https://bugs.openjdk.java.net/browse/JDK-6378256 bug has been fixed in JDK 9 It's not a bug in Drools but will be affected severely if using Drools for serious workloads. in my case 40% of CPU usage was to _ java.lang.System.identityHashCode_ Please consider to propose a workaround if possible > Use of System.identityHashCode in org.drools.core.common.DefaultFactHandle > -------------------------------------------------------------------------- > > Key: DROOLS-2361 > URL: https://issues.jboss.org/browse/DROOLS-2361 > Project: Drools > Issue Type: Enhancement > Components: core engine > Affects Versions: 7.6.0.Final > Reporter: Sidi Mohamed EL AATIFI > Assignee: Mario Fusco > Labels: performance > > This is a JVM https://bugs.openjdk.java.net/browse/JDK-6378256 bug has been fixed in JDK 9 > It's not a bug in Drools but will be affected severely if using Drools for serious workloads. > in my case 40% of CPU usage was to > _ java.lang.System.identityHashCode_ > Please consider to propose a workaround if possible -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2018