January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4906) Maven configuration script is not able to start in HA-CEP image in Openshift

by Massimiliano Dessi (Jira)

Massimiliano Dessi created DROOLS-4906: ------------------------------------------ Summary: Maven configuration script is not able to start in HA-CEP image in Openshift Key: DROOLS-4906 URL: https://issues.redhat.com/browse/DROOLS-4906 Project: Drools Issue Type: Bug Reporter: Massimiliano Dessi Assignee: Massimiliano Dessi -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4791) HttpManagementConstantHeadersTestCase causes tests failures

by Richard Opalka (Jira)

[ https://issues.redhat.com/browse/WFCORE-4791?page=com.atlassian.jira.plug... ] Richard Opalka updated WFCORE-4791: ----------------------------------- Description: Commit 68928b0b in WildFly-Core introduced new regression. High probably test doesn't do proper test environment clean up and some tests following it are thus failing. The issue isn't visible in our CI environment so it probably depends on actual tests ordering. I am able to reproduce this issue on my laptop always. was: Commit 68928b0b in WildFly-Core introduced new regression. High probably test doesn't do proper test environment clean up and some tests following it are thus failing. The issue isn't visible in our CI environment so it probably depends on actual tests ordering. I am able to reproduce this issue always on my laptop. > HttpManagementConstantHeadersTestCase causes tests failures > ----------------------------------------------------------- > > Key: WFCORE-4791 > URL: https://issues.redhat.com/browse/WFCORE-4791 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Reporter: Richard Opalka > Assignee: Tomas Terem > Priority: Major > Fix For: 11.0.0.Beta6 > > Attachments: testsuite.log > > > Commit 68928b0b in WildFly-Core introduced new regression. > High probably test doesn't do proper test environment clean up > and some tests following it are thus failing. The issue isn't visible > in our CI environment so it probably depends on actual tests ordering. > I am able to reproduce this issue on my laptop always. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4791) HttpManagementConstantHeadersTestCase causes tests failures

by Richard Opalka (Jira)

[ https://issues.redhat.com/browse/WFCORE-4791?page=com.atlassian.jira.plug... ] Richard Opalka updated WFCORE-4791: ----------------------------------- Attachment: testsuite.log > HttpManagementConstantHeadersTestCase causes tests failures > ----------------------------------------------------------- > > Key: WFCORE-4791 > URL: https://issues.redhat.com/browse/WFCORE-4791 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Reporter: Richard Opalka > Assignee: Tomas Terem > Priority: Major > Fix For: 11.0.0.Beta6 > > Attachments: testsuite.log > > > Commit 68928b0b in WildFly-Core introduced new regression. > High probably test doesn't do proper test environment clean up > and some tests following it are thus failing. The issue isn't visible > in our CI environment so it probably depends on actual tests ordering. > I am able to reproduce this issue always on my laptop. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4546) GDST V&V: Add support for ranges

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4546?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-4546: --------------------------------- Sprint: 2019 Week 50-52 (from Dec 9) (was: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > GDST V&V: Add support for ranges > -------------------------------- > > Key: DROOLS-4546 > URL: https://issues.redhat.com/browse/DROOLS-4546 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Data modeller supports ranges. That information can be used to improve GDST V&V reporting. > https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-common-forms... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3094) Create a Verifier backend adapter for DMN tables

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-3094?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-3094: --------------------------------- Sprint: 2019 Week 50-52 (from Dec 9) (was: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > Create a Verifier backend adapter for DMN tables > ------------------------------------------------ > > Key: DROOLS-3094 > URL: https://issues.redhat.com/browse/DROOLS-3094 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Optional > Labels: drools-tools, verifier > > The goal is to make it possible to run the DMN Validation using the DMN backend validate-method. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4791) HttpManagementConstantHeadersTestCase causes tests failures

by Richard Opalka (Jira)

Richard Opalka created WFCORE-4791: -------------------------------------- Summary: HttpManagementConstantHeadersTestCase causes tests failures Key: WFCORE-4791 URL: https://issues.redhat.com/browse/WFCORE-4791 Project: WildFly Core Issue Type: Bug Components: Test Suite Reporter: Richard Opalka Assignee: Tomas Terem Fix For: 11.0.0.Beta6 Commit 68928b0b in WildFly-Core introduced new regression. High probably test doesn't do proper test environment clean up and some tests following it are thus failing. The issue isn't visible in our CI environment so it probably depends on actual tests ordering. I am able to reproduce this issue always on my laptop. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4876) GDST: Aliases only work for Strings

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4876?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-4876: --------------------------------- Story Points: 1 (was: 3) > GDST: Aliases only work for Strings > ----------------------------------- > > Key: DROOLS-4876 > URL: https://issues.redhat.com/browse/DROOLS-4876 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > If you use the Column creator and add an alias for any other column type than String, the aliases do not show up. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4882) [Guided DecisionTable] Incorrect getters and setters for fields that starts with one lowercase letter

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4882?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-4882: --------------------------------- Story Points: 1 > [Guided DecisionTable] Incorrect getters and setters for fields that starts with one lowercase letter > ----------------------------------------------------------------------------------------------------- > > Key: DROOLS-4882 > URL: https://issues.redhat.com/browse/DROOLS-4882 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor, Guided Decision Tree Editor, Guided Rule Editor, Guided Score Card Editor, Guided Template Editor > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Major > Labels: reported-by-qe > > If the guided decision table uses fact field that has form 'xXxxx' then the generated getters and setters are incorrect. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4883) Test Scenario: create kie-docs content for Test Scenario Kie-server support

by Daniele Zonca (Jira)

[ https://issues.redhat.com/browse/DROOLS-4883?page=com.atlassian.jira.plug... ] Daniele Zonca updated DROOLS-4883: ---------------------------------- Story Points: 5 (was: 3) > Test Scenario: create kie-docs content for Test Scenario Kie-server support > --------------------------------------------------------------------------- > > Key: DROOLS-4883 > URL: https://issues.redhat.com/browse/DROOLS-4883 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: drools-tools > > Document how to enable test-scenario capability in Kie-server and how to use it -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3957) Make verifier panel use docks

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-3957?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-3957: --------------------------------- Story Points: 1 (was: 3) > Make verifier panel use docks > ----------------------------- > > Key: DROOLS-3957 > URL: https://issues.redhat.com/browse/DROOLS-3957 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > Attachments: v&v.webm > > > Pretty sure we had a ticket for this, but could not find it. Here it is. > h3. Acceptance test > On both Firefox and Chrome (/) > - Opening multiple decision tables, switching between them > - Repeated reopening of guided decision table > - Opening other asset that uses docks - scenario, data object > Selenium tests updated https://github.com/jboss-integration/bxms-qe-tests/pull/2971 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4883) Test Scenario: create kie-docs content for Test Scenario Kie-server support

by Daniele Zonca (Jira)

[ https://issues.redhat.com/browse/DROOLS-4883?page=com.atlassian.jira.plug... ] Daniele Zonca updated DROOLS-4883: ---------------------------------- Sprint: 2020 Week 01-03 (from Dec 30) > Test Scenario: create kie-docs content for Test Scenario Kie-server support > --------------------------------------------------------------------------- > > Key: DROOLS-4883 > URL: https://issues.redhat.com/browse/DROOLS-4883 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: drools-tools > > Document how to enable test-scenario capability in Kie-server and how to use it -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4883) Test Scenario: create kie-docs content for Test Scenario Kie-server support

by Daniele Zonca (Jira)

[ https://issues.redhat.com/browse/DROOLS-4883?page=com.atlassian.jira.plug... ] Daniele Zonca updated DROOLS-4883: ---------------------------------- Story Points: 3 > Test Scenario: create kie-docs content for Test Scenario Kie-server support > --------------------------------------------------------------------------- > > Key: DROOLS-4883 > URL: https://issues.redhat.com/browse/DROOLS-4883 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: drools-tools > > Document how to enable test-scenario capability in Kie-server and how to use it -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4901) [DMN Designer] Data Types - Drag and Drop - Error when a single structure data type is dragged twice

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4901?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4901: ------------------------------------ Sprint: 2020 Week 01-03 (from Dec 30) > [DMN Designer] Data Types - Drag and Drop - Error when a single structure data type is dragged twice > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-4901 > URL: https://issues.redhat.com/browse/DROOLS-4901 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: 2020-01-03 16.48.12.gif > > > Error when a single structure data type is dragged twice. See the steps to reproduce: > !2020-01-03 16.48.12.gif|width=300! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4803) [DMN Designer] Data Types - Drag and Drop - User is unable to reorder structure items

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4803?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4803: ------------------------------------ Sprint: 2020 Week 01-03 (from Dec 30) > [DMN Designer] Data Types - Drag and Drop - User is unable to reorder structure items > ------------------------------------------------------------------------------------- > > Key: DROOLS-4803 > URL: https://issues.redhat.com/browse/DROOLS-4803 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.31.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: reorder-structure-items.webm > > > If user wants to reorder the items of a DMN structure, the dragged item is always taken out from the Structure between top level data types. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4901) [DMN Designer] Data Types - Drag and Drop - Error when a single structure data type is dragged twice

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4901?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4901: ------------------------------------ Sprint: (was: 2020 Week 01-03 (from Dec 30)) > [DMN Designer] Data Types - Drag and Drop - Error when a single structure data type is dragged twice > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-4901 > URL: https://issues.redhat.com/browse/DROOLS-4901 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: 2020-01-03 16.48.12.gif > > > Error when a single structure data type is dragged twice. See the steps to reproduce: > !2020-01-03 16.48.12.gif|width=300! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4803) [DMN Designer] Data Types - Drag and Drop - User is unable to reorder structure items

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4803?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4803: ------------------------------------ Sprint: (was: 2020 Week 01-03 (from Dec 30)) > [DMN Designer] Data Types - Drag and Drop - User is unable to reorder structure items > ------------------------------------------------------------------------------------- > > Key: DROOLS-4803 > URL: https://issues.redhat.com/browse/DROOLS-4803 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.31.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: reorder-structure-items.webm > > > If user wants to reorder the items of a DMN structure, the dragged item is always taken out from the Structure between top level data types. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4847) [DMN Designer] Entries are expanded when user edit structures in a row

by Daniel José dos Santos (Jira)

[ https://issues.redhat.com/browse/DROOLS-4847?page=com.atlassian.jira.plug... ] Daniel José dos Santos updated DROOLS-4847: ------------------------------------------- Story Points: 5 > [DMN Designer] Entries are expanded when user edit structures in a row > ----------------------------------------------------------------------- > > Key: DROOLS-4847 > URL: https://issues.redhat.com/browse/DROOLS-4847 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.31.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: edit-in-a-row.webm > > > Data types entries are unexpectedly expanded when user click edit button of structures in a row. See the attached video. > The issue was found during DROOLS-4795 review, however probably it is not related. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4846) [DMN Designer] User is unable to save model when multilevel structure is removed

by Daniel José dos Santos (Jira)

[ https://issues.redhat.com/browse/DROOLS-4846?page=com.atlassian.jira.plug... ] Daniel José dos Santos updated DROOLS-4846: ------------------------------------------- Story Points: 2 > [DMN Designer] User is unable to save model when multilevel structure is removed > -------------------------------------------------------------------------------- > > Key: DROOLS-4846 > URL: https://issues.redhat.com/browse/DROOLS-4846 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.31.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Minor > Labels: drools-tools > Fix For: 7.32.0.Final > > Attachments: multilevel-structure.webm > > > There is scenario causing user is not able to save the DMN file anymore. If is editing some multilevel structure field, but he decides in the middle of editing to remove whole top level structure, the save button of the designer remains disabled. See the attached video. > We should either fix this scenario or drop the *disable save button* feature. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4833) [DMN Designer] Data Types - edit is not consistent

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4833?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4833: ------------------------------------ Sprint: 2020 Week 01-03 (from Dec 30) > [DMN Designer] Data Types - edit is not consistent > -------------------------------------------------- > > Key: DROOLS-4833 > URL: https://issues.redhat.com/browse/DROOLS-4833 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.31.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: edit-focus.webm > > > There is an inconsistent behavior of the "edit" mode according to the way in invoke it. See the video. Once started by mouse, once by keyboard. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3936) [DMN Designer] Data Types - Constraints enumeration - skip zero values

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-3936?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-3936: ------------------------------------ Sprint: 2020 Week 01-03 (from Dec 30) > [DMN Designer] Data Types - Constraints enumeration - skip zero values > ---------------------------------------------------------------------- > > Key: DROOLS-3936 > URL: https://issues.redhat.com/browse/DROOLS-3936 > Project: Drools > Issue Type: Task > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: DROOLS-3936.png > > > In the Data Types tab > Data Types list > Constraints > Enumeration (for *days and time duration*): > !DROOLS-3936.png|thumbnail! > We must skip zeros, and show: > *1 day* > ...instead of showing: > *1 day, 0 hours, 0 minutes, 0 seconds* -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1048) Testcases - Kiali Validations sync-up

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1048?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan commented on SWSQE-1048: --------------------------------------- "VirtualService is pointing to a non-existent gateway", in example there are more errors. v2 should be changed to v1. > Testcases - Kiali Validations sync-up > ------------------------------------- > > Key: SWSQE-1048 > URL: https://issues.redhat.com/browse/SWSQE-1048 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Sunil Kondkar > Priority: Major > > Sync up all validations from https://kiali.io/documentation/validations/ with Polarion estcases. > Make sure all validations have up-to-date testcases in Polarion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3292) [DMN Designer] Custom Data Type dialog can be invoked from read only mode

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-3292?page=com.atlassian.jira.plug... ] Guilherme Gomes edited comment on DROOLS-3292 at 1/7/20 7:47 AM: ----------------------------------------------------------------- [~jomarko] Can we close this JIRA? was (Author: karreiro): [~jomarko] Can we close this one? > [DMN Designer] Custom Data Type dialog can be invoked from read only mode > ------------------------------------------------------------------------- > > Key: DROOLS-3292 > URL: https://issues.redhat.com/browse/DROOLS-3292 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Trivial > Labels: drools-tools > Attachments: Screenshot from 2018-11-09 09-25-38.png > > > In the attachment is shown manage button is not disabled in read only mode. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3292) [DMN Designer] Custom Data Type dialog can be invoked from read only mode

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-3292?page=com.atlassian.jira.plug... ] Guilherme Gomes commented on DROOLS-3292: ----------------------------------------- [~jomarko] Can we close this one? > [DMN Designer] Custom Data Type dialog can be invoked from read only mode > ------------------------------------------------------------------------- > > Key: DROOLS-3292 > URL: https://issues.redhat.com/browse/DROOLS-3292 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Trivial > Labels: drools-tools > Attachments: Screenshot from 2018-11-09 09-25-38.png > > > In the attachment is shown manage button is not disabled in read only mode. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12936) Provide ability to configure HTTP/2 (requires TLSv1.2) in FIPS mode (PKCS11)

by Diana Vilkolakova (Jira)

Diana Vilkolakova created WFLY-12936: ---------------------------------------- Summary: Provide ability to configure HTTP/2 (requires TLSv1.2) in FIPS mode (PKCS11) Key: WFLY-12936 URL: https://issues.redhat.com/browse/WFLY-12936 Project: WildFly Issue Type: Feature Request Components: Security Reporter: Diana Vilkolakova Assignee: Diana Vilkolakova -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4905) [DMN Designer] Code Completion - Index all elements named by users

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4905?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4905: ------------------------------------ Summary: [DMN Designer] Code Completion - Index all elements named by users (was: [DMN Designer] Code Completion - Index all elements named by user) > [DMN Designer] Code Completion - Index all elements named by users > ------------------------------------------------------------------ > > Key: DROOLS-4905 > URL: https://issues.redhat.com/browse/DROOLS-4905 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > Create the infrastructure code that provided all elements named by the user. It will be called by the suggestion component. So users will be able to see as suggestions DRG Elements and Data Types. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4905) [DMN Designer] Code Completion - Index all elements named by user

by Guilherme Gomes (Jira)

Guilherme Gomes created DROOLS-4905: --------------------------------------- Summary: [DMN Designer] Code Completion - Index all elements named by user Key: DROOLS-4905 URL: https://issues.redhat.com/browse/DROOLS-4905 Project: Drools Issue Type: Task Components: DMN Editor Reporter: Guilherme Gomes Assignee: Guilherme Gomes Create the infrastructure code that provided all elements named by the user. It will be called by the suggestion component. So users will be able to see as suggestions DRG Elements and Data Types. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4681) [DMN Designer] Data Types - Implement the new dropdown design in the type selector

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4681?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4681: ------------------------------------ Sprint: 2019 Week 50-52 (from Dec 9) (was: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > [DMN Designer] Data Types - Implement the new dropdown design in the type selector > ---------------------------------------------------------------------------------- > > Key: DROOLS-4681 > URL: https://issues.redhat.com/browse/DROOLS-4681 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: prototype.png > > > Implement the new dropdown design in the type selector, following the prototype: > !prototype.png|width=600! > Notice: this JIRA comprehends the tooltip into the label as well. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4901) [DMN Designer] Data Types - Drag and Drop - Error when a single structure data type is dragged twice

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4901?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4901: ------------------------------------ Sprint: 2020 Week 01-03 (from Dec 30) > [DMN Designer] Data Types - Drag and Drop - Error when a single structure data type is dragged twice > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-4901 > URL: https://issues.redhat.com/browse/DROOLS-4901 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: 2020-01-03 16.48.12.gif > > > Error when a single structure data type is dragged twice. See the steps to reproduce: > !2020-01-03 16.48.12.gif|width=300! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4803) [DMN Designer] User is unable to reorder structure items

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4803?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4803: ------------------------------------ Sprint: 2020 Week 01-03 (from Dec 30) > [DMN Designer] User is unable to reorder structure items > -------------------------------------------------------- > > Key: DROOLS-4803 > URL: https://issues.redhat.com/browse/DROOLS-4803 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.31.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: reorder-structure-items.webm > > > If user wants to reorder the items of a DMN structure, the dragged item is always taken out from the Structure between top level data types. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4803) [DMN Designer] Data Types - Drag and Drop - User is unable to reorder structure items

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4803?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4803: ------------------------------------ Summary: [DMN Designer] Data Types - Drag and Drop - User is unable to reorder structure items (was: [DMN Designer] User is unable to reorder structure items) > [DMN Designer] Data Types - Drag and Drop - User is unable to reorder structure items > ------------------------------------------------------------------------------------- > > Key: DROOLS-4803 > URL: https://issues.redhat.com/browse/DROOLS-4803 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.31.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: reorder-structure-items.webm > > > If user wants to reorder the items of a DMN structure, the dragged item is always taken out from the Structure between top level data types. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4803) [DMN Designer] User is unable to reorder structure items

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4803?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4803: ------------------------------------ Story Points: 3 > [DMN Designer] User is unable to reorder structure items > -------------------------------------------------------- > > Key: DROOLS-4803 > URL: https://issues.redhat.com/browse/DROOLS-4803 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.31.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: reorder-structure-items.webm > > > If user wants to reorder the items of a DMN structure, the dragged item is always taken out from the Structure between top level data types. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4480) [DMN Designer] Business Central Data Objects as DMN Data Types (7.6)

by Daniel José dos Santos (Jira)

[ https://issues.redhat.com/browse/DROOLS-4480?page=com.atlassian.jira.plug... ] Daniel José dos Santos resolved DROOLS-4480. -------------------------------------------- Resolution: Done > [DMN Designer] Business Central Data Objects as DMN Data Types (7.6) > -------------------------------------------------------------------- > > Key: DROOLS-4480 > URL: https://issues.redhat.com/browse/DROOLS-4480 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > > This is an umbrella for all JIRAs (target to 7.6) related to Business Central Data Objects as DMN Data Types. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4752) [DMN Designer] Code Completion - When users press Escape on suggestions the edit mode is closed

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4752?page=com.atlassian.jira.plug... ] Guilherme Gomes resolved DROOLS-4752. ------------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/kie-wb-common/pull/3000 > [DMN Designer] Code Completion - When users press Escape on suggestions the edit mode is closed > ----------------------------------------------------------------------------------------------- > > Key: DROOLS-4752 > URL: https://issues.redhat.com/browse/DROOLS-4752 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > This bug was created by this comment: https://github.com/kiegroup/kie-wb-common/pull/3000#issuecomment-553442743 > {quote}*Reported by Jozef:* > Once completions are shown, then pressing Escape hides them however cancel also edit mode of the cell, I am not sure what customers will think about this. > {quote} > Check with UX the expected behaviour, and implement the expected behaviour for the Escape key in the described case > The severity of the issue is higher if we follow this steps: > - Put some value into cell, confirm it == finish edit mode > - Edit the same cell, type new expression > - Very probably autocompletions will be shown > - However imagine you do not want to use any hint, so you press *Escape* > - Now the completions are hidden, however also edit mode was canceled and typed value was not stored -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4752) [DMN Designer] Code Completion - When users press Escape on suggestions the edit mode is closed

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4752?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4752: ------------------------------------ Sprint: 2020 Week 01-03 (from Dec 30) > [DMN Designer] Code Completion - When users press Escape on suggestions the edit mode is closed > ----------------------------------------------------------------------------------------------- > > Key: DROOLS-4752 > URL: https://issues.redhat.com/browse/DROOLS-4752 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > This bug was created by this comment: https://github.com/kiegroup/kie-wb-common/pull/3000#issuecomment-553442743 > {quote}*Reported by Jozef:* > Once completions are shown, then pressing Escape hides them however cancel also edit mode of the cell, I am not sure what customers will think about this. > {quote} > Check with UX the expected behaviour, and implement the expected behaviour for the Escape key in the described case > The severity of the issue is higher if we follow this steps: > - Put some value into cell, confirm it == finish edit mode > - Edit the same cell, type new expression > - Very probably autocompletions will be shown > - However imagine you do not want to use any hint, so you press *Escape* > - Now the completions are hidden, however also edit mode was canceled and typed value was not stored -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-293) Current implementation of MP-JWT doesn't require claims which should be required

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFWIP-293?page=com.atlassian.jira.plugin... ] Darran Lofthouse commented on WFWIP-293: ---------------------------------------- I will have a look at this one now. > Current implementation of MP-JWT doesn't require claims which should be required > -------------------------------------------------------------------------------- > > Key: WFWIP-293 > URL: https://issues.redhat.com/browse/WFWIP-293 > Project: WildFly WIP > Issue Type: Bug > Components: MP JWT > Reporter: Jan Kasik > Assignee: Darran Lofthouse > Priority: Critical > > Chapter 4.1 of MP-JWT 1.1 recommends minimal set of JWT claims which should be required. > Current implementation doesn't check for following claims and returns 200/OK if they are missing: > * {{upn}} > * {{jti}} > * {{groups}} > * {{iat}} > * {{sub}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12935) Replace Java EE7 Concurrency RI with Jakarta EE 8 Concurrency RI

by Eduardo Martins (Jira)

Eduardo Martins created WFLY-12935: -------------------------------------- Summary: Replace Java EE7 Concurrency RI with Jakarta EE 8 Concurrency RI Key: WFLY-12935 URL: https://issues.redhat.com/browse/WFLY-12935 Project: WildFly Issue Type: Enhancement Components: Concurrency Utilities Reporter: Eduardo Martins Assignee: Eduardo Martins The new Jakarta EE8 Concurrency RI is fully compatible with Java EE7 Concurrency RI and besides already including a few bug fixes its development is active, thus it makes sense to upgrade the base framework of WildFly EE Concurrency Utilities implementation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2841) [DMN Designer] Sort item definitions of the model

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-2841?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-2841: -------------------------------- Priority: Minor (was: Major) > [DMN Designer] Sort item definitions of the model > ------------------------------------------------- > > Key: DROOLS-2841 > URL: https://issues.redhat.com/browse/DROOLS-2841 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.10.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Minor > Labels: drools-tools > > The DMN model file can contain custom item definitions. These are then shown in the data type picker dialog. Currently these definitions are not sorted in the dialog. We should sort them and their attributes alphabetically (a -> z). > Possibility to change key for sorting shouldn't be implemented. If such requirement appears in future, will be implemented in separate jira. > h2. Acceptance Test > - Ordering of {{A a B b C c}} doesn't result to {{A B C a b c}} > - Ordering is applied in properties panel, output data type selectbox > - Ordering is applied in *Manage custom data type* dialog > - Changes in *Manage custom data type* dialog are reflected into > -- *Manage custom data type* dialog > -- output data type selectbox -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4869) [DMN Designer] Data Types - Unexpected jump on clicking a row on the datatypes table

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4869?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-4869: -------------------------------- Affects Version/s: 7.32.0.Final > [DMN Designer] Data Types - Unexpected jump on clicking a row on the datatypes table > ------------------------------------------------------------------------------------ > > Key: DROOLS-4869 > URL: https://issues.redhat.com/browse/DROOLS-4869 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.32.0.Final > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: steps-to-reproduce.mp4 > > > When users click on a list of that types that has a scroll bar, the screen unexpectedly jumps to a non-related data type. > See the steps to reproduce: > [^steps-to-reproduce.mp4] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4869) [DMN Designer] Data Types - Unexpected jump on clicking a row on the datatypes table

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4869?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-4869: -------------------------------- Issue Type: Bug (was: Task) > [DMN Designer] Data Types - Unexpected jump on clicking a row on the datatypes table > ------------------------------------------------------------------------------------ > > Key: DROOLS-4869 > URL: https://issues.redhat.com/browse/DROOLS-4869 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.32.0.Final > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: steps-to-reproduce.mp4 > > > When users click on a list of that types that has a scroll bar, the screen unexpectedly jumps to a non-related data type. > See the steps to reproduce: > [^steps-to-reproduce.mp4] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-293) Current implementation of MP-JWT doesn't require claims which should be required

by Jan Kasik (Jira)

Jan Kasik created WFWIP-293: ------------------------------- Summary: Current implementation of MP-JWT doesn't require claims which should be required Key: WFWIP-293 URL: https://issues.redhat.com/browse/WFWIP-293 Project: WildFly WIP Issue Type: Bug Components: MP JWT Reporter: Jan Kasik Assignee: Darran Lofthouse Chapter 4.1 of MP-JWT 1.1 recommends minimal set of JWT claims which should be required. Current implementation doesn't check for following claims and returns 200/OK if they are missing: * {{upn}} * {{jti}} * {{groups}} * {{iat}} * {{sub}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12934) Remove link to google plus on https://wildfly.org/

by Jpa Ge (Jira)

Jpa Ge created WFLY-12934: ----------------------------- Summary: Remove link to google plus on https://wildfly.org/ Key: WFLY-12934 URL: https://issues.redhat.com/browse/WFLY-12934 Project: WildFly Issue Type: Bug Reporter: Jpa Ge Assignee: Brian Stansberry On the website, https://wildfly.org/, in the "Follow us" menu, there an sub menu for google plus. But google plus was turned off in december 2018. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4904) DMN raise RTF wrong PMT example

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-4904?page=com.atlassian.jira.plug... ] Matteo Mortari resolved DROOLS-4904. ------------------------------------ Resolution: Done done with https://issues.omg.org/browse/INBOX-939 > DMN raise RTF wrong PMT example > ------------------------------- > > Key: DROOLS-4904 > URL: https://issues.redhat.com/browse/DROOLS-4904 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > report wrong example as described in [DROOLS-4812] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4904) DMN raise RTF wrong PMT example

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-4904: -------------------------------------- Summary: DMN raise RTF wrong PMT example Key: DROOLS-4904 URL: https://issues.redhat.com/browse/DROOLS-4904 Project: Drools Issue Type: Task Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari report wrong example as described in [DROOLS-4812] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11388) User is not informed about incorrect values in exposed-subsystems for MP Metrics

by Lin Gao (Jira)

[ https://issues.redhat.com/browse/WFLY-11388?page=com.atlassian.jira.plugi... ] Lin Gao updated WFLY-11388: --------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/12884 (was: https://github.com/wildfly/wildfly/pull/11998) > User is not informed about incorrect values in exposed-subsystems for MP Metrics > -------------------------------------------------------------------------------- > > Key: WFLY-11388 > URL: https://issues.redhat.com/browse/WFLY-11388 > Project: WildFly > Issue Type: Bug > Components: MP Metrics > Reporter: Rostislav Svoboda > Assignee: Lin Gao > Priority: Major > > User is not informed about incorrect values in exposed-subsystems for MP Metrics > When I do stuff like > {code} > /subsystem=microprofile-metrics-smallrye/:write-attribute(name=exposed-subsystems, value=["batch_jberet"]) > {code} > instead of > {code} > /subsystem=microprofile-metrics-smallrye/:write-attribute(name=exposed-subsystems, value=["batch-jberet"]) > {code} > I get no warning about non-existing subsystem. > User should be informed about misconfiguration. > Question is when: > - when server boots > - when the cli / management command is invoked > - both cases -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11388) User is not informed about incorrect values in exposed-subsystems for MP Metrics

by Lin Gao (Jira)

[ https://issues.redhat.com/browse/WFLY-11388?page=com.atlassian.jira.plugi... ] Lin Gao commented on WFLY-11388: -------------------------------- Update PR: https://github.com/wildfly/wildfly/pull/12884 > User is not informed about incorrect values in exposed-subsystems for MP Metrics > -------------------------------------------------------------------------------- > > Key: WFLY-11388 > URL: https://issues.redhat.com/browse/WFLY-11388 > Project: WildFly > Issue Type: Bug > Components: MP Metrics > Reporter: Rostislav Svoboda > Assignee: Lin Gao > Priority: Major > > User is not informed about incorrect values in exposed-subsystems for MP Metrics > When I do stuff like > {code} > /subsystem=microprofile-metrics-smallrye/:write-attribute(name=exposed-subsystems, value=["batch_jberet"]) > {code} > instead of > {code} > /subsystem=microprofile-metrics-smallrye/:write-attribute(name=exposed-subsystems, value=["batch-jberet"]) > {code} > I get no warning about non-existing subsystem. > User should be informed about misconfiguration. > Question is when: > - when server boots > - when the cli / management command is invoked > - both cases -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-291) Log messages from io.smallrye.openapi don't have message ID

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFWIP-291?page=com.atlassian.jira.plugin... ] Darran Lofthouse commented on WFWIP-291: ---------------------------------------- Additionally there is also a general issue in that we can not impose our own logging formats on third party projects pulled into WildFly. If a third party project throws an Exception we can catch we may have an opportunity to catch and log with an ID or rethrow with an ID but we don't have options to intercept messages directly logged. Having said that it does seem SmallRye will be receptive to having support added to internatinalised messages with IDs but as with the comment from Paul this would not cover messages at debug or trace level. > Log messages from io.smallrye.openapi don't have message ID > ----------------------------------------------------------- > > Key: WFWIP-291 > URL: https://issues.redhat.com/browse/WFWIP-291 > Project: WildFly WIP > Issue Type: Bug > Components: MP OpenAPI > Reporter: Fabio Burzigotti > Assignee: Paul Ferraro > Priority: Major > > Messages logged by io.smallrye.openapi don't have assigned ID: > {code} > 2020-01-05 16:58:49,225 DEBUG [io.smallrye.openapi.runtime.util.SchemaFactory] (MSC service thread 1-4) Processing a single @Schema annotation. > 2020-01-05 16:58:49,225 DEBUG [io.smallrye.openapi.runtime.scanner.OpenApiAnnotationScanner] (MSC service thread 1-4) Processing a single @Response annotation. > 2020-01-05 16:58:49,225 DEBUG [io.smallrye.openapi.runtime.scanner.OpenApiAnnotationScanner] (MSC service thread 1-4) Processing jax-rs method: {0} > 2020-01-05 16:58:49,225 DEBUG [io.smallrye.openapi.runtime.scanner.OpenApiDataObjectScanner] (MSC service thread 1-4) Starting processing with root: java.lang.String > {code} > A search in SmallRye implementation seems to show that IDs are not used even when level is WARN: > {code} > $ find . -name '*.*' -type f -print0 | xargs -0 grep --color -n -e 'LOG.warn' > ./implementation/src/main/java/io/smallrye/openapi/runtime/scanner/ParameterProcessor.java:551: LOG.warnf("Matrix parameter references missing path segment: %s", segmentName); > ./implementation/src/main/java/io/smallrye/openapi/runtime/scanner/ParameterProcessor.java:1147: LOG.warnf("Value '%s' is not a valid %s default", stringValue, primitive.name().toLowerCase()); > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1048) Testcases - Kiali Validations sync-up

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1048?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan edited comment on SWSQE-1048 at 1/7/20 3:24 AM: --------------------------------------------------------------- "More than one Destination Rule for the same host subset combination" error text is shows in fact: "More than one DestinationRules for the same host subset combination" was (Author: hhovsepy): "More than one Destination Rule for the same host subset combination" error text before was a different one. > Testcases - Kiali Validations sync-up > ------------------------------------- > > Key: SWSQE-1048 > URL: https://issues.redhat.com/browse/SWSQE-1048 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Sunil Kondkar > Priority: Major > > Sync up all validations from https://kiali.io/documentation/validations/ with Polarion estcases. > Make sure all validations have up-to-date testcases in Polarion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4902) Can not use mod operators (%) in when clause.

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4902?page=com.atlassian.jira.plug... ] Mario Fusco resolved DROOLS-4902. --------------------------------- Resolution: Done Fixed in mvel with https://github.com/mvel/mvel/commit/691466dd5657317a421792dfb1c366394288c1fe In the meanwhile you can workaround this issue with additional parenthesis like in: {code} Number( (this % 5) == 0 ) {code} > Can not use mod operators (%) in when clause. > --------------------------------------------- > > Key: DROOLS-4902 > URL: https://issues.redhat.com/browse/DROOLS-4902 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.31.0.Final > Reporter: xb l > Assignee: Mario Fusco > Priority: Major > > When I study drools , I write a rule use divide operator > {code:java} > rule "Buzz" salience 2 > when > $n: Number( this / 5 == 3 ) > then > System.out.println("Buzz"); > end > {code} > It's OK. > But: > {code:java} > rule "Buzz" salience 2 > when > $n: Number( this % 5 == 0 ) > then > System.out.println("Buzz"); > end > {code} > Report parser error: Unable to Analyse Expression this % 5 == 0: > The drools document mentioned the same example: > Person( age > 100 && ( age % 10 == 0 ) ) > % is Multiplicative operators, why parser error? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1048) Testcases - Kiali Validations sync-up

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1048?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan commented on SWSQE-1048: --------------------------------------- "mTLS settings of a non-local Destination Rule are overridden" exception, v10 in example is typo and causing other warning which confuses, should be v1. > Testcases - Kiali Validations sync-up > ------------------------------------- > > Key: SWSQE-1048 > URL: https://issues.redhat.com/browse/SWSQE-1048 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Sunil Kondkar > Priority: Major > > Sync up all validations from https://kiali.io/documentation/validations/ with Polarion estcases. > Make sure all validations have up-to-date testcases in Polarion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4903) In constraints fail to compile if negated or inside a forall pattern

by Matteo Casalino (Jira)

[ https://issues.redhat.com/browse/DROOLS-4903?page=com.atlassian.jira.plug... ] Matteo Casalino updated DROOLS-4903: ------------------------------------ Description: It appears that the KieBuilder fails to compile the following pattern: {noformat} Pojo(!(x in (1,2,3))) {noformat} returning the following error: {noformat} Error Messages: Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 text=Unable to Analyse Expression !(x in (1,2,3)): [Error: unexpected token: ,2] [Near : {... !(x in (1,2,3)) ....}] {noformat} Furthermore, as of Drools 7.29.0.Final, the following form will also fail to compile: {noformat} forall(Pojo(y==42, x in (1,2,3))) {noformat} with the following error: {noformat} Error Messages: Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 text=Unable to Analyse Expression !(y==42) || !(x in (1,2,3)): [Error: unexpected token: ,2] [Near : {... !(y==42) || !(x in (1,2,3)) ....}] {noformat} The latter is likely a consequence of the negation introduced by [DROOLS-4632], [DROOLS-4633] was: It appears that the KieBuilder fails to compile the following pattern: {noformat} Pojo(!(x in (1,2,3))) {noformat} returning the following error: {noformat} Error Messages: Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 text=Unable to Analyse Expression !(x in (1,2,3)): [Error: unexpected token: ,2] [Near : {... !(x in (1,2,3)) ....}] {noformat} Furthermore, as of Drools 7.29.0.Final, the following form will also fail to compile: {noformat} forall(Pojo(y==42, x in (1,2,3))) {noformat} with the following error: {noformat} Error Messages: Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 text=Unable to Analyse Expression !(y==42) || !(x in (1,2,3)): [Error: unexpected token: ,2] [Near : {... !(y==42) || !(x in (1,2,3)) ....}] {noformat} The latter is likely a consequence of the negation introduced by [DROOLS-4632|https://issues.redhat.com/browse/DROOLS-4632], [DROOLS-4633][https://issues.redhat.com/browse/DROOLS-4633] > In constraints fail to compile if negated or inside a forall pattern > -------------------------------------------------------------------- > > Key: DROOLS-4903 > URL: https://issues.redhat.com/browse/DROOLS-4903 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.31.0.Final > Reporter: Matteo Casalino > Assignee: Mario Fusco > Priority: Major > Attachments: in-constraint-negation.tgz > > > It appears that the KieBuilder fails to compile the following pattern: > {noformat} > Pojo(!(x in (1,2,3))) > {noformat} > returning the following error: > {noformat} > Error Messages: > Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 > text=Unable to Analyse Expression !(x in (1,2,3)): > [Error: unexpected token: ,2] > [Near : {... !(x in (1,2,3)) ....}] > {noformat} > Furthermore, as of Drools 7.29.0.Final, the following form will also fail to compile: > {noformat} > forall(Pojo(y==42, x in (1,2,3))) > {noformat} > with the following error: > {noformat} > Error Messages: > Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 > text=Unable to Analyse Expression !(y==42) || !(x in (1,2,3)): > [Error: unexpected token: ,2] > [Near : {... !(y==42) || !(x in (1,2,3)) ....}] > {noformat} > The latter is likely a consequence of the negation introduced by [DROOLS-4632], [DROOLS-4633] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4903) In constraints fail to compile if negated or inside a forall pattern

by Matteo Casalino (Jira)

[ https://issues.redhat.com/browse/DROOLS-4903?page=com.atlassian.jira.plug... ] Matteo Casalino updated DROOLS-4903: ------------------------------------ Description: It appears that the KieBuilder fails to compile the following pattern: {noformat} Pojo(!(x in (1,2,3))) {noformat} returning the following error: {noformat} Error Messages: Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 text=Unable to Analyse Expression !(x in (1,2,3)): [Error: unexpected token: ,2] [Near : {... !(x in (1,2,3)) ....}] {noformat} Furthermore, as of Drools 7.29.0.Final, the following form will also fail to compile: {noformat} forall(Pojo(y==42, x in (1,2,3))) {noformat} with the following error: {noformat} Error Messages: Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 text=Unable to Analyse Expression !(y==42) || !(x in (1,2,3)): [Error: unexpected token: ,2] [Near : {... !(y==42) || !(x in (1,2,3)) ....}] {noformat} The latter is likely a consequence of the negation introduced by [DROOLS-4632|https://issues.redhat.com/browse/DROOLS-4632], [DROOLS-4633][https://issues.redhat.com/browse/DROOLS-4633] was: It appears that the KieBuilder fails to compile the following pattern: {noformat} Pojo(!(x in (1,2,3))) {noformat} returning the following error: {noformat} Error Messages: Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 text=Unable to Analyse Expression !(x in (1,2,3)): [Error: unexpected token: ,2] [Near : {... !(x in (1,2,3)) ....}] {noformat} Furthermore, as of Drools 7.29.0.Final, the following form will also fail to compile: {noformat} forall(Pojo(y==42, x in (1,2,3))) {noformat} with the following error: {noformat} Error Messages: Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 text=Unable to Analyse Expression !(y==42) || !(x in (1,2,3)): [Error: unexpected token: ,2] [Near : {... !(y==42) || !(x in (1,2,3)) ....}] {noformat} The latter is likely a consequence of the negation introduced by [DROOLS-4632|https://issues.redhat.com/browse/DROOLS-4632] > In constraints fail to compile if negated or inside a forall pattern > -------------------------------------------------------------------- > > Key: DROOLS-4903 > URL: https://issues.redhat.com/browse/DROOLS-4903 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.31.0.Final > Reporter: Matteo Casalino > Assignee: Mario Fusco > Priority: Major > Attachments: in-constraint-negation.tgz > > > It appears that the KieBuilder fails to compile the following pattern: > {noformat} > Pojo(!(x in (1,2,3))) > {noformat} > returning the following error: > {noformat} > Error Messages: > Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 > text=Unable to Analyse Expression !(x in (1,2,3)): > [Error: unexpected token: ,2] > [Near : {... !(x in (1,2,3)) ....}] > {noformat} > Furthermore, as of Drools 7.29.0.Final, the following form will also fail to compile: > {noformat} > forall(Pojo(y==42, x in (1,2,3))) > {noformat} > with the following error: > {noformat} > Error Messages: > Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 > text=Unable to Analyse Expression !(y==42) || !(x in (1,2,3)): > [Error: unexpected token: ,2] > [Near : {... !(y==42) || !(x in (1,2,3)) ....}] > {noformat} > The latter is likely a consequence of the negation introduced by [DROOLS-4632|https://issues.redhat.com/browse/DROOLS-4632], [DROOLS-4633][https://issues.redhat.com/browse/DROOLS-4633] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4903) In constraints fail to compile if negated or inside a forall pattern

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4903?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-4903: -------------------------------- Sprint: 2020 Week 01-03 (from Dec 30) > In constraints fail to compile if negated or inside a forall pattern > -------------------------------------------------------------------- > > Key: DROOLS-4903 > URL: https://issues.redhat.com/browse/DROOLS-4903 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.31.0.Final > Reporter: Matteo Casalino > Assignee: Mario Fusco > Priority: Major > Attachments: in-constraint-negation.tgz > > > It appears that the KieBuilder fails to compile the following pattern: > {noformat} > Pojo(!(x in (1,2,3))) > {noformat} > returning the following error: > {noformat} > Error Messages: > Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 > text=Unable to Analyse Expression !(x in (1,2,3)): > [Error: unexpected token: ,2] > [Near : {... !(x in (1,2,3)) ....}] > {noformat} > Furthermore, as of Drools 7.29.0.Final, the following form will also fail to compile: > {noformat} > forall(Pojo(y==42, x in (1,2,3))) > {noformat} > with the following error: > {noformat} > Error Messages: > Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 > text=Unable to Analyse Expression !(y==42) || !(x in (1,2,3)): > [Error: unexpected token: ,2] > [Near : {... !(y==42) || !(x in (1,2,3)) ....}] > {noformat} > The latter is likely a consequence of the negation introduced by [DROOLS-4632|https://issues.redhat.com/browse/DROOLS-4632] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12931) Upgrade Undertow Schema to 11.0

by Flavia Rainone (Jira)

[ https://issues.redhat.com/browse/WFLY-12931?page=com.atlassian.jira.plugi... ] Flavia Rainone updated WFLY-12931: ---------------------------------- Component/s: Web (Undertow) > Upgrade Undertow Schema to 11.0 > ------------------------------- > > Key: WFLY-12931 > URL: https://issues.redhat.com/browse/WFLY-12931 > Project: WildFly > Issue Type: Task > Components: Web (Undertow) > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Major > > Upgrade the schema version to 11.0 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12933) Add documentation on the Undertow subsystem attributes

by Flavia Rainone (Jira)

[ https://issues.redhat.com/browse/WFLY-12933?page=com.atlassian.jira.plugi... ] Flavia Rainone updated WFLY-12933: ---------------------------------- Component/s: Documentation > Add documentation on the Undertow subsystem attributes > ------------------------------------------------------ > > Key: WFLY-12933 > URL: https://issues.redhat.com/browse/WFLY-12933 > Project: WildFly > Issue Type: Task > Components: Documentation > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Minor > > Currently the Admin Guide for Undertow subsystem does not have a list of the subsystem attributes. Add that to the documentation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12932) Test UndertowService config with subsystem attributes

by Flavia Rainone (Jira)

[ https://issues.redhat.com/browse/WFLY-12932?page=com.atlassian.jira.plugi... ] Flavia Rainone updated WFLY-12932: ---------------------------------- Component/s: Web (Undertow) > Test UndertowService config with subsystem attributes > ----------------------------------------------------- > > Key: WFLY-12932 > URL: https://issues.redhat.com/browse/WFLY-12932 > Project: WildFly > Issue Type: Task > Components: Web (Undertow) > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Minor > > Currently the tests dont verify if the Undertow config reflects in the correct configuration in UndertowService. Add that to the test suite. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12933) Add documentation on the Undertow subsystem attributes

by Flavia Rainone (Jira)

Flavia Rainone created WFLY-12933: ------------------------------------- Summary: Add documentation on the Undertow subsystem attributes Key: WFLY-12933 URL: https://issues.redhat.com/browse/WFLY-12933 Project: WildFly Issue Type: Task Reporter: Flavia Rainone Assignee: Flavia Rainone Currently the Admin Guide for Undertow subsystem does not have a list of the subsystem attributes. Add that to the documentation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12932) Test UndertowService config with subsystem attributes

by Flavia Rainone (Jira)

Flavia Rainone created WFLY-12932: ------------------------------------- Summary: Test UndertowService config with subsystem attributes Key: WFLY-12932 URL: https://issues.redhat.com/browse/WFLY-12932 Project: WildFly Issue Type: Task Reporter: Flavia Rainone Assignee: Flavia Rainone Currently the tests dont verify if the Undertow config reflects in the correct configuration in UndertowService. Add that to the test suite. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12931) Upgrade Undertow Schema to 11.0

by Flavia Rainone (Jira)

Flavia Rainone created WFLY-12931: ------------------------------------- Summary: Upgrade Undertow Schema to 11.0 Key: WFLY-12931 URL: https://issues.redhat.com/browse/WFLY-12931 Project: WildFly Issue Type: Task Reporter: Flavia Rainone Assignee: Flavia Rainone Upgrade the schema version to 11.0 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12926) Upgrade Infinispan to 9.4.18.Final

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-12926?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-12926: -------------------------------- Description: https://issues.redhat.com/projects/ISPN/versions/12343651 (was: https://github.com/infinispan/infinispan/compare/9.4.16.Final...9.4.x) > Upgrade Infinispan to 9.4.18.Final > ---------------------------------- > > Key: WFLY-12926 > URL: https://issues.redhat.com/browse/WFLY-12926 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System, Clustering > Affects Versions: 18.0.1.Final > Reporter: Chao Wang > Assignee: Paul Ferraro > Priority: Major > Labels: downstream_dependency > > https://issues.redhat.com/projects/ISPN/versions/12343651 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12926) Upgrade Infinispan to 9.4.18.Final

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-12926?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-12926: -------------------------------- Summary: Upgrade Infinispan to 9.4.18.Final (was: Upgrade Infinispan from 9.4.16.Final to 9.4.18.Final) > Upgrade Infinispan to 9.4.18.Final > ---------------------------------- > > Key: WFLY-12926 > URL: https://issues.redhat.com/browse/WFLY-12926 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System, Clustering > Affects Versions: 18.0.1.Final > Reporter: Chao Wang > Assignee: Paul Ferraro > Priority: Major > Labels: downstream_dependency > > https://github.com/infinispan/infinispan/compare/9.4.16.Final...9.4.x -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4790) Migrate deployment-scanner module to new MSC API

by Richard Opalka (Jira)

[ https://issues.redhat.com/browse/WFCORE-4790?page=com.atlassian.jira.plug... ] Richard Opalka updated WFCORE-4790: ----------------------------------- Summary: Migrate deployment-scanner module to new MSC API (was: Migrade deployment-scanner module to new MSC API) > Migrate deployment-scanner module to new MSC API > ------------------------------------------------ > > Key: WFCORE-4790 > URL: https://issues.redhat.com/browse/WFCORE-4790 > Project: WildFly Core > Issue Type: Task > Components: Deployment Scanner > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Major > Fix For: 11.0.0.Beta6 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4790) Migrade deployment-scanner module to new MSC API

by Richard Opalka (Jira)

Richard Opalka created WFCORE-4790: -------------------------------------- Summary: Migrade deployment-scanner module to new MSC API Key: WFCORE-4790 URL: https://issues.redhat.com/browse/WFCORE-4790 Project: WildFly Core Issue Type: Task Components: Deployment Scanner Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 11.0.0.Beta6 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12930) HttpSessionListener.sessionDestroyed event can deadlock if it attempts write operations on a session

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-12930: ----------------------------------- Summary: HttpSessionListener.sessionDestroyed event can deadlock if it attempts write operations on a session Key: WFLY-12930 URL: https://issues.redhat.com/browse/WFLY-12930 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 18.0.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Infinispan listeners are intentionally non-transactional - and thus should never attempt to perform cache writes. In order to trigger the requisite session listeners, session destroy events need to lookup the cache entries relevant to a given session via SessionFactory.findValue(..). However, if there are entries missing (e.g. a creation meta data entry w/out a access meta data entry), this method will attempt to purge the orphaned entries. This should never be done within the context of a session destroy event. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12929) HttpSessionListener.sessionDestroyed event can deadlock if it attempts write operations on a session

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-12929?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-12929: -------------------------------- Summary: HttpSessionListener.sessionDestroyed event can deadlock if it attempts write operations on a session (was: Session remove event can deadlock if it attempts write operations on a session) > HttpSessionListener.sessionDestroyed event can deadlock if it attempts write operations on a session > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-12929 > URL: https://issues.redhat.com/browse/WFLY-12929 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.1.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > Labels: downstream_dependency > > Infinispan listeners are intentionally non-transactional - and thus should never attempt to perform cache writes. > In order to trigger the requisite session listeners, session destroy events need to lookup the cache entries relevant to a given session via SessionFactory.findValue(..). However, if there are entries missing (e.g. a creation meta data entry w/out a access meta data entry), this method will attempt to purge the orphaned entries. This should never be done within the context of a session destroy event. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12929) Session remove event can deadlock if it attempts write operations on a session

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-12929?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-12929: -------------------------------- Description: Infinispan listeners are intentionally non-transactional - and thus should never attempt to perform cache writes. In order to trigger the requisite session listeners, session destroy events need to lookup the cache entries relevant to a given session via SessionFactory.findValue(..). However, if there are entries missing (e.g. a creation meta data entry w/out a access meta data entry), this method will attempt to purge the orphaned entries. This should never be done within the context of a session destroy event. was: Activation/passivation listeners are intentionally non-transactional - and thus should never attempt to perform cache writes. In order to trigger the requisite activation/passivation listeners, activation/passivation events need to lookup the cache entries relevant to a given session via SessionFactory.findValue(..). However, if there are entries missing (e.g. a creation meta data entry w/out a access meta data entry), this method will attempt to purge the orphaned entries. This should never be done within the context of an activation/passivation event. > Session remove event can deadlock if it attempts write operations on a session > ------------------------------------------------------------------------------ > > Key: WFLY-12929 > URL: https://issues.redhat.com/browse/WFLY-12929 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.1.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > Labels: downstream_dependency > > Infinispan listeners are intentionally non-transactional - and thus should never attempt to perform cache writes. > In order to trigger the requisite session listeners, session destroy events need to lookup the cache entries relevant to a given session via SessionFactory.findValue(..). However, if there are entries missing (e.g. a creation meta data entry w/out a access meta data entry), this method will attempt to purge the orphaned entries. This should never be done within the context of a session destroy event. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12929) Session remove event can deadlock if it attempts write operations on a session

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-12929?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-12929: -------------------------------- Affects Version/s: 18.0.1.Final (was: 18.0.0.Final) > Session remove event can deadlock if it attempts write operations on a session > ------------------------------------------------------------------------------ > > Key: WFLY-12929 > URL: https://issues.redhat.com/browse/WFLY-12929 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.1.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > Labels: downstream_dependency > > Activation/passivation listeners are intentionally non-transactional - and thus should never attempt to perform cache writes. > In order to trigger the requisite activation/passivation listeners, activation/passivation events need to lookup the cache entries relevant to a given session via SessionFactory.findValue(..). However, if there are entries missing (e.g. a creation meta data entry w/out a access meta data entry), this method will attempt to purge the orphaned entries. This should never be done within the context of an activation/passivation event. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12929) Session remove event can deadlock if it attempts write operations on a session

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-12929?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-12929: -------------------------------- Fix Version/s: (was: 19.0.0.Beta1) > Session remove event can deadlock if it attempts write operations on a session > ------------------------------------------------------------------------------ > > Key: WFLY-12929 > URL: https://issues.redhat.com/browse/WFLY-12929 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.1.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > Labels: downstream_dependency > > Activation/passivation listeners are intentionally non-transactional - and thus should never attempt to perform cache writes. > In order to trigger the requisite activation/passivation listeners, activation/passivation events need to lookup the cache entries relevant to a given session via SessionFactory.findValue(..). However, if there are entries missing (e.g. a creation meta data entry w/out a access meta data entry), this method will attempt to purge the orphaned entries. This should never be done within the context of an activation/passivation event. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12929) Session remove event can deadlock if it attempts write operations on a session

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-12929?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-12929: -------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/12705) > Session remove event can deadlock if it attempts write operations on a session > ------------------------------------------------------------------------------ > > Key: WFLY-12929 > URL: https://issues.redhat.com/browse/WFLY-12929 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.1.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > Labels: downstream_dependency > > Activation/passivation listeners are intentionally non-transactional - and thus should never attempt to perform cache writes. > In order to trigger the requisite activation/passivation listeners, activation/passivation events need to lookup the cache entries relevant to a given session via SessionFactory.findValue(..). However, if there are entries missing (e.g. a creation meta data entry w/out a access meta data entry), this method will attempt to purge the orphaned entries. This should never be done within the context of an activation/passivation event. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12929) Session remove event can deadlock if it attempts write operations on a session

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-12929: ----------------------------------- Summary: Session remove event can deadlock if it attempts write operations on a session Key: WFLY-12929 URL: https://issues.redhat.com/browse/WFLY-12929 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 18.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 19.0.0.Beta1 Activation/passivation listeners are intentionally non-transactional - and thus should never attempt to perform cache writes. In order to trigger the requisite activation/passivation listeners, activation/passivation events need to lookup the cache entries relevant to a given session via SessionFactory.findValue(..). However, if there are entries missing (e.g. a creation meta data entry w/out a access meta data entry), this method will attempt to purge the orphaned entries. This should never be done within the context of an activation/passivation event. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4789) Enable TLS 1.3 by default

by Farah Juma (Jira)

Farah Juma created WFCORE-4789: ---------------------------------- Summary: Enable TLS 1.3 by default Key: WFCORE-4789 URL: https://issues.redhat.com/browse/WFCORE-4789 Project: WildFly Core Issue Type: Feature Request Components: Security Reporter: Farah Juma WFCORE-4172 added support for TLS 1.3 but left TLS 1.3 disabled by default for reasons described in WFWIP-160: https://github.com/wildfly/wildfly-core/pull/3815/commits/4ee03bd5662b1fd... Once we are ready to do so, we should enable TLS 1.3 by default. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-1917) Enable TLS 1.3 by default

by Farah Juma (Jira)

Farah Juma created ELY-1917: ------------------------------- Summary: Enable TLS 1.3 by default Key: ELY-1917 URL: https://issues.redhat.com/browse/ELY-1917 Project: WildFly Elytron Issue Type: Feature Request Components: SSL Reporter: Farah Juma ELY-1706 added support for TLS 1.3 but left TLS 1.3 disabled by default for reasons described in WFWIP-160: https://github.com/wildfly-security/wildfly-elytron/pull/1295/commits/0f2... Once we are ready to do so, we should enable TLS 1.3 by default. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12915) Clean out unneeded provisioning boilerplate

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12915?page=com.atlassian.jira.plugi... ] Brian Stansberry resolved WFLY-12915. ------------------------------------- Resolution: Duplicate Issue > Clean out unneeded provisioning boilerplate > ------------------------------------------- > > Key: WFLY-12915 > URL: https://issues.redhat.com/browse/WFLY-12915 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > > The current Galleon versions should allow trimming quite a bit of boilerplate from all the places where we provision servers: > Alexey Loubyansky 5:07 PM > I did a bit more work on this, fixed a couple of issues and just released Galleon 4.2.1.Final and WFGP 4.2.1.Final > Alexey Loubyansky 5:07 PM > also opened a PR to upgrade WildFly Core to these releases https://github.com/wildfly/wildfly-core/pull/4025 > 5:08 PM > upgrading doesn't affect anything, except the bug fixes contained in those versions > 5:10 PM > however, for wildfly, i think we should use GAVs as feature-pack locations for feature-pack dependencies, in place of Galleon FPL > 5:11 PM > the benefit would be to avoid the universe resolver in maven builds > 5:11 PM > and also a simplified (mojo) provisioning config > Brian Stansberry 5:14 PM > good timing; I'm working on how to add a new f-p to wildfly (for microprofile stuff) so i should use best practices :) > Alexey Loubyansky 5:16 PM > by simplified provisioning config i mean that the selected block should be removed completely https://github.com/wildfly/wildfly/blob/master/build/pom.xml#L84-L97 > 5:16 PM > the only reason it is there is to avoid resolution from the universe > 5:17 PM > with GAVs for dependencies, it won't be necessary anymore > Brian Stansberry 5:17 PM > what about <inheritConfigs>false</inheritConfigs> ? > Alexey Loubyansky 5:18 PM > that was there to workaround a bug which was fixed in 4.2.0.Final > Brian Stansberry 5:18 PM > how about > 5:18 PM > <included-packages> > <name>docs.examples.configs</name> > </included-packages> > 5:19 PM > assuming that's not in the top level f-p > Alexey Loubyansky 5:19 PM > that should definitely stay, it's not in the selected block > 5:19 PM > ah, then you can have that > 5:20 PM > then there would be a real reason to mention the transitive dependency > 5:20 PM > i.e. you want something from it > Brian Stansberry 5:20 PM > could it be declared in the top level block, even though the package is in the transitive dep? > 5:20 PM > i'm going off on tangents, but first i should have said... > 5:21 PM > Nice! > Alexey Loubyansky 5:21 PM (EDITED) > unless the package is installed by default, it has to be included explicitly using transitive element > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1401) Avoid flushing pooled connections when matchManagedConnections returns no match

by Stephen Fikes (Jira)

[ https://issues.redhat.com/browse/JBJCA-1401?page=com.atlassian.jira.plugi... ] Stephen Fikes commented on JBJCA-1401: -------------------------------------- [~maeste], can you verify if there is a workaround to have pooling when using different credentials with a resource adapter? Would the workaround be to define different connection-definitions for each distinct credential? > Avoid flushing pooled connections when matchManagedConnections returns no match > ------------------------------------------------------------------------------- > > Key: JBJCA-1401 > URL: https://issues.redhat.com/browse/JBJCA-1401 > Project: IronJacamar > Issue Type: Feature Request > Components: Core > Affects Versions: 1.4.10 > Reporter: Stephen Fikes > Priority: Major > > When no match is returned by the resource adapter implementation of [ManagedConnectionFactory.matchManagedConnections|https://docs.oracle.com/...], the IronJacamar pool implementation [terminates non-matching connections|https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1...]. > There may be cases where resource adapters return {{null}} for cases where no connection matches but where the connections in the match set are not invalid though a different connection needs to be created based on the calling context ({{ConnectionRequestInfo}}). > A mechanism to avoid the termination of non-matching connections is needed to support such cases. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1048) Testcases - Kiali Validations sync-up

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1048?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan commented on SWSQE-1048: --------------------------------------- "MeshPolicy enabling mTLS is missing" is shown in fact "ServiceMeshPolicy enabling mTLS is missing" > Testcases - Kiali Validations sync-up > ------------------------------------- > > Key: SWSQE-1048 > URL: https://issues.redhat.com/browse/SWSQE-1048 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Sunil Kondkar > Priority: Major > > Sync up all validations from https://kiali.io/documentation/validations/ with Polarion estcases. > Make sure all validations have up-to-date testcases in Polarion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4903) In constraints fail to compile if negated or inside a forall pattern

by Matteo Casalino (Jira)

Matteo Casalino created DROOLS-4903: --------------------------------------- Summary: In constraints fail to compile if negated or inside a forall pattern Key: DROOLS-4903 URL: https://issues.redhat.com/browse/DROOLS-4903 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.31.0.Final Reporter: Matteo Casalino Assignee: Mario Fusco Attachments: in-constraint-negation.tgz It appears that the KieBuilder fails to compile the following pattern: {noformat} Pojo(!(x in (1,2,3))) {noformat} returning the following error: {noformat} Error Messages: Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 text=Unable to Analyse Expression !(x in (1,2,3)): [Error: unexpected token: ,2] [Near : {... !(x in (1,2,3)) ....}] {noformat} Furthermore, as of Drools 7.29.0.Final, the following form will also fail to compile: {noformat} forall(Pojo(y==42, x in (1,2,3))) {noformat} with the following error: {noformat} Error Messages: Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 text=Unable to Analyse Expression !(y==42) || !(x in (1,2,3)): [Error: unexpected token: ,2] [Near : {... !(y==42) || !(x in (1,2,3)) ....}] {noformat} The latter is likely a consequence of the negation introduced by [DROOLS-4632|https://issues.redhat.com/browse/DROOLS-4632] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-291) Log messages from io.smallrye.openapi don't have message ID

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFWIP-291?page=com.atlassian.jira.plugin... ] Paul Ferraro closed WFWIP-291. ------------------------------ Resolution: Rejected WildFly has no such requirement that debug or trace messages use i18n (and thus have a message ID). > Log messages from io.smallrye.openapi don't have message ID > ----------------------------------------------------------- > > Key: WFWIP-291 > URL: https://issues.redhat.com/browse/WFWIP-291 > Project: WildFly WIP > Issue Type: Bug > Components: MP OpenAPI > Reporter: Fabio Burzigotti > Assignee: Paul Ferraro > Priority: Major > > Messages logged by io.smallrye.openapi don't have assigned ID: > {code} > 2020-01-05 16:58:49,225 DEBUG [io.smallrye.openapi.runtime.util.SchemaFactory] (MSC service thread 1-4) Processing a single @Schema annotation. > 2020-01-05 16:58:49,225 DEBUG [io.smallrye.openapi.runtime.scanner.OpenApiAnnotationScanner] (MSC service thread 1-4) Processing a single @Response annotation. > 2020-01-05 16:58:49,225 DEBUG [io.smallrye.openapi.runtime.scanner.OpenApiAnnotationScanner] (MSC service thread 1-4) Processing jax-rs method: {0} > 2020-01-05 16:58:49,225 DEBUG [io.smallrye.openapi.runtime.scanner.OpenApiDataObjectScanner] (MSC service thread 1-4) Starting processing with root: java.lang.String > {code} > A search in SmallRye implementation seems to show that IDs are not used even when level is WARN: > {code} > $ find . -name '*.*' -type f -print0 | xargs -0 grep --color -n -e 'LOG.warn' > ./implementation/src/main/java/io/smallrye/openapi/runtime/scanner/ParameterProcessor.java:551: LOG.warnf("Matrix parameter references missing path segment: %s", segmentName); > ./implementation/src/main/java/io/smallrye/openapi/runtime/scanner/ParameterProcessor.java:1147: LOG.warnf("Value '%s' is not a valid %s default", stringValue, primitive.name().toLowerCase()); > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2429) MsgStats num_bytes_sent should be incremented by the Message::size

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2429?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2429: -------------------------------- [~dan.berindei] You're right > MsgStats num_bytes_sent should be incremented by the Message::size > ------------------------------------------------------------------ > > Key: JGRP-2429 > URL: https://issues.redhat.com/browse/JGRP-2429 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.1.8 > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Major > Fix For: 4.1.9 > > > MsgStats num_bytes_sent should be incremented by the Message::size > Today it is incremented by the Message:length that is the length of the payload, it doesn't include the headers. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1048) Testcases - Kiali Validations sync-up

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1048?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan commented on SWSQE-1048: --------------------------------------- "More than one Destination Rule for the same host subset combination" error text before was a different one. > Testcases - Kiali Validations sync-up > ------------------------------------- > > Key: SWSQE-1048 > URL: https://issues.redhat.com/browse/SWSQE-1048 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Sunil Kondkar > Priority: Major > > Sync up all validations from https://kiali.io/documentation/validations/ with Polarion estcases. > Make sure all validations have up-to-date testcases in Polarion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4788) Upgrade org.apache.httpcomponents:httpclient 4.5.10

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-4788?page=com.atlassian.jira.plug... ] Jeff Mesnil updated WFCORE-4788: -------------------------------- Component/s: Server (was: Test Suite) > Upgrade org.apache.httpcomponents:httpclient 4.5.10 > --------------------------------------------------- > > Key: WFCORE-4788 > URL: https://issues.redhat.com/browse/WFCORE-4788 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Server > Affects Versions: 11.0.0.Beta5 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4788) Upgrade org.apache.httpcomponents:httpclient 4.5.10

by Jeff Mesnil (Jira)

Jeff Mesnil created WFCORE-4788: ----------------------------------- Summary: Upgrade org.apache.httpcomponents:httpclient 4.5.10 Key: WFCORE-4788 URL: https://issues.redhat.com/browse/WFCORE-4788 Project: WildFly Core Issue Type: Component Upgrade Components: Test Suite Affects Versions: 11.0.0.Beta5 Reporter: Jeff Mesnil Assignee: Jeff Mesnil -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12486) Memory leak in OpenTracing when deployment is redeployed multiple times

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-12486?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet commented on WFLY-12486: ------------------------------------------ https://github.com/wildfly/wildfly/pull/12878 if https://github.com/wildfly/wildfly/pull/12836 doesn't make it to feature freeze. > Memory leak in OpenTracing when deployment is redeployed multiple times > ----------------------------------------------------------------------- > > Key: WFLY-12486 > URL: https://issues.redhat.com/browse/WFLY-12486 > Project: WildFly > Issue Type: Bug > Components: MP OpenTracing > Affects Versions: 17.0.0.Final, 17.0.1.Final, 18.0.1.Final > Reporter: Jan Stourac > Assignee: Emmanuel Hugonnet > Priority: Blocker > Attachments: memory-leak-bad.png, memory-leak-good.png, wildfly-thread-leak.png > > > There seems to be a memory leak when a deployment is redeployed multiple times (100 times in our test). This is very similar to what has been described in WFLY-10991. Also first commit this started to happen is [this one|https://github.com/wildfly/wildfly/commit/74170b5f49dd83f6b9ebd489f85...] - JaegerTracing and Apache Thrift dependencies update. Thus I selected MP OpenTracing component for this issue. > Test and deployment is same as is described in WFLY-10991. > Size of the extra heap in use is about 27MB plus when compared to the initial size before multiple redeploy operations. > I've tried to check manually via [visualVM|https://visualvm.github.io/] tool. Screenshot with suspicious jaegertracing instances are attached - there are much more jaegertracing class instances with new version of Jager Tracing and Apache Thrift dependencies, which is suspicious. > Interesting thing is that when microprofile-opentracing-smallrye subsystem is removed via: > {code} > /subsystem=microprofile-opentracing-smallrye:remove() > {code} > the memory leak is still present. This is kind of confusing to me. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4787) Fix or disable failing tests on IBM JDK

by Peter Mackay (Jira)

Peter Mackay created WFCORE-4787: ------------------------------------ Summary: Fix or disable failing tests on IBM JDK Key: WFCORE-4787 URL: https://issues.redhat.com/browse/WFCORE-4787 Project: WildFly Core Issue Type: Bug Components: Logging Reporter: Peter Mackay Assignee: Richard Opalka Fix For: 10.0.0.Beta3, 10.0.0.Final The following tests are failing on latest IBM JDK 8: --- # testsuite/standalone SilentModeTestCase # testsuite/manualmode CLIEmbedHostControllerTestCase CLIEmbedServerTestCase --- Tested on: --- java version "1.8.0_211" Java(TM) SE Runtime Environment (build 8.0.5.36 - pxa6480sr5fp36-20190510_01(SR5 FP36)) IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20190502_415899 (JIT enabled, AOT enabled) OpenJ9 - 46e57f9 OMR - 06a046a IBM - 0b909bf) JCL - 20190409_01 based on Oracle jdk8u211-b25 --- -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4786) Upgrade Jandex 2.1.2.Final

by Jeff Mesnil (Jira)

Jeff Mesnil created WFCORE-4786: ----------------------------------- Summary: Upgrade Jandex 2.1.2.Final Key: WFCORE-4786 URL: https://issues.redhat.com/browse/WFCORE-4786 Project: WildFly Core Issue Type: Component Upgrade Components: Server Affects Versions: 11.0.0.Beta5 Reporter: Jeff Mesnil Assignee: Jeff Mesnil -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3048) [DMN Designer] CellEditorControl needs to issue a new instance per use

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-3048?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-3048: -------------------------------- Attachment: applicationscope-vs-dependendscope.webm > [DMN Designer] CellEditorControl needs to issue a new instance per use > ---------------------------------------------------------------------- > > Key: DROOLS-3048 > URL: https://issues.redhat.com/browse/DROOLS-3048 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.12.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: applicationscope-vs-dependendscope.webm > > > A {{Popover}} used to edit a cell or column header (or any other DOM-based editor for that matter) disappears following a change in the widget that causes a {{Layer.draw()}} if the grid is sufficiently wide that there is a column not visible on screen. > All cells/columns that use {{CellEditorControls}} (containing, for example, the {{Popover}}) share a single instance from {{CellEditorControl}} and hence although the User makes a change in a visible column the invisible column (scrolled off screen) has its DOM resources destroyed that is the same instance as that for the visible column. > See https://github.com/kiegroup/appformer/blob/master/uberfire-extensions/ube.... If a column is not in the _body_ or _floating_ columns collection its DOM resources are destroyed. > I probably need to ensure different instances of {{CellEditorControl}} are created for each column/cell where we currently share the same instance. Also check for destruction of DOM elements in {{Document}} when grids/columns etc are destroyed. > h3. Acceptance criteria > # Create a DMN model > # Add a Decision > # Set its expression to a Decision Table > # Add multiple Input and Output columns so that the table is wider than the visible screen space (i.e. some columns are not rendered) > # Click on the header of a visible column > # The Name/Data-type popup should appear > # Repeat for expression type of Relation -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4902) Can not use mod operators (%) in when clause.

by xb l (Jira)

[ https://issues.redhat.com/browse/DROOLS-4902?page=com.atlassian.jira.plug... ] xb l updated DROOLS-4902: ------------------------- Summary: Can not use mod operators (%) in when clause. (was: Can not use mod operators (%) in when clouse.) > Can not use mod operators (%) in when clause. > --------------------------------------------- > > Key: DROOLS-4902 > URL: https://issues.redhat.com/browse/DROOLS-4902 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.31.0.Final > Reporter: xb l > Assignee: Mario Fusco > Priority: Major > > When I study drools , I write a rule use divide operator > {code:java} > rule "Buzz" salience 2 > when > $n: Number( this / 5 == 3 ) > then > System.out.println("Buzz"); > end > {code} > It's OK. > But: > {code:java} > rule "Buzz" salience 2 > when > $n: Number( this % 5 == 0 ) > then > System.out.println("Buzz"); > end > {code} > Report parser error: Unable to Analyse Expression this % 5 == 0: > The drools document mentioned the same example: > Person( age > 100 && ( age % 10 == 0 ) ) > % is Multiplicative operators, why parser error? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4902) Can not use mod operators (%) in when closures.

by xb l (Jira)

[ https://issues.redhat.com/browse/DROOLS-4902?page=com.atlassian.jira.plug... ] xb l updated DROOLS-4902: ------------------------- Description: When I study drools , I write a rule use divide operator {code:java} rule "Buzz" salience 2 when $n: Number( this / 5 == 3 ) then System.out.println("Buzz"); end {code} It's OK. But: {code:java} rule "Buzz" salience 2 when $n: Number( this % 5 == 0 ) then System.out.println("Buzz"); end {code} Report parser error: Unable to Analyse Expression this % 5 == 0: The drools document mentioned the same example: Person( age > 100 && ( age % 10 == 0 ) ) % is Multiplicative operators, why parser error? was: When I study drools , I write a rule use divide operator {code:java} rule "Buzz" salience 2 when $n: Number( this / 5 == 3 ) then System.out.println("Buzz"); end {code} It's OK. But: {code:java} rule "Buzz" salience 2 when $n: Number( this % 5 == 0 ) then System.out.println("Buzz"); end {code} Report parser error: Unable to Analyse Expression this % 5 == 0: > Can not use mod operators (%) in when closures. > ----------------------------------------------- > > Key: DROOLS-4902 > URL: https://issues.redhat.com/browse/DROOLS-4902 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.31.0.Final > Reporter: xb l > Assignee: Mario Fusco > Priority: Major > > When I study drools , I write a rule use divide operator > {code:java} > rule "Buzz" salience 2 > when > $n: Number( this / 5 == 3 ) > then > System.out.println("Buzz"); > end > {code} > It's OK. > But: > {code:java} > rule "Buzz" salience 2 > when > $n: Number( this % 5 == 0 ) > then > System.out.println("Buzz"); > end > {code} > Report parser error: Unable to Analyse Expression this % 5 == 0: > The drools document mentioned the same example: > Person( age > 100 && ( age % 10 == 0 ) ) > % is Multiplicative operators, why parser error? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4902) Can not use mod operators (%) in when clouse.

by xb l (Jira)

[ https://issues.redhat.com/browse/DROOLS-4902?page=com.atlassian.jira.plug... ] xb l updated DROOLS-4902: ------------------------- Summary: Can not use mod operators (%) in when clouse. (was: Can not use mod operators (%) in when closures.) > Can not use mod operators (%) in when clouse. > --------------------------------------------- > > Key: DROOLS-4902 > URL: https://issues.redhat.com/browse/DROOLS-4902 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.31.0.Final > Reporter: xb l > Assignee: Mario Fusco > Priority: Major > > When I study drools , I write a rule use divide operator > {code:java} > rule "Buzz" salience 2 > when > $n: Number( this / 5 == 3 ) > then > System.out.println("Buzz"); > end > {code} > It's OK. > But: > {code:java} > rule "Buzz" salience 2 > when > $n: Number( this % 5 == 0 ) > then > System.out.println("Buzz"); > end > {code} > Report parser error: Unable to Analyse Expression this % 5 == 0: > The drools document mentioned the same example: > Person( age > 100 && ( age % 10 == 0 ) ) > % is Multiplicative operators, why parser error? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1048) Testcases - Kiali Validations sync-up

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1048?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan reassigned SWSQE-1048: ------------------------------------- Assignee: Sunil Kondkar > Testcases - Kiali Validations sync-up > ------------------------------------- > > Key: SWSQE-1048 > URL: https://issues.redhat.com/browse/SWSQE-1048 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Sunil Kondkar > Priority: Major > > Sync up all validations from https://kiali.io/documentation/validations/ with Polarion estcases. > Make sure all validations have up-to-date testcases in Polarion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12913) Rationalize com.sum.xml.bind module dependencies

by Lin Gao (Jira)

[ https://issues.redhat.com/browse/WFLY-12913?page=com.atlassian.jira.plugi... ] Lin Gao commented on WFLY-12913: -------------------------------- +com.sun.istack+ comes from [istack-commons repository|https://github.com/eclipse-ee4j/jaxb-istack-commons/tree/maste...], which is different than the jaxb-ri one. The version is different as well. The version of +com.sun.istack+ used by WildFly is +3.0.7+, looks like we need to upgrade it as well together with jaxb-ri. > Rationalize com.sum.xml.bind module dependencies > ------------------------------------------------ > > Key: WFLY-12913 > URL: https://issues.redhat.com/browse/WFLY-12913 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate, REST, Web Services > Reporter: Brian Stansberry > Assignee: Lin Gao > Priority: Minor > > The com.sun.xml.bind module depends on and exports four other modules, and those modules in turn are private and have no other dependents: > {code} > <module name="com.github.relaxng" export="true" /> > <module name="com.sun.istack" export="true" /> > <module name="com.sun.xml.txw2" export="true" /> > <module name="com.sun.xsom" export="true" /> > {code} > Task is to: > 1) Write to wildfly-dev mail list to check for any projects that layer on WildFly that directly use these modules. > 2) Write to jboss-layered-products (internal Red Hat) mail list to check for any products based on WF/EAP that directly use these modules. > 3) Assuming no positive responses, make the artifacts from the above four modules direct artifacts of the com.sun.xml.bind module, add any needed module dependencies to con.sum.xml.bind, and get rid of those four modules. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12913) Rationalize com.sum.xml.bind module dependencies

by Lin Gao (Jira)

[ https://issues.redhat.com/browse/WFLY-12913?page=com.atlassian.jira.plugi... ] Lin Gao edited comment on WFLY-12913 at 1/6/20 5:38 AM: -------------------------------------------------------- +com.sun.istack+ comes from [istack-commons repository|https://github.com/eclipse-ee4j/jaxb-istack-commons/tree/maste...], which is different than the jaxb-ri one. The version is different as well. The version of +com.sun.istack+ used by WildFly is +3.0.7+, looks like we need to upgrade it as well(to 3.0.10) together with jaxb-ri. was (Author: gaol): +com.sun.istack+ comes from [istack-commons repository|https://github.com/eclipse-ee4j/jaxb-istack-commons/tree/maste...], which is different than the jaxb-ri one. The version is different as well. The version of +com.sun.istack+ used by WildFly is +3.0.7+, looks like we need to upgrade it as well together with jaxb-ri. > Rationalize com.sum.xml.bind module dependencies > ------------------------------------------------ > > Key: WFLY-12913 > URL: https://issues.redhat.com/browse/WFLY-12913 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate, REST, Web Services > Reporter: Brian Stansberry > Assignee: Lin Gao > Priority: Minor > > The com.sun.xml.bind module depends on and exports four other modules, and those modules in turn are private and have no other dependents: > {code} > <module name="com.github.relaxng" export="true" /> > <module name="com.sun.istack" export="true" /> > <module name="com.sun.xml.txw2" export="true" /> > <module name="com.sun.xsom" export="true" /> > {code} > Task is to: > 1) Write to wildfly-dev mail list to check for any projects that layer on WildFly that directly use these modules. > 2) Write to jboss-layered-products (internal Red Hat) mail list to check for any products based on WF/EAP that directly use these modules. > 3) Assuming no positive responses, make the artifacts from the above four modules direct artifacts of the com.sun.xml.bind module, add any needed module dependencies to con.sum.xml.bind, and get rid of those four modules. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2429) MsgStats num_bytes_sent should be incremented by the Message::size

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/JGRP-2429?page=com.atlassian.jira.plugin... ] Dan Berindei commented on JGRP-2429: ------------------------------------ [~belaban] is the fact that "number of bytes sent" means "number of payload bytes sent" documented anywhere? I'm pretty sure in {{doSend()}} {{length}} is the number of actual bytes sent, **not** the payload length. > MsgStats num_bytes_sent should be incremented by the Message::size > ------------------------------------------------------------------ > > Key: JGRP-2429 > URL: https://issues.redhat.com/browse/JGRP-2429 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.1.8 > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Major > Fix For: 4.1.9 > > > MsgStats num_bytes_sent should be incremented by the Message::size > Today it is incremented by the Message:length that is the length of the payload, it doesn't include the headers. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4902) Can not use mod operators (%) in when closures.

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4902?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-4902: -------------------------------- Sprint: 2020 Week 01-03 (from Dec 30) > Can not use mod operators (%) in when closures. > ----------------------------------------------- > > Key: DROOLS-4902 > URL: https://issues.redhat.com/browse/DROOLS-4902 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.31.0.Final > Reporter: xb l > Assignee: Mario Fusco > Priority: Major > > When I study drools , I write a rule use divide operator > {code:java} > rule "Buzz" salience 2 > when > $n: Number( this / 5 == 3 ) > then > System.out.println("Buzz"); > end > {code} > It's OK. > But: > {code:java} > rule "Buzz" salience 2 > when > $n: Number( this % 5 == 0 ) > then > System.out.println("Buzz"); > end > {code} > Report parser error: Unable to Analyse Expression this % 5 == 0: -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4785) PathAddress leaked on reload

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFCORE-4785?page=com.atlassian.jira.plug... ] Jean Francois Denise updated WFCORE-4785: ----------------------------------------- Attachment: after-reload.hprof > PathAddress leaked on reload > ---------------------------- > > Key: WFCORE-4785 > URL: https://issues.redhat.com/browse/WFCORE-4785 > Project: WildFly Core > Issue Type: Bug > Components: Management > Reporter: Jean Francois Denise > Assignee: Jeff Mesnil > Priority: Major > Attachments: after-reload.hprof, nominal.hprof, server.log, standalone-minimal2.xml > > > Boot server, connect CLI and reload. > As an example, the PathAddress [("core-service" => "management"),("management-interface" => "http-interface")] is leaked after the first reload (and only the first one, additional reloads don't create leak). > Attached heapdump, server.log and configuration used (reduced standalone.xml). > server.log contains traces of Instrumented PathAddress. Each created instance has an ID to track finalization. > server.log contains stacktrace of PathAddress allocation. > You will notice: > 0) Server starts and allocates 9 PathAddress for the management-interface=http-interface. > 1) GC occurs (forced from remote), 7 PathAddress are finalized. Instance 149 and 338 are not finalized. > 2) Reload occurs and allocates 9 new PathAddress for the management-interface=http-interface. > 3) GC occurs (forced from remote), 8 PathAddress are finalized. Instance 338 is Finalized but NOT instance 149. > 4) We have 3 remaining PathAddress 149, 600 and 789 > 5) Reload occurs and allocates 9 new PathAddress for the management-interface=http-interface. > 6) GC occurs (forced from remote), 9 PathAddress are finalized, we still have 149, new ones being 1029 and 1218. > So we have a leak of 1 PathAddress instance, instance 149. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4785) PathAddress leaked on reload

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFCORE-4785?page=com.atlassian.jira.plug... ] Jean Francois Denise updated WFCORE-4785: ----------------------------------------- Attachment: nominal.hprof > PathAddress leaked on reload > ---------------------------- > > Key: WFCORE-4785 > URL: https://issues.redhat.com/browse/WFCORE-4785 > Project: WildFly Core > Issue Type: Bug > Components: Management > Reporter: Jean Francois Denise > Assignee: Jeff Mesnil > Priority: Major > Attachments: after-reload.hprof, nominal.hprof, server.log, standalone-minimal2.xml > > > Boot server, connect CLI and reload. > As an example, the PathAddress [("core-service" => "management"),("management-interface" => "http-interface")] is leaked after the first reload (and only the first one, additional reloads don't create leak). > Attached heapdump, server.log and configuration used (reduced standalone.xml). > server.log contains traces of Instrumented PathAddress. Each created instance has an ID to track finalization. > server.log contains stacktrace of PathAddress allocation. > You will notice: > 0) Server starts and allocates 9 PathAddress for the management-interface=http-interface. > 1) GC occurs (forced from remote), 7 PathAddress are finalized. Instance 149 and 338 are not finalized. > 2) Reload occurs and allocates 9 new PathAddress for the management-interface=http-interface. > 3) GC occurs (forced from remote), 8 PathAddress are finalized. Instance 338 is Finalized but NOT instance 149. > 4) We have 3 remaining PathAddress 149, 600 and 789 > 5) Reload occurs and allocates 9 new PathAddress for the management-interface=http-interface. > 6) GC occurs (forced from remote), 9 PathAddress are finalized, we still have 149, new ones being 1029 and 1218. > So we have a leak of 1 PathAddress instance, instance 149. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4785) PathAddress leaked on reload

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFCORE-4785?page=com.atlassian.jira.plug... ] Jean Francois Denise updated WFCORE-4785: ----------------------------------------- Attachment: server.log > PathAddress leaked on reload > ---------------------------- > > Key: WFCORE-4785 > URL: https://issues.redhat.com/browse/WFCORE-4785 > Project: WildFly Core > Issue Type: Bug > Components: Management > Reporter: Jean Francois Denise > Assignee: Jeff Mesnil > Priority: Major > Attachments: after-reload.hprof, nominal.hprof, server.log, standalone-minimal2.xml > > > Boot server, connect CLI and reload. > As an example, the PathAddress [("core-service" => "management"),("management-interface" => "http-interface")] is leaked after the first reload (and only the first one, additional reloads don't create leak). > Attached heapdump, server.log and configuration used (reduced standalone.xml). > server.log contains traces of Instrumented PathAddress. Each created instance has an ID to track finalization. > server.log contains stacktrace of PathAddress allocation. > You will notice: > 0) Server starts and allocates 9 PathAddress for the management-interface=http-interface. > 1) GC occurs (forced from remote), 7 PathAddress are finalized. Instance 149 and 338 are not finalized. > 2) Reload occurs and allocates 9 new PathAddress for the management-interface=http-interface. > 3) GC occurs (forced from remote), 8 PathAddress are finalized. Instance 338 is Finalized but NOT instance 149. > 4) We have 3 remaining PathAddress 149, 600 and 789 > 5) Reload occurs and allocates 9 new PathAddress for the management-interface=http-interface. > 6) GC occurs (forced from remote), 9 PathAddress are finalized, we still have 149, new ones being 1029 and 1218. > So we have a leak of 1 PathAddress instance, instance 149. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4785) PathAddress leaked on reload

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFCORE-4785?page=com.atlassian.jira.plug... ] Jean Francois Denise updated WFCORE-4785: ----------------------------------------- Attachment: standalone-minimal2.xml > PathAddress leaked on reload > ---------------------------- > > Key: WFCORE-4785 > URL: https://issues.redhat.com/browse/WFCORE-4785 > Project: WildFly Core > Issue Type: Bug > Components: Management > Reporter: Jean Francois Denise > Assignee: Jeff Mesnil > Priority: Major > Attachments: after-reload.hprof, nominal.hprof, server.log, standalone-minimal2.xml > > > Boot server, connect CLI and reload. > As an example, the PathAddress [("core-service" => "management"),("management-interface" => "http-interface")] is leaked after the first reload (and only the first one, additional reloads don't create leak). > Attached heapdump, server.log and configuration used (reduced standalone.xml). > server.log contains traces of Instrumented PathAddress. Each created instance has an ID to track finalization. > server.log contains stacktrace of PathAddress allocation. > You will notice: > 0) Server starts and allocates 9 PathAddress for the management-interface=http-interface. > 1) GC occurs (forced from remote), 7 PathAddress are finalized. Instance 149 and 338 are not finalized. > 2) Reload occurs and allocates 9 new PathAddress for the management-interface=http-interface. > 3) GC occurs (forced from remote), 8 PathAddress are finalized. Instance 338 is Finalized but NOT instance 149. > 4) We have 3 remaining PathAddress 149, 600 and 789 > 5) Reload occurs and allocates 9 new PathAddress for the management-interface=http-interface. > 6) GC occurs (forced from remote), 9 PathAddress are finalized, we still have 149, new ones being 1029 and 1218. > So we have a leak of 1 PathAddress instance, instance 149. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4785) PathAddress leaked on reload

by Jean Francois Denise (Jira)

Jean Francois Denise created WFCORE-4785: -------------------------------------------- Summary: PathAddress leaked on reload Key: WFCORE-4785 URL: https://issues.redhat.com/browse/WFCORE-4785 Project: WildFly Core Issue Type: Bug Components: Management Reporter: Jean Francois Denise Assignee: Jeff Mesnil Boot server, connect CLI and reload. As an example, the PathAddress [("core-service" => "management"),("management-interface" => "http-interface")] is leaked after the first reload (and only the first one, additional reloads don't create leak). Attached heapdump, server.log and configuration used (reduced standalone.xml). server.log contains traces of Instrumented PathAddress. Each created instance has an ID to track finalization. server.log contains stacktrace of PathAddress allocation. You will notice: 0) Server starts and allocates 9 PathAddress for the management-interface=http-interface. 1) GC occurs (forced from remote), 7 PathAddress are finalized. Instance 149 and 338 are not finalized. 2) Reload occurs and allocates 9 new PathAddress for the management-interface=http-interface. 3) GC occurs (forced from remote), 8 PathAddress are finalized. Instance 338 is Finalized but NOT instance 149. 4) We have 3 remaining PathAddress 149, 600 and 789 5) Reload occurs and allocates 9 new PathAddress for the management-interface=http-interface. 6) GC occurs (forced from remote), 9 PathAddress are finalized, we still have 149, new ones being 1029 and 1218. So we have a leak of 1 PathAddress instance, instance 149. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12927) wildfly 8.2 huge memory allocation during and after deployement

by sandev sandev (Jira)

[ https://issues.redhat.com/browse/WFLY-12927?page=com.atlassian.jira.plugi... ] sandev sandev updated WFLY-12927: --------------------------------- Issue Type: Bug (was: Feature Request) > wildfly 8.2 huge memory allocation during and after deployement > --------------------------------------------------------------- > > Key: WFLY-12927 > URL: https://issues.redhat.com/browse/WFLY-12927 > Project: WildFly > Issue Type: Bug > Reporter: sandev sandev > Assignee: Brian Stansberry > Priority: Major > Attachments: threads.png > > > I am using wildfly 8.2.1 final to deploy java ee 7 maven web application wars about 30 war with dependence between them using rmi remote ejb. I found that the server consumes a lot of memory special on startup of the server to 8 g my java opt are -xms 8g -xmx 8g -metaspacesize 1g .so I use java "visualvm" to understand what is happening. I found that the most consumed memory is for 2 types of threads at deploy: MSC service thread and after deploy finish: DeployementScanner-threads in additional that no user use the server or the deployed application this server was just for test > my question is why wildfly starts with about 3g and after some time the memory growth to ~= 8g without any action on the server its idle any help to solve this problem please -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4779) Upgrade Woodstox from 5.0.3 to 6.0.3

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-4779?page=com.atlassian.jira.plug... ] Jeff Mesnil updated WFCORE-4779: -------------------------------- Component/s: Management (was: Build System) > Upgrade Woodstox from 5.0.3 to 6.0.3 > ------------------------------------ > > Key: WFCORE-4779 > URL: https://issues.redhat.com/browse/WFCORE-4779 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Management > Reporter: Ilia Vassilev > Assignee: Jeff Mesnil > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12927) wildfly 8.2 huge memory allocation during and after deployement

by sandev sandev (Jira)

[ https://issues.redhat.com/browse/WFLY-12927?page=com.atlassian.jira.plugi... ] sandev sandev updated WFLY-12927: --------------------------------- Attachment: threads.png > wildfly 8.2 huge memory allocation during and after deployement > --------------------------------------------------------------- > > Key: WFLY-12927 > URL: https://issues.redhat.com/browse/WFLY-12927 > Project: WildFly > Issue Type: Feature Request > Reporter: sandev sandev > Assignee: Brian Stansberry > Priority: Major > Attachments: threads.png > > > I am using wildfly 8.2.1 final to deploy java ee 7 maven web application wars about 30 war with dependence between them using rmi remote ejb. I found that the server consumes a lot of memory special on startup of the server to 8 g my java opt are -xms 8g -xmx 8g -metaspacesize 1g .so I use java "visualvm" to understand what is happening. I found that the most consumed memory is for 2 types of threads at deploy: MSC service thread and after deploy finish: DeployementScanner-threads in additional that no user use the server or the deployed application this server was just for test > my question is why wildfly starts with about 3g and after some time the memory growth to ~= 8g without any action on the server its idle any help to solve this problem please -- This message was sent by Atlassian Jira (v7.13.8#713008)

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