January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1860) Verification reporting: Merge same messages in analysis report into one line

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1860?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-1860: --------------------------------- Labels: drools-tools verifier (was: drools-tools) > Verification reporting: Merge same messages in analysis report into one line > ---------------------------------------------------------------------------- > > Key: DROOLS-1860 > URL: https://issues.jboss.org/browse/DROOLS-1860 > Project: Drools > Issue Type: Sub-task > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.Beta5 > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools, verifier > > To keep the analysis report readable as much as possible, merge all messages with the same meaning and content (differ only in the row number) into single row in the analysis report panel. Currently are merged only "Empty Rules", "Missing Condition" and "Missing Action". -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1861) Verification reporting: Missing range explanation points to incorrect row

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1861?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-1861: --------------------------------- Labels: reported-by-qe verifier (was: reported-by-qe) > Verification reporting: Missing range explanation points to incorrect row > ------------------------------------------------------------------------- > > Key: DROOLS-1861 > URL: https://issues.jboss.org/browse/DROOLS-1861 > Project: Drools > Issue Type: Sub-task > Affects Versions: 7.0.0.Beta7 > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Labels: reported-by-qe, verifier > Fix For: 7.0.0.CR2 > > Attachments: Screenshot from 2017-03-22 09-20-28.png > > > When the table contains Missing Range Issue, then the explanation has incorrect row number. See the attached screenshot. There are correct affected rows, but incorrect row number in the explanation. > It is caused because in explanation is added 1: > https://github.com/kiegroup/drools-wb/blob/master/drools-wb-services/droo... > While there is correct row number already during issue creation: > https://github.com/kiegroup/drools-wb/blob/master/drools-wb-services/droo... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1859) Verification reporting: Consider Missing Conditions report as duplicate with Conflict/Subsumption

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1859?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-1859: --------------------------------- Labels: verifier (was: verification) > Verification reporting: Consider Missing Conditions report as duplicate with Conflict/Subsumption > ------------------------------------------------------------------------------------------------- > > Key: DROOLS-1859 > URL: https://issues.jboss.org/browse/DROOLS-1859 > Project: Drools > Issue Type: Sub-task > Components: Guided Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: verifier > > If a row is missing a condition in most cases it also either conflicts or is subsumptant with the other rows. This can quickly fill the reporting panel with Conflict issue reports. > To fix this it would be good to use a variable in V&V Preferences that blocks Conflict reporting when conditions are missing. This setting should be on by default, but the user can drown in his own issue reports and disable it when he wants. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3492) Create UX proposal to show/edit Test Scenario (Preview) global setting

by tao zhu (Jira)

[ https://issues.jboss.org/browse/DROOLS-3492?page=com.atlassian.jira.plugi... ] tao zhu updated DROOLS-3492: ---------------------------- Attachment: 11unnamed.png > Create UX proposal to show/edit Test Scenario (Preview) global setting > ---------------------------------------------------------------------- > > Key: DROOLS-3492 > URL: https://issues.jboss.org/browse/DROOLS-3492 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: tao zhu > Priority: Major > Labels: ScenarioSimulation, UXD, UXTeam > Attachments: 11unnamed.png > > > As user I want to be able to see/edit editor global settings. > For instance DMN file linked to the scenario or the Session name of a Rule scenario -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1859) Verification reporting: Consider Missing Conditions report as duplicate with Conflict/Subsumption

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1859?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-1859: --------------------------------- Labels: verification (was: ) > Verification reporting: Consider Missing Conditions report as duplicate with Conflict/Subsumption > ------------------------------------------------------------------------------------------------- > > Key: DROOLS-1859 > URL: https://issues.jboss.org/browse/DROOLS-1859 > Project: Drools > Issue Type: Sub-task > Components: Guided Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: verification > > If a row is missing a condition in most cases it also either conflicts or is subsumptant with the other rows. This can quickly fill the reporting panel with Conflict issue reports. > To fix this it would be good to use a variable in V&V Preferences that blocks Conflict reporting when conditions are missing. This setting should be on by default, but the user can drown in his own issue reports and disable it when he wants. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10723) Jboss AS 7.1 didn't read the deployment folders

by Bartosz Baranowski (Jira)

[ https://issues.jboss.org/browse/WFLY-10723?page=com.atlassian.jira.plugin... ] Bartosz Baranowski reassigned WFLY-10723: ----------------------------------------- Assignee: Bartosz Baranowski > Jboss AS 7.1 didn't read the deployment folders > ----------------------------------------------- > > Key: WFLY-10723 > URL: https://issues.jboss.org/browse/WFLY-10723 > Project: WildFly > Issue Type: Bug > Components: EE > Affects Versions: JBoss AS7 7.1.1.Final > Reporter: Veeresham Kardas > Assignee: Bartosz Baranowski > Priority: Minor > > I have an EAR deployed on Jboss AS 7.1.1.Final running on Solaris. When I started the jboss, it didn't picked up the deployements and no error in the log (boot.log and server.log). > The server.log on the day doesn't print that it looking for deployements and no log with > {code:java} > JBAS015874: JBoss AS 7.1.1.Final "Brontes" started > {code} > On a successful start day, the server.log is > {code:java} > 06:30:05,391 INFO [jacorb] JBAS016330: CORBA ORB Service started > 06:30:05,475 INFO [scanner] JBAS015012: Started FileSystemDeploymentService for directory /home/veeresh/apps/jboss-as-7.1.1.Final/standalone/deployments > 06:30:05,476 INFO [remoting] JBAS017100: Listening on localhost/127.0.0.1:20499 > 06:30:05,476 INFO [remoting] JBAS017100: Listening on tkjsbsvp1a/127.0.0.1:14947 > .... > .... > 06:30:06,319 INFO [as] JBAS015951: Admin console listening on http://127.0.0.1:20490 > 06:30:06,320 INFO [as] JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 3600ms - Started 262 of 344 services (78 services are passive or on-demand) > {code} > After waiting for 15 mins, the process was killed and re-started and it worked fine without any changes and issues. This happened only once and not able to re-produce -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10723) Jboss AS 7.1 didn't read the deployment folders

by Bartosz Baranowski (Jira)

[ https://issues.jboss.org/browse/WFLY-10723?page=com.atlassian.jira.plugin... ] Bartosz Baranowski resolved WFLY-10723. --------------------------------------- Resolution: Cannot Reproduce > Jboss AS 7.1 didn't read the deployment folders > ----------------------------------------------- > > Key: WFLY-10723 > URL: https://issues.jboss.org/browse/WFLY-10723 > Project: WildFly > Issue Type: Bug > Components: EE > Affects Versions: JBoss AS7 7.1.1.Final > Reporter: Veeresham Kardas > Assignee: Bartosz Baranowski > Priority: Minor > > I have an EAR deployed on Jboss AS 7.1.1.Final running on Solaris. When I started the jboss, it didn't picked up the deployements and no error in the log (boot.log and server.log). > The server.log on the day doesn't print that it looking for deployements and no log with > {code:java} > JBAS015874: JBoss AS 7.1.1.Final "Brontes" started > {code} > On a successful start day, the server.log is > {code:java} > 06:30:05,391 INFO [jacorb] JBAS016330: CORBA ORB Service started > 06:30:05,475 INFO [scanner] JBAS015012: Started FileSystemDeploymentService for directory /home/veeresh/apps/jboss-as-7.1.1.Final/standalone/deployments > 06:30:05,476 INFO [remoting] JBAS017100: Listening on localhost/127.0.0.1:20499 > 06:30:05,476 INFO [remoting] JBAS017100: Listening on tkjsbsvp1a/127.0.0.1:14947 > .... > .... > 06:30:06,319 INFO [as] JBAS015951: Admin console listening on http://127.0.0.1:20490 > 06:30:06,320 INFO [as] JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 3600ms - Started 262 of 344 services (78 services are passive or on-demand) > {code} > After waiting for 15 mins, the process was killed and re-started and it worked fine without any changes and issues. This happened only once and not able to re-produce -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3504) [DMN Designer] Move DragBoundsJSO to lienzo-tests

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3504?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3504: ------------------------------------- [~roger600] so it is fine with you, can I keep this task for me? > [DMN Designer] Move DragBoundsJSO to lienzo-tests > ------------------------------------------------- > > Key: DROOLS-3504 > URL: https://issues.jboss.org/browse/DROOLS-3504 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.17.0.Final > Reporter: Michael Anstis > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools > > JIRA DROOLS-3406 introduced {{DragBoundsJSO}} overrides the default settings of {{lienzo-tests}} in order for Unit Tests involving drag constraints to be written. [~roger600] requested that the change be added to {{lienzo-tests}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4267) dump-all-threads management operation forces explicit setting of locked-monitors and locked-syncrhonizers

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4267?page=com.atlassian.jira.plugi... ] Brian Stansberry edited comment on WFCORE-4267 at 1/10/19 6:53 PM: ------------------------------------------------------------------- Thanks, Jaikiran. ThreadMXBeanDumpAllThreadsHandler is quite old code and isn't using the AttributeDefinition object that provides the description data to also handle reading the param from the request. The AD has default value handling logic and the old code does not. So that's why setting the params is needed. That's a simple fix. Re: the text descriptions, they are booleans, and here's what the text should say: https://github.com/wildfly/wildfly-core/blob/master/platform-mbean/src/ma... -For some reason it looks like it's instead outputting the text for the operation reply: https://github.com/wildfly/wildfly-core/blob/master/platform-mbean/src/ma... That, I don't know why.- I know why; there's a different property that has the wrong text. was (Author: brian.stansberry): Thanks, Jaikiran. ThreadMXBeanDumpAllThreadsHandler is quite old code and isn't using the AttributeDefinition object that provides the description data to also handle reading the param from the request. The AD has default value handling logic and the old code does not. So that's why setting the params is needed. That's a simple fix. Re: the text descriptions, they are booleans, and here's what the text should say: https://github.com/wildfly/wildfly-core/blob/master/platform-mbean/src/ma... For some reason it looks like it's instead outputting the text for the operation reply: https://github.com/wildfly/wildfly-core/blob/master/platform-mbean/src/ma... That, I don't know why. > dump-all-threads management operation forces explicit setting of locked-monitors and locked-syncrhonizers > --------------------------------------------------------------------------------------------------------- > > Key: WFCORE-4267 > URL: https://issues.jboss.org/browse/WFCORE-4267 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 7.0.0.Final > Environment: WildFly server 15.0.0.Final > Reporter: jaikiran pai > Assignee: Jeff Mesnil > Priority: Major > > The {{dump-all-threads}} exposed by {{/core-service=platform-mbean/type=threading}} has this resource operation description: > {code} > .... > "request-properties" => { > "locked-monitors" => { > "type" => BOOLEAN, > "description" => "A list of detyped representations java.lang.management.MonitorInfo objects, each of w > hich represents an object monitor currently locked by the thread.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "default" => false > }, > "locked-synchronizers" => { > "type" => BOOLEAN, > "description" => "A list of detyped representations java.lang.management.LockInfo objects, each of whic > h represents an ownable synchronizer currently locked by the thread.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "default" => false > } > ... > {code} > The {{locked-monitors}} and {{locked-synchronizers}} both are mentioned as {{required=false}} and with default values. However, when I run this operation as follows on a (standalone) WildFly 15.0.0.Final instance: > {code} > /core-service=platform-mbean/type=threading:dump-all-threads > {code} > I get: > {code} > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0155: 'locked-synchronizers' may not be null", > "rolled-back" => true > } > {code} > when I then pass, locked-synchronizers explicitly as an attribute, it then complains about locked-monitors being absent. The only way to get past this is to specify both those attributes in the operation. > By the way, the description of those attributes isn't too clear, IMO. Is it saying that the attribute represents a "list of detyped representations ...." ? In which case the type of BOOLEAN for that attribute would be incorrect. Or does it mean that if set to true then a "list of detyped representations ...." will be returned? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4267) dump-all-threads management operation forces explicit setting of locked-monitors and locked-syncrhonizers

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4267?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-4267: ------------------------------------------ Thanks, Jaikiran. ThreadMXBeanDumpAllThreadsHandler is quite old code and isn't using the AttributeDefinition object that provides the description data to also handle reading the param from the request. The AD has default value handling logic and the old code does not. So that's why setting the params is needed. That's a simple fix. Re: the text descriptions, they are booleans, and here's what the text should say: https://github.com/wildfly/wildfly-core/blob/master/platform-mbean/src/ma... For some reason it looks like it's instead outputting the text for the operation reply: https://github.com/wildfly/wildfly-core/blob/master/platform-mbean/src/ma... That, I don't know why. > dump-all-threads management operation forces explicit setting of locked-monitors and locked-syncrhonizers > --------------------------------------------------------------------------------------------------------- > > Key: WFCORE-4267 > URL: https://issues.jboss.org/browse/WFCORE-4267 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 7.0.0.Final > Environment: WildFly server 15.0.0.Final > Reporter: jaikiran pai > Assignee: Jeff Mesnil > Priority: Major > > The {{dump-all-threads}} exposed by {{/core-service=platform-mbean/type=threading}} has this resource operation description: > {code} > .... > "request-properties" => { > "locked-monitors" => { > "type" => BOOLEAN, > "description" => "A list of detyped representations java.lang.management.MonitorInfo objects, each of w > hich represents an object monitor currently locked by the thread.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "default" => false > }, > "locked-synchronizers" => { > "type" => BOOLEAN, > "description" => "A list of detyped representations java.lang.management.LockInfo objects, each of whic > h represents an ownable synchronizer currently locked by the thread.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "default" => false > } > ... > {code} > The {{locked-monitors}} and {{locked-synchronizers}} both are mentioned as {{required=false}} and with default values. However, when I run this operation as follows on a (standalone) WildFly 15.0.0.Final instance: > {code} > /core-service=platform-mbean/type=threading:dump-all-threads > {code} > I get: > {code} > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0155: 'locked-synchronizers' may not be null", > "rolled-back" => true > } > {code} > when I then pass, locked-synchronizers explicitly as an attribute, it then complains about locked-monitors being absent. The only way to get past this is to specify both those attributes in the operation. > By the way, the description of those attributes isn't too clear, IMO. Is it saying that the attribute represents a "list of detyped representations ...." ? In which case the type of BOOLEAN for that attribute would be incorrect. Or does it mean that if set to true then a "list of detyped representations ...." will be returned? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 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 2019