July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-787) UI Automations - Add check "is_there" to optimize navigation.

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-787?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan closed SWSQE-787. -------------------------------- Resolution: Done > UI Automations - Add check "is_there" to optimize navigation. > ------------------------------------------------------------- > > Key: SWSQE-787 > URL: https://issues.jboss.org/browse/SWSQE-787 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4556) Upgrade jboss-remoting to 5.0.13.Final

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4556?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-4556: ------------------------------------- Component/s: Remoting > Upgrade jboss-remoting to 5.0.13.Final > -------------------------------------- > > Key: WFCORE-4556 > URL: https://issues.jboss.org/browse/WFCORE-4556 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Remoting > Reporter: Teresa Miyar Gil > Assignee: Flavia Rainone > Priority: Major > Labels: downstream_dependency > > Upgrade jboss-remoting to 5.0.12.Final -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4556) Upgrade jboss-remoting to 5.0.13.Final

by Teresa Miyar Gil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4556?page=com.atlassian.jira.plugi... ] Teresa Miyar Gil updated WFCORE-4556: ------------------------------------- Labels: downstream_dependency (was: ) > Upgrade jboss-remoting to 5.0.13.Final > -------------------------------------- > > Key: WFCORE-4556 > URL: https://issues.jboss.org/browse/WFCORE-4556 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Teresa Miyar Gil > Assignee: Jeff Mesnil > Priority: Major > Labels: downstream_dependency > > Upgrade jboss-remoting to 5.0.12.Final -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4556) Upgrade jboss-remoting to 5.0.13.Final

by Teresa Miyar Gil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4556?page=com.atlassian.jira.plugi... ] Teresa Miyar Gil reassigned WFCORE-4556: ---------------------------------------- Assignee: Flavia Rainone (was: Jeff Mesnil) > Upgrade jboss-remoting to 5.0.13.Final > -------------------------------------- > > Key: WFCORE-4556 > URL: https://issues.jboss.org/browse/WFCORE-4556 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Teresa Miyar Gil > Assignee: Flavia Rainone > Priority: Major > Labels: downstream_dependency > > Upgrade jboss-remoting to 5.0.12.Final -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4557) The read http-upgrade-enabled attribute operation acquires the write lock unnecessarily

by Yeray Borges (Jira)

Yeray Borges created WFCORE-4557: ------------------------------------ Summary: The read http-upgrade-enabled attribute operation acquires the write lock unnecessarily Key: WFCORE-4557 URL: https://issues.jboss.org/browse/WFCORE-4557 Project: WildFly Core Issue Type: Bug Components: Management Reporter: Yeray Borges Assignee: Yeray Borges When we are reading the http-upgrade-enabled, the model is read acquiring the write lock. That could make the operation block until the write lock is released by any other underlying operation that previously has acquired it. The read handler only reads the value and put it in the response, so taking the write lock here is unnecessary. This issue affects the ongoing work in WFCORE-4283, there, we could have servers starting with the write lock taken, so it negatively affects to any reading of this attribute. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4556) Upgrade jboss-remoting to 5.0.13.Final

by Teresa Miyar Gil (Jira)

Teresa Miyar Gil created WFCORE-4556: ---------------------------------------- Summary: Upgrade jboss-remoting to 5.0.13.Final Key: WFCORE-4556 URL: https://issues.jboss.org/browse/WFCORE-4556 Project: WildFly Core Issue Type: Component Upgrade Reporter: Teresa Miyar Gil Assignee: Jeff Mesnil Upgrade jboss-remoting to 5.0.12.Final -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1840) Strong type defined credential store in client schema

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1840: ------------------------------------- Summary: Strong type defined credential store in client schema Key: ELY-1840 URL: https://issues.jboss.org/browse/ELY-1840 Project: WildFly Elytron Issue Type: Feature Request Components: Authentication Client, Credential Store Reporter: Darran Lofthouse We are trying to use more strongly typed self describing configuration however the credential store still depends on configuration properties - this is fine for custom stores but our implementation needs to be easy to configure. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4285) Slow build due to inefficient EnumServiceImpl.doValidation() call

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4285?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-4285: ----------------------------------- Story Points: 3 Sprint: 2019 Week 26-28 > Slow build due to inefficient EnumServiceImpl.doValidation() call > ----------------------------------------------------------------- > > Key: DROOLS-4285 > URL: https://issues.jboss.org/browse/DROOLS-4285 > Project: Drools > Issue Type: Bug > Components: Enumerations Editor > Affects Versions: 7.23.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools, support > > In a live environment with ~1300 assets, the project build takes ~20 minutes when invoked in decision-central. > Using a debugger, I observe that one execution of KieModuleMetaInfo.unmarshallMetaInfos() takes 20 seconds. It's called from EnumServiceImpl.validate(). > {noformat} > at org.drools.core.rule.KieModuleMetaInfo.unmarshallMetaInfos(KieModuleMetaInfo.java:49) > at org.kie.scanner.KieModuleMetaDataImpl.indexMetaInfo(KieModuleMetaDataImpl.java:251) > at org.kie.scanner.KieModuleMetaDataImpl.indexKieModule(KieModuleMetaDataImpl.java:100) > at org.kie.scanner.KieModuleMetaDataImpl.<init>(KieModuleMetaDataImpl.java:85) > at org.kie.scanner.KieModuleMetaData$Factory.newKieModuleMetaData(KieModuleMetaData.java:60) > at org.kie.scanner.KieModuleMetaData$Factory.newKieModuleMetaData(KieModuleMetaData.java:48) > at org.drools.workbench.screens.enums.backend.server.EnumServiceImpl.doValidation(EnumServiceImpl.java:272) > at org.drools.workbench.screens.enums.backend.server.EnumServiceImpl.validate(EnumServiceImpl.java:263) > at org.drools.workbench.screens.enums.backend.server.EnumServiceImpl.validate(EnumServiceImpl.java:253) > at org.drools.workbench.screens.enums.backend.server.EnumServiceImpl$Proxy$_$$_WeldClientProxy.validate(Unknown Source) > at org.kie.workbench.common.services.backend.builder.core.Builder.build(Builder.java:238) > {noformat} > However, {{EnumServiceImpl.validate()}} is repeatedly called in a loop in Builder.build(). So all ".enumeration" files call this method (this project has 18 .enumeration files). It results in 6 min in my env. > Probably the unmarshalled KieModuleMetaInfo can be cached? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4285) Slow build due to inefficient EnumServiceImpl.doValidation() call

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4285?page=com.atlassian.jira.plugi... ] Michael Anstis moved RHDM-1005 to DROOLS-4285: ---------------------------------------------- Project: Drools (was: Red Hat Decision Manager) Key: DROOLS-4285 (was: RHDM-1005) Workflow: GIT Pull Request workflow (was: CDW with docs v1) Docs QE Status: NEW Component/s: Enumerations Editor (was: Decision Central) Affects Version/s: 7.23.0.Final (was: 7.3.1.GA) QE Status: NEW > Slow build due to inefficient EnumServiceImpl.doValidation() call > ----------------------------------------------------------------- > > Key: DROOLS-4285 > URL: https://issues.jboss.org/browse/DROOLS-4285 > Project: Drools > Issue Type: Bug > Components: Enumerations Editor > Affects Versions: 7.23.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools, support > > In a live environment with ~1300 assets, the project build takes ~20 minutes when invoked in decision-central. > Using a debugger, I observe that one execution of KieModuleMetaInfo.unmarshallMetaInfos() takes 20 seconds. It's called from EnumServiceImpl.validate(). > {noformat} > at org.drools.core.rule.KieModuleMetaInfo.unmarshallMetaInfos(KieModuleMetaInfo.java:49) > at org.kie.scanner.KieModuleMetaDataImpl.indexMetaInfo(KieModuleMetaDataImpl.java:251) > at org.kie.scanner.KieModuleMetaDataImpl.indexKieModule(KieModuleMetaDataImpl.java:100) > at org.kie.scanner.KieModuleMetaDataImpl.<init>(KieModuleMetaDataImpl.java:85) > at org.kie.scanner.KieModuleMetaData$Factory.newKieModuleMetaData(KieModuleMetaData.java:60) > at org.kie.scanner.KieModuleMetaData$Factory.newKieModuleMetaData(KieModuleMetaData.java:48) > at org.drools.workbench.screens.enums.backend.server.EnumServiceImpl.doValidation(EnumServiceImpl.java:272) > at org.drools.workbench.screens.enums.backend.server.EnumServiceImpl.validate(EnumServiceImpl.java:263) > at org.drools.workbench.screens.enums.backend.server.EnumServiceImpl.validate(EnumServiceImpl.java:253) > at org.drools.workbench.screens.enums.backend.server.EnumServiceImpl$Proxy$_$$_WeldClientProxy.validate(Unknown Source) > at org.kie.workbench.common.services.backend.builder.core.Builder.build(Builder.java:238) > {noformat} > However, {{EnumServiceImpl.validate()}} is repeatedly called in a loop in Builder.build(). So all ".enumeration" files call this method (this project has 18 .enumeration files). It results in 6 min in my env. > Probably the unmarshalled KieModuleMetaInfo can be cached? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1839) The schemas are in the wrong location

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1839: ------------------------------------- Summary: The schemas are in the wrong location Key: ELY-1839 URL: https://issues.jboss.org/browse/ELY-1839 Project: WildFly Elytron Issue Type: Bug Reporter: Darran Lofthouse Fix For: 1.10.0.CR3 The schemas are currently located in "./tests/base/src/main/resources/schema" these may be needed for testing purposes but these should be in a module somewhere exposed as public API. This could also potentially be a new module that just contains schemas if needed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

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 July 2019