November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9588) Investigate on splitting as transaction module to not be gathering all dependencies

by Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/WFLY-9588?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka commented on WFLY-9588: --------------------------------------- [~yersan] I consider the both should be removed. I think the `org.jboss.threads` for sure. There are not used anywhere what I can say. For the `org.jboss.ws.common` I think it could be removed as well. It's not used in the module directly and if I verified correctly it's not used in the Narayana either. > Investigate on splitting as transaction module to not be gathering all dependencies > ----------------------------------------------------------------------------------- > > Key: WFLY-9588 > URL: https://issues.jboss.org/browse/WFLY-9588 > Project: WildFly > Issue Type: Task > Components: Transactions > Affects Versions: 11.0.0.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Major > Attachments: eap71-txn-dependencies.jpg > > > Current org.jboss.as.transaction module is heavy lifting and has many dependencies and lot of work competencies. E.g. org.jboss.jts module depends on that too. > It should be investigated how to disentangle all the dependencies. > Plus this could be beneficiary for WildFly Swarm if we are able to split the dependency chains, maybe not using one big jar in the transaction module but provide more granularity. Needs to be investigated. > See attached image for a view of dependencies. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11340) Tests in org.jboss.as.test.integration.microprofile.opentracing failing with security manager

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFLY-11340?page=com.atlassian.jira.plugin... ] Martin Choma updated WFLY-11340: -------------------------------- Steps to Reproduce: cd wildfly/testsuite/integration/basic mvn clean test -Dtest=ResourceNotTracedTestCase -Dsecurity.manager > Tests in org.jboss.as.test.integration.microprofile.opentracing failing with security manager > --------------------------------------------------------------------------------------------- > > Key: WFLY-11340 > URL: https://issues.jboss.org/browse/WFLY-11340 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 14.0.0.Final > Reporter: Martin Choma > Priority: Major > > These tests fail with security manager from package org.jboss.as.test.integration.microprofile.opentracing > * ResourceNotTracedTestCase.notTracedEndpointYieldsNoSpans > * ResourceTracedTestCase.tracedEndpointYieldsSpan > * ResourceWithCDITestCase.tracedEndpointYieldsSpan > * ResourceWithCustomOperationNameBeanTestCase.customOperationName > * SimpleRestClientTestCase.clientRequestSpanJoinsServer > {noformat} > java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.lang.RuntimePermission" "modifyThread")" in code source "(vfs:/content/3f3aff01-8e62-42e9-81c0-022f693ec7e0.war/WEB-INF/classes <no signer certificates>)" of "ModuleClassLoader for Module "deployment.3f3aff01-8e62-42e9-81c0-022f693ec7e0.war" from Service Module Loader") > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:294) > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:191) > at java.util.concurrent.ThreadPoolExecutor.checkShutdownAccess(ThreadPoolExecutor.java:742) > at java.util.concurrent.ThreadPoolExecutor.shutdownNow(ThreadPoolExecutor.java:1429) > at java.util.concurrent.Executors$DelegatedExecutorService.shutdownNow(Executors.java:670) > at org.jboss.as.test.integration.common.HttpRequest.execute(HttpRequest.java:63) > at org.jboss.as.test.integration.common.HttpRequest.get(HttpRequest.java:82) > at org.jboss.as.test.integration.microprofile.opentracing.ResourceNotTracedTestCase.performCall(ResourceNotTracedTestCase.java:63) > at org.jboss.as.test.integration.microprofile.opentracing.ResourceNotTracedTestCase.notTracedEndpointYieldsNoSpans(ResourceNotTracedTestCase.java:57) > {noformat} > As stacktrace is from test side and tests are missing @RunAsClient, I believe tests are running in container. [~juraci.costa] is this really intent tests are missing @RunAsClient annotation? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11341) Upgrade WildFly Core 7.0.0.Beta1

by Jeff Mesnil (Jira)

Jeff Mesnil created WFLY-11341: ---------------------------------- Summary: Upgrade WildFly Core 7.0.0.Beta1 Key: WFLY-11341 URL: https://issues.jboss.org/browse/WFLY-11341 Project: WildFly Issue Type: Component Upgrade Components: Management Reporter: Jeff Mesnil Assignee: Jeff Mesnil -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-499) Configure automation jobs to start using clusters from pool

by Filip Brychta (Jira)

Filip Brychta created SWSQE-499: ----------------------------------- Summary: Configure automation jobs to start using clusters from pool Key: SWSQE-499 URL: https://issues.jboss.org/browse/SWSQE-499 Project: Kiali QE Issue Type: Sub-task Reporter: Filip Brychta Assignee: Filip Brychta We can use https://jenkins.io/doc/pipeline/steps/lockable-resources/ plugin to define cluster of OS clusters and then configure jobs to pick and lock free one. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-498) Create new cluster/s from free baremetal hosts

by Filip Brychta (Jira)

Filip Brychta created SWSQE-498: ----------------------------------- Summary: Create new cluster/s from free baremetal hosts Key: SWSQE-498 URL: https://issues.jboss.org/browse/SWSQE-498 Project: Kiali QE Issue Type: Sub-task Reporter: Filip Brychta Assignee: Filip Brychta -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11340) Tests in org.jboss.as.test.integration.microprofile.opentracing failing with security manager

by Martin Choma (Jira)

Martin Choma created WFLY-11340: ----------------------------------- Summary: Tests in org.jboss.as.test.integration.microprofile.opentracing failing with security manager Key: WFLY-11340 URL: https://issues.jboss.org/browse/WFLY-11340 Project: WildFly Issue Type: Bug Components: Test Suite Affects Versions: 14.0.0.Final Reporter: Martin Choma These tests fail with security manager from package org.jboss.as.test.integration.microprofile.opentracing * ResourceNotTracedTestCase.notTracedEndpointYieldsNoSpans * ResourceTracedTestCase.tracedEndpointYieldsSpan * ResourceWithCDITestCase.tracedEndpointYieldsSpan * ResourceWithCustomOperationNameBeanTestCase.customOperationName * SimpleRestClientTestCase.clientRequestSpanJoinsServer {noformat} java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.lang.RuntimePermission" "modifyThread")" in code source "(vfs:/content/3f3aff01-8e62-42e9-81c0-022f693ec7e0.war/WEB-INF/classes <no signer certificates>)" of "ModuleClassLoader for Module "deployment.3f3aff01-8e62-42e9-81c0-022f693ec7e0.war" from Service Module Loader") at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:294) at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:191) at java.util.concurrent.ThreadPoolExecutor.checkShutdownAccess(ThreadPoolExecutor.java:742) at java.util.concurrent.ThreadPoolExecutor.shutdownNow(ThreadPoolExecutor.java:1429) at java.util.concurrent.Executors$DelegatedExecutorService.shutdownNow(Executors.java:670) at org.jboss.as.test.integration.common.HttpRequest.execute(HttpRequest.java:63) at org.jboss.as.test.integration.common.HttpRequest.get(HttpRequest.java:82) at org.jboss.as.test.integration.microprofile.opentracing.ResourceNotTracedTestCase.performCall(ResourceNotTracedTestCase.java:63) at org.jboss.as.test.integration.microprofile.opentracing.ResourceNotTracedTestCase.notTracedEndpointYieldsNoSpans(ResourceNotTracedTestCase.java:57) {noformat} As stacktrace is from test side and tests are missing @RunAsClient, I believe tests are running in container. [~juraci.costa] is this really intent tests are missing @RunAsClient annotation? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-497) Remove one node from each clusters if possible

by Filip Brychta (Jira)

Filip Brychta created SWSQE-497: ----------------------------------- Summary: Remove one node from each clusters if possible Key: SWSQE-497 URL: https://issues.jboss.org/browse/SWSQE-497 Project: Kiali QE Issue Type: Sub-task Reporter: Filip Brychta Assignee: Filip Brychta -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-496) Check if it's possible to use clusters with just master + one node for automation runs

by Filip Brychta (Jira)

Filip Brychta created SWSQE-496: ----------------------------------- Summary: Check if it's possible to use clusters with just master + one node for automation runs Key: SWSQE-496 URL: https://issues.jboss.org/browse/SWSQE-496 Project: Kiali QE Issue Type: Sub-task Reporter: Filip Brychta Assignee: Filip Brychta Currently we have clusters with 1 master and 2 nodes for automation runs. Is it possible to use only master with one node? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-495) Configure automation runs to pick free cluster from a pool

by Filip Brychta (Jira)

Filip Brychta created SWSQE-495: ----------------------------------- Summary: Configure automation runs to pick free cluster from a pool Key: SWSQE-495 URL: https://issues.jboss.org/browse/SWSQE-495 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta To utilize our baremetal hosts properly, it would be good to have pool of OpenShift clusters ready for automation jobs. Jobs could then run concurrently and pick free cluster from the pool. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2911) Update Scenario Simulation command to use the new module

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-2911?page=com.atlassian.jira.plugi... ] Gabriele Cardosi updated DROOLS-2911: ------------------------------------- Description: Use new kie-wb-common-command-api for Scenario Simulation commands *Specs:* Preliminary steps: * Add dependency to the new module containing AbstractCommand * Split CommandExecutor class into two classes: a pure executor and a general event handler that accepts all the events * Refactor ScenarioGridMode.bindContent and ScenarioSimulationViewImpl.refreshContent to be able to refresh internal model and grid model in a simple way (for now it refreshes only the errors from the internal model) * Refactor remaining actions with no commands (for instance flush of inline editing should fire an event instead of update directly the code). More or less all the methods that work with ScenarioGridModel should be inside a command Move to common API: * Implement ScenarioCommandManager extending org.kie.workbench.common.command.impl.CommandManagerImpl * Refactor all commands to extend org.kie.workbench.common.command.AbstractCommand * Implement a default undo strategy that dump the model and restore it when needed (we should consider how to *preserve selections, columns width and right panel status*) * Implement ScenarioCommandRegistry extending org.kie.workbench.common.command.registry.command.CommandRegistryImpl * Implement ScenarioCommandController (or with a better name :) ) that wrap ScenarioCommandRegistry and ScenarioCommandManager and exposes some API for safe command execute (for instance undo only of the last executed method). This class should be the entry point to manage commands (probably it should be declared as @Dependent and injected into the Presenter) was: Use new kie-wb-common-command-api for Scenario Simulation commands *Specs:* Preliminary steps: * Split CommandExecutor class into two classes: a pure executor and a general event handler that accepts all the events * Refactor ScenarioGridMode.bindContent and ScenarioSimulationViewImpl.refreshContent to be able to refresh internal model and grid model in a simple way (for now it refreshes only the errors from the internal model) * Refactor remaining actions with no commands (for instance flush of inline editing should fire an event instead of update directly the code). More or less all the methods that work with ScenarioGridModel should be inside a command Move to common API: * Implement ScenarioCommandManager extending org.kie.workbench.common.command.impl.CommandManagerImpl * Refactor all commands to extend org.kie.workbench.common.command.AbstractCommand * Implement a default undo strategy that dump the model and restore it when needed (we should consider how to *preserve selections, columns width and right panel status*) * Implement ScenarioCommandRegistry extending org.kie.workbench.common.command.registry.command.CommandRegistryImpl * Implement ScenarioCommandController (or with a better name :) ) that wrap ScenarioCommandRegistry and ScenarioCommandManager and exposes some API for safe command execute (for instance undo only of the last executed method). This class should be the entry point to manage commands (probably it should be declared as @Dependent and injected into the Presenter) > Update Scenario Simulation command to use the new module > -------------------------------------------------------- > > Key: DROOLS-2911 > URL: https://issues.jboss.org/browse/DROOLS-2911 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Major > > Use new kie-wb-common-command-api for Scenario Simulation commands > *Specs:* > Preliminary steps: > * Add dependency to the new module containing AbstractCommand > * Split CommandExecutor class into two classes: a pure executor and a general event handler that accepts all the events > * Refactor ScenarioGridMode.bindContent and ScenarioSimulationViewImpl.refreshContent to be able to refresh internal model and grid model in a simple way (for now it refreshes only the errors from the internal model) > * Refactor remaining actions with no commands (for instance flush of inline editing should fire an event instead of update directly the code). More or less all the methods that work with ScenarioGridModel should be inside a command > Move to common API: > * Implement ScenarioCommandManager extending org.kie.workbench.common.command.impl.CommandManagerImpl > * Refactor all commands to extend org.kie.workbench.common.command.AbstractCommand > * Implement a default undo strategy that dump the model and restore it when needed (we should consider how to *preserve selections, columns width and right panel status*) > * Implement ScenarioCommandRegistry extending org.kie.workbench.common.command.registry.command.CommandRegistryImpl > * Implement ScenarioCommandController (or with a better name :) ) that wrap ScenarioCommandRegistry and ScenarioCommandManager and exposes some API for safe command execute (for instance undo only of the last executed method). This class should be the entry point to manage commands (probably it should be declared as @Dependent and injected into the Presenter) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 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 November 2018