July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2491) Reduce use of synchronized

by Bela Ban (Jira)

Bela Ban created JGRP-2491: ------------------------------ Summary: Reduce use of synchronized Key: JGRP-2491 URL: https://issues.redhat.com/browse/JGRP-2491 Project: JGroups Issue Type: Enhancement Reporter: Bela Ban Assignee: Bela Ban Fix For: 5.0.0.Final The synchronized keyword fares badly with virtual threads (project Loom). Contrary to {{java.util.concurrent.lock.Lock}}, {{synchronized}} can still block. This might change in the future, but for now, we should replace all uses of {{synchronized}} with {{Lock.lock()/unlock().}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2488) VERIFY_SUSPECT: don't start a new thread for each SUSPECT event

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2488?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2488: --------------------------- Fix Version/s: 4.2.5 > VERIFY_SUSPECT: don't start a new thread for each SUSPECT event > --------------------------------------------------------------- > > Key: JGRP-2488 > URL: https://issues.redhat.com/browse/JGRP-2488 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.2.5, 5.0.0.Final > > > Currently, {{VERIFY_SUSPECT}} starts a new thread to handle every {{SUSPECT}} event. This should be changed, so that - if a thread is already running - reuse it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2478) Fibers: test performance versus regular threads

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2478?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2478. ---------------------------- Resolution: Done http://belaban.blogspot.com/2020/07/double-your-performance-virtual-threa... > Fibers: test performance versus regular threads > ----------------------------------------------- > > Key: JGRP-2478 > URL: https://issues.redhat.com/browse/JGRP-2478 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0.0.Final > > > Test performance on the latest JDK-15-loom with {{use_fibers="true"/"false"}}. > This requires a few code changes: > * There's no need to pool fibers, see [1] for details > * If fibers are used, {{thread_pool}} and {{internal_pool}} in {{TP}} could be assigned the result of {{Executors.newVirtualThreadExecutor()}} > * In a future version, we could simply remove the 2 thread pools > [1] [https://cr.openjdk.java.net/~rpressler/loom/loom/sol1_part1.html] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13675) Make legacy security optional for "org.wildfly.extension.batch.jberet"

by Darran Lofthouse (Jira)

Darran Lofthouse created WFLY-13675: --------------------------------------- Summary: Make legacy security optional for "org.wildfly.extension.batch.jberet" Key: WFLY-13675 URL: https://issues.redhat.com/browse/WFLY-13675 Project: WildFly Issue Type: Sub-task Components: Batch, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 21.0.0.Beta1 The dependency needs to optional so provisioning a layer with batch does not automatically pull in legacy security. This is not just about making the module dependency optional, this is about understanding why it is not optional and identifying the steps required to make it optional. This needs to consider: * Default Configuration * User Defined Configuration Both of these can have different consequences depending on of they are used for: * Resource defined services * DeploymentUnitProcessor processing -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1045) Jenkins master configuration as a code

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1045?page=com.atlassian.jira.plugi... ] Filip Brychta closed SWSQE-1045. -------------------------------- Resolution: Duplicate Issue Will be done in https://issues.redhat.com/browse/SWSQE-616 > Jenkins master configuration as a code > -------------------------------------- > > Key: SWSQE-1045 > URL: https://issues.redhat.com/browse/SWSQE-1045 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > Currently we configured jenkins master manually and we are backing it up. > There is a new internal project to keep jenkins master as a code: > https://docs.engineering.redhat.com/display/CentralCI/CCI+Jenkins+Declara... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-616) Migrate to new Containerized Jenkins CSB

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-616?page=com.atlassian.jira.plugin... ] Filip Brychta updated SWSQE-616: -------------------------------- Summary: Migrate to new Containerized Jenkins CSB (was: Migrate our jenkins slaves to PSI) > Migrate to new Containerized Jenkins CSB > ---------------------------------------- > > Key: SWSQE-616 > URL: https://issues.redhat.com/browse/SWSQE-616 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > Before we do the migration we need to answer following questions: > * do we want to use containers for jenkins slaves in ocp or VMs in openStack? > * currently we need privileged containers (for kiali-build), is it possible to have it in PSI? > * check connectivity (stability/latency) to our testing ocp clusters (in our bos lab and in PSI) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-616) Migrate to new Containerized Jenkins CSB

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-616?page=com.atlassian.jira.plugin... ] Filip Brychta commented on SWSQE-616: ------------------------------------- {color:#333333}I am proud to announce that the Containerized Jenkins CSB[1] provided by{color} {color:#333333}Central CI and Tooling Team is now Generally Available for production{color} {color:#333333}use. It provides a supported environment for running QE workloads on{color} {color:#333333}Jenkins inside PSI OpenShift. The service is here to replace existing{color} {color:#333333}Jenkins deployments running on RHV, which will be phased out by the end{color} {color:#333333}of this calendar year. Please start planning your migration now so that{color} {color:#333333}we can make sure to fill any gaps before then.{color} {color:#333333}Notable changes effective with the GA:{color} {color:#333333}- Whether you are a new user or an early adopter using the service for a{color} {color:#333333}while, please make sure to consult the service support policy[2] and the{color} {color:#333333}migration guide[3].{color} {color:#333333}- Sources for CCI-JD[4], the project interpreting declaration{color} {color:#333333}repositories storing Jenkins config, were moved and merged with the rest{color} {color:#333333}of the Containerized CSB automation. Separate steps are needed to{color} {color:#333333}migrate users’ repositories[5].{color} {color:#333333}- Google chat group “Containerized Jenkins CSB” has been created for{color} {color:#333333}users to ask questions.{color} {color:#333333}- All plugins are now distributed through a single internal update center.{color} {color:#333333}- There is a Service Now application “CCIT Jenkins” for easier and{color} {color:#333333}faster triage of tickets. Make sure to specify that when filing tickets{color} {color:#333333}for Jenkins.{color} {color:#333333}While the details are still in the works, we also anticipate migrating{color} {color:#333333}all Jenkins masters in OpenShift from OCPv3 to OCPv4 later this year.{color} {color:#333333}There are no immediate actions to take by the users for now.{color} {color:#333333}[1]{color} {color:#333333}https://docs.engineering.redhat.com/display/CentralCI/Jenkins+CSB+Containerized{color} {color:#333333}[2]{color} {color:#333333}https://docs.engineering.redhat.com/display/CentralCI/Jenkins+Masters+-+PSI+OpenShift{color} {color:#333333}[3] https://docs.engineering.redhat.com/display/CentralCI/Migration+guide{color} {color:#333333}[4]{color} {color:#333333}https://docs.engineering.redhat.com/pages/viewpage.action?pageId=93540007{color} {color:#333333}[5]{color} {color:#333333}https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/jcasc/blob/master/README.md{color} {color:#333333}Thanks!{color} {color:#333333}--{color} {color:#333333}oliver{color} > Migrate to new Containerized Jenkins CSB > ---------------------------------------- > > Key: SWSQE-616 > URL: https://issues.redhat.com/browse/SWSQE-616 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > Before we do the migration we need to answer following questions: > * do we want to use containers for jenkins slaves in ocp or VMs in openStack? > * currently we need privileged containers (for kiali-build), is it possible to have it in PSI? > * check connectivity (stability/latency) to our testing ocp clusters (in our bos lab and in PSI) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-617) Migrate our test ocp clusters to PSI

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-617?page=com.atlassian.jira.plugin... ] Filip Brychta resolved SWSQE-617. --------------------------------- Resolution: Done Done, we have following jobs to provision OCP clusters in PSI OpenStack: https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/view/infra-jobs/ > Migrate our test ocp clusters to PSI > ------------------------------------ > > Key: SWSQE-617 > URL: https://issues.redhat.com/browse/SWSQE-617 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > We need to answer following questions: > * do we want to do that or stay in our bos lab > * how to provision ocp clusters in PSI (Flexy? Flexy wrapper, LInchpin) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5513) Issue while installing drools engine on wildfly

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5513?page=com.atlassian.jira.plug... ] Mario Fusco commented on DROOLS-5513: ------------------------------------- Can you give us more hints about this? Which version of Wildfly are you using? Can you send us your project to reproduce this problem? > Issue while installing drools engine on wildfly > ----------------------------------------------- > > Key: DROOLS-5513 > URL: https://issues.redhat.com/browse/DROOLS-5513 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.34.0.Final > Reporter: sumita sarkhel > Assignee: Mario Fusco > Priority: Critical > Labels: support > > Hi, > While calling buildAll() function, it throws the below error: > Caused by: java.lang.NoClassDefFoundError: org/codehaus/plexus/interpolation/InterpolationException > at org.apache.maven.settings.building.DefaultSettingsBuilderFactory.newInstance(DefaultSettingsBuilderFactory.java:62) > at org.appformer.maven.integration.embedder.MavenSettings.initSettings(MavenSettings.java:91) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5513) Issue while installing drools engine on wildfly

by sumita sarkhel (Jira)

sumita sarkhel created DROOLS-5513: -------------------------------------- Summary: Issue while installing drools engine on wildfly Key: DROOLS-5513 URL: https://issues.redhat.com/browse/DROOLS-5513 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.34.0.Final Reporter: sumita sarkhel Assignee: Mario Fusco Hi, While calling buildAll() function, it throws the below error: Caused by: java.lang.NoClassDefFoundError: org/codehaus/plexus/interpolation/InterpolationException at org.apache.maven.settings.building.DefaultSettingsBuilderFactory.newInstance(DefaultSettingsBuilderFactory.java:62) at org.appformer.maven.integration.embedder.MavenSettings.initSettings(MavenSettings.java:91) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 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 July 2020