March 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13240) Clustering TS: Default to non-multicast discovery protocol for 'bridge' channel used in XSite tests

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13240?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13240: ---------------------------------- Affects Version/s: 19.0.0.Beta3 > Clustering TS: Default to non-multicast discovery protocol for 'bridge' channel used in XSite tests > --------------------------------------------------------------------------------------------------- > > Key: WFLY-13240 > URL: https://issues.redhat.com/browse/WFLY-13240 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 19.0.0.Beta3 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 20.0.0.Beta1 > > > The last piece in the WFLY-12900 puzzle. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13240) Clustering TS: Default to non-multicast discovery protocol for 'bridge' channel used in XSite tests

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13240?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13240: ---------------------------------- Fix Version/s: 20.0.0.Beta1 > Clustering TS: Default to non-multicast discovery protocol for 'bridge' channel used in XSite tests > --------------------------------------------------------------------------------------------------- > > Key: WFLY-13240 > URL: https://issues.redhat.com/browse/WFLY-13240 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 19.0.0.Beta3 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 20.0.0.Beta1 > > > The last piece in the WFLY-12900 puzzle. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13240) Clustering TS: Default to non-multicast discovery protocol for 'bridge' channel used in XSite tests

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13240?page=com.atlassian.jira.plugi... ] Radoslav Husar reassigned WFLY-13240: ------------------------------------- Assignee: Radoslav Husar (was: Paul Ferraro) > Clustering TS: Default to non-multicast discovery protocol for 'bridge' channel used in XSite tests > --------------------------------------------------------------------------------------------------- > > Key: WFLY-13240 > URL: https://issues.redhat.com/browse/WFLY-13240 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 19.0.0.Beta3 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 20.0.0.Beta1 > > > The last piece in the WFLY-12900 puzzle. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1405) [GSS](7.3.z) JBJCA-1404: Race condition involving Pool.fillTo

by Stephen Fikes (Jira)

Stephen Fikes created JBJCA-1405: ------------------------------------ Summary: [GSS](7.3.z) JBJCA-1404: Race condition involving Pool.fillTo Key: JBJCA-1405 URL: https://issues.redhat.com/browse/JBJCA-1405 Project: IronJacamar Issue Type: Bug Reporter: Stephen Fikes Assignee: Flavia Rainone The fillTo implementation of SemaphoreConcurrentLinkedDequeManagedConnectionPool suffers from the same issue we found in increase capacity: https://github.com/ironjacamar/ironjacamar/pull/695/commits/d80c2ae7713f4... See JBJCA-1399. This means that when more than two threads attempt to add connections to the pool and one of them does so via fillTo, we can run into problems with pool max size. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5162) [DMN Designer] Persist Java FQCN as ItemDefinition attribute for converted Java classes

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5162?page=com.atlassian.jira.plug... ] Michael Anstis updated DROOLS-5162: ----------------------------------- Description: The DMN editor has the ability to import Java files as {{ItemDefinition}}. [~tari_manga] has requested the following enhancement: {quote} ... 2. ... could the DMN editor note in the ItemDefintion the FQN of the java class which was used? By means of extra attribute, extensions, etc. whatever is more convenient {quote} This JIRA is for Business Central, server-side marshalling, only. The linked JIRA is for client-side marshalling, when it becomes viable. was: The DMN editor has the ability to import Java files as {{ItemDefinition}}. [~tari_manga] has requested the following enhancement: {quote} ... 2. ... could the DMN editor note in the ItemDefintion the FQN of the java class which was used? By means of extra attribute, extensions, etc. whatever is more convenient {quote} > [DMN Designer] Persist Java FQCN as ItemDefinition attribute for converted Java classes > --------------------------------------------------------------------------------------- > > Key: DROOLS-5162 > URL: https://issues.redhat.com/browse/DROOLS-5162 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools, kogito-tooling > > The DMN editor has the ability to import Java files as {{ItemDefinition}}. > [~tari_manga] has requested the following enhancement: > {quote} > ... > 2. ... could the DMN editor note in the ItemDefintion the FQN of the java class which was used? > By means of extra attribute, extensions, etc. whatever is more convenient > {quote} > This JIRA is for Business Central, server-side marshalling, only. The linked JIRA is for client-side marshalling, when it becomes viable. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5162) [DMN Designer] Persist Java FQCN as ItemDefinition attribute for converted Java classes

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5162?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-5162: -------------------------------------- Assignee: Daniel José dos Santos (was: Michael Anstis) > [DMN Designer] Persist Java FQCN as ItemDefinition attribute for converted Java classes > --------------------------------------------------------------------------------------- > > Key: DROOLS-5162 > URL: https://issues.redhat.com/browse/DROOLS-5162 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools, kogito-tooling > > The DMN editor has the ability to import Java files as {{ItemDefinition}}. > [~tari_manga] has requested the following enhancement: > {quote} > ... > 2. ... could the DMN editor note in the ItemDefintion the FQN of the java class which was used? > By means of extra attribute, extensions, etc. whatever is more convenient > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5162) [DMN Designer] Persist Java FQCN as ItemDefinition attribute for converted Java classes

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5162?page=com.atlassian.jira.plug... ] Michael Anstis updated DROOLS-5162: ----------------------------------- Reporter: Matteo Mortari (was: Michael Anstis) > [DMN Designer] Persist Java FQCN as ItemDefinition attribute for converted Java classes > --------------------------------------------------------------------------------------- > > Key: DROOLS-5162 > URL: https://issues.redhat.com/browse/DROOLS-5162 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools, kogito-tooling > > The DMN editor has the ability to import Java files as {{ItemDefinition}}. > [~tari_manga] has requested the following enhancement: > {quote} > ... > 2. ... could the DMN editor note in the ItemDefintion the FQN of the java class which was used? > By means of extra attribute, extensions, etc. whatever is more convenient > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5162) [DMN Designer] Persist Java FQCN as ItemDefinition attribute for converted Java classes

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5162?page=com.atlassian.jira.plug... ] Michael Anstis updated DROOLS-5162: ----------------------------------- Description: The DMN editor has the ability to import Java files as {{ItemDefinition}}. [~tari_manga] has requested the following enhancement: {quote} ... 2. ... could the DMN editor note in the ItemDefintion the FQN of the java class which was used? By means of extra attribute, extensions, etc. whatever is more convenient {quote} was: The DMN editor's ability to import Java files as {{ItemDefinition}} requires the ability to gather meta-data for Java classes present in the underlying FileSystem (or container, e.g. VSCode, Che etc). This is currently handled server-side using the {{DataModelOracle}}. The client-side implementation will need to either query the container for Java class meta-data or be able to handle the Java source to extract the meta-data. [~ederign] [~porcelli] Possibly another requirement of the container? [~tari_manga] requested the following: {quote} 1. Is this feature going to be eventually supported in Kogito as well, potentially once a few "Microsoft APIs" and Stunner framework features, will make available to the editor the DMO-equivalent or anyway a service to know which class could be used for this scope? 2. if YES, could the DMN editor note in the ItemDefintion the FQN of the java class which was used? By means of extra attribute, extensions, etc. whatever is more convenient {quote} > [DMN Designer] Persist Java FQCN as ItemDefinition attribute for converted Java classes > --------------------------------------------------------------------------------------- > > Key: DROOLS-5162 > URL: https://issues.redhat.com/browse/DROOLS-5162 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools, kogito-tooling > > The DMN editor has the ability to import Java files as {{ItemDefinition}}. > [~tari_manga] has requested the following enhancement: > {quote} > ... > 2. ... could the DMN editor note in the ItemDefintion the FQN of the java class which was used? > By means of extra attribute, extensions, etc. whatever is more convenient > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5162) [DMN Designer] Persist Java FQCN as ItemDefinition attribute for converted Java classes

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5162?page=com.atlassian.jira.plug... ] Michael Anstis moved KOGITO-1444 to DROOLS-5162: ------------------------------------------------ Project: Drools (was: Kogito) Key: DROOLS-5162 (was: KOGITO-1444) Docs QE Status: NEW Component/s: DMN Editor (was: Authoring Tooling) QE Status: NEW > [DMN Designer] Persist Java FQCN as ItemDefinition attribute for converted Java classes > --------------------------------------------------------------------------------------- > > Key: DROOLS-5162 > URL: https://issues.redhat.com/browse/DROOLS-5162 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools, kogito-tooling > > The DMN editor's ability to import Java files as {{ItemDefinition}} requires the ability to gather meta-data for Java classes present in the underlying FileSystem (or container, e.g. VSCode, Che etc). This is currently handled server-side using the {{DataModelOracle}}. The client-side implementation will need to either query the container for Java class meta-data or be able to handle the Java source to extract the meta-data. > [~ederign] [~porcelli] Possibly another requirement of the container? > [~tari_manga] requested the following: > {quote} > 1. Is this feature going to be eventually supported in Kogito as well, potentially once a few "Microsoft APIs" and Stunner framework features, will make available to the editor the DMO-equivalent or anyway a service to know which class could be used for this scope? > 2. if YES, could the DMN editor note in the ItemDefintion the FQN of the java class which was used? > By means of extra attribute, extensions, etc. whatever is more convenient > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13239) Fix s390 OpenJ9 domain mode testing

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-13239: --------------------------------------- Summary: Fix s390 OpenJ9 domain mode testing Key: WFLY-13239 URL: https://issues.redhat.com/browse/WFLY-13239 Project: WildFly Issue Type: Task Components: Test Suite Reporter: Brian Stansberry Assignee: Yeray Borges Santana Our CI tests of running on a s390 server using OpenJ9 are consistently failing in testsuite/domain: https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterLinuxS390OpenJ911 Specifically CLITestSuite and DomainTestSuite fail. Task is to resolve those and get reasonably consistent execution of those parts of the testsuite. [~luck3y] can provide info re the infrastructure running this job. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 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 2020