July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-5037) Attributes of type Object with complex value types don't work if they are a map

by Kabir Khan (Jira)

[ https://issues.redhat.com/browse/WFCORE-5037?page=com.atlassian.jira.plug... ] Kabir Khan updated WFCORE-5037: ------------------------------- Summary: Attributes of type Object with complex value types don't work if they are a map (was: EJB Stats MBeans do not return method stats via JMX, but does via CLI) > Attributes of type Object with complex value types don't work if they are a map > ------------------------------------------------------------------------------- > > Key: WFCORE-5037 > URL: https://issues.redhat.com/browse/WFCORE-5037 > Project: WildFly Core > Issue Type: Bug > Components: JMX > Reporter: Kabir Khan > Priority: Major > > > This looks like a bug in that the JMX is not responding with the same as the CLI. > I am not sure if this is EJB subsystem issue or JMX or other. > Reproducer: > {code:java} > unzip -d $JBOSS_HOME/ reproducer-overlay.zip > ./bin/standalone.sh > ./run-test.sh {code} > > From JMX, it is not seeing an array under methods, it is returning CompositeDataSupport with 3 keys execution-time , invocations and wait-time all null. To match the CLI output, methods would need to return an another CompositeDataSupport where the key is the method name and its value is another CompositeDataSupport that has keys: execution-time , invocations and wait-time with the correct values. > > {code:java} > methods: javax.management.openmbean.CompositeDataSupport(compositeType=javax.management.openmbean.CompositeType(name=Complex type,items=((itemName=execution-time,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)),(itemName=invocations,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)),(itemName=wait-time,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)))),contents={execution-time=null, invocations=null, wait-time=null}) > methods.getCompositeType: javax.management.openmbean.CompositeType(name=Complex type,items=((itemName=execution-time,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)),(itemName=invocations,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)),(itemName=wait-time,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)))) > key: execution-time value: null > key: invocations value: null > key: wait-time value: null {code} > > {code:java} > [standalone@localhost:9990 /] /deployment=ejb-client.jar/subsystem=ejb3/stateless-session-bean=Hello:read-resource(recursive=true, include-runtime=true) > { > "outcome" => "success", > "result" => { > "component-class-name" => "Hello", > "declared-roles" => [], > "execution-time" => 5L, > "invocations" => 20L, > "methods" => { > "sayHello" => { > "execution-time" => 5L, > "invocations" => 10L, > "wait-time" => 36L > }, > "goodbye" => { > "execution-time" => 0L, > "invocations" => 10L, > "wait-time" => 3L > } > }, {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5037) EJB Stats MBeans do not return method stats via JMX, but does via CLI

by Kabir Khan (Jira)

[ https://issues.redhat.com/browse/WFCORE-5037?page=com.atlassian.jira.plug... ] Kabir Khan moved EAPSUP-205 to WFCORE-5037: ------------------------------------------- Project: WildFly Core (was: EAP Support) Key: WFCORE-5037 (was: EAPSUP-205) Issue Type: Bug (was: Question) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: JMX (was: EJB) (was: JMX) > EJB Stats MBeans do not return method stats via JMX, but does via CLI > --------------------------------------------------------------------- > > Key: WFCORE-5037 > URL: https://issues.redhat.com/browse/WFCORE-5037 > Project: WildFly Core > Issue Type: Bug > Components: JMX > Reporter: Kabir Khan > Priority: Major > > > This looks like a bug in that the JMX is not responding with the same as the CLI. > I am not sure if this is EJB subsystem issue or JMX or other. > Reproducer: > {code:java} > unzip -d $JBOSS_HOME/ reproducer-overlay.zip > ./bin/standalone.sh > ./run-test.sh {code} > > From JMX, it is not seeing an array under methods, it is returning CompositeDataSupport with 3 keys execution-time , invocations and wait-time all null. To match the CLI output, methods would need to return an another CompositeDataSupport where the key is the method name and its value is another CompositeDataSupport that has keys: execution-time , invocations and wait-time with the correct values. > > {code:java} > methods: javax.management.openmbean.CompositeDataSupport(compositeType=javax.management.openmbean.CompositeType(name=Complex type,items=((itemName=execution-time,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)),(itemName=invocations,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)),(itemName=wait-time,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)))),contents={execution-time=null, invocations=null, wait-time=null}) > methods.getCompositeType: javax.management.openmbean.CompositeType(name=Complex type,items=((itemName=execution-time,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)),(itemName=invocations,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)),(itemName=wait-time,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)))) > key: execution-time value: null > key: invocations value: null > key: wait-time value: null {code} > > {code:java} > [standalone@localhost:9990 /] /deployment=ejb-client.jar/subsystem=ejb3/stateless-session-bean=Hello:read-resource(recursive=true, include-runtime=true) > { > "outcome" => "success", > "result" => { > "component-class-name" => "Hello", > "declared-roles" => [], > "execution-time" => 5L, > "invocations" => 20L, > "methods" => { > "sayHello" => { > "execution-time" => 5L, > "invocations" => 10L, > "wait-time" => 36L > }, > "goodbye" => { > "execution-time" => 0L, > "invocations" => 10L, > "wait-time" => 3L > } > }, {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3084) [DMN Designer] Data Types - The expand/collapse feature is not keeping the state after a data type update

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-3084?page=com.atlassian.jira.plug... ] Guilherme Gomes closed DROOLS-3084. ----------------------------------- Resolution: Done > [DMN Designer] Data Types - The expand/collapse feature is not keeping the state after a data type update > --------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3084 > URL: https://issues.redhat.com/browse/DROOLS-3084 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Minor > Labels: drools-tools > Attachments: DROOLS-3084-steps.gif > > > The expand/collapse feature is not keeping the state after a data type update. See: > !DROOLS-3084-steps.gif|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4004) [DMN Designer] Included Models (7.5)

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4004?page=com.atlassian.jira.plug... ] Guilherme Gomes resolved DROOLS-4004. ------------------------------------- Resolution: Done > [DMN Designer] Included Models (7.5) > ------------------------------------ > > Key: DROOLS-4004 > URL: https://issues.redhat.com/browse/DROOLS-4004 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > This is an umbrella for all JIRAs (target to 7.5) related to the Included Models feature. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-866) Drools decision table with contains operator in a conditional group not working

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-866?page=com.atlassian.jira.plugi... ] Guilherme Gomes closed DROOLS-866. ---------------------------------- Resolution: Out of Date > Drools decision table with contains operator in a conditional group not working > ------------------------------------------------------------------------------- > > Key: DROOLS-866 > URL: https://issues.redhat.com/browse/DROOLS-866 > Project: Drools > Issue Type: Bug > Components: decision tables > Affects Versions: 6.2.0.Final > Environment: Windows 7 > Reporter: lucio piccoli > Assignee: Michael Anstis > Priority: Major > Attachments: FeePricing-grouping-error.xls, PricingRuleGroupingExample.java > > > I cannot get the Decision Table to using grouping in the expression. > Decision Table > ------------------------------------ > <row 10> CONDITION > <row 12> classList $param > expressions are in each row. > <row 43> (contains('AAA') || contains('BBB') ) && contains('CCC') <--fails to compile > <row 44> (contains('AAA') || contains('BBB') > <row 45> (contains('AA') || contains('BB') || contains('CCC') || contains('DDD') > where the fact classList is > List<String> classList = {'AAA', 'BB'.....} > the rule43 is meant to fire if the list contains either 'AAA' OR 'BBB' AND 'CCC' > however the decision table parser is failing with exception for rule 43 > [Error: Missing left node] > [Near : {... classList (contains("AAA") || contains("CCC")) ....}] > i have a similar rule working fine for other rows > <row 42> contains('AAA') || contains('BBB') || contains('CCC') > there seems to be something strange with using the contains operator in a group condition. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2008) Test Scenarios: Ability to fail a Guvnor Test Scenario if any unexpected rules are fired when the test scenario is executed

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-2008?page=com.atlassian.jira.plug... ] Guilherme Gomes closed DROOLS-2008. ----------------------------------- Resolution: Out of Date > Test Scenarios: Ability to fail a Guvnor Test Scenario if any unexpected rules are fired when the test scenario is executed > --------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2008 > URL: https://issues.redhat.com/browse/DROOLS-2008 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Andrea Lee > Assignee: Toni Rikkola > Priority: Minor > Labels: drools-tools > > Example scenario: > Existing Rules: Rule A, Rule B, Rule C. > Test Scenario expectation: Expect Rule A to fire once. > I would like to have the ability to specify that this Test Scenario should fail if any other rule in addition to Rule A is fired WITHOUT having to specify the following additional expectations: Expect Rule B to not fire, Expect Rule C to not fire. > I have posted this in the user mailing list as well: http://n3.nabble.com/Guvnor-Test-Scenario-Expectations-td722429.html#a722429 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-187) Wrong MIME Type in Guvnor User Guide

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-187?page=com.atlassian.jira.plugi... ] Guilherme Gomes closed DROOLS-187. ---------------------------------- Resolution: Out of Date > Wrong MIME Type in Guvnor User Guide > ------------------------------------ > > Key: DROOLS-187 > URL: https://issues.redhat.com/browse/DROOLS-187 > Project: Drools > Issue Type: Bug > Affects Versions: 6.0.0.Beta4 > Environment: All supported environments. > Reporter: Fernando Ribeiro > Assignee: Michael Anstis > Priority: Major > > In section 9.2.2, there are several occurrences of "plain/text" (wrong) instead of "text/plain" (right) which you may want to fix in the final version. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-470) Decision Table (XLS) should support fixed conditions, such as SeatDesignation(isNeighborOf($guest))

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-470?page=com.atlassian.jira.plugi... ] Guilherme Gomes closed DROOLS-470. ---------------------------------- Resolution: Out of Date > Decision Table (XLS) should support fixed conditions, such as SeatDesignation(isNeighborOf($guest)) > --------------------------------------------------------------------------------------------------- > > Key: DROOLS-470 > URL: https://issues.redhat.com/browse/DROOLS-470 > Project: Drools > Issue Type: Enhancement > Components: decision tables > Affects Versions: 6.1.0.Beta2 > Reporter: Geoffrey De Smet > Assignee: Michael Anstis > Priority: Major > Labels: optaplanner-request-for-drools > > This DT should work: > ||CONDITION||CONDITION||ACTION| > |$guest : SeatDesignation()|$neighbor : SeatDesignation(isNeighborOf($guest))|| > |guestName == "$param"|guestName == "$param"|doSomething();| > It crashes because of the "SeatDesignation(isNeighborOf($guest))". Only empty parenthesis are allowed. > Failing workaround 1: This workaround (as specified by the docs), does NOT work well, because it adds the same condition (isNeighborOf($guest)) multiple times in the same rule: > ||CONDITION||CONDITION||CONDITION||ACTION| > |$guest : SeatDesignation()|$neighbor : SeatDesignation()||| > |guestName == "$param"|isNeighborOf($guest), guestName == "$param"|isNeighborOf($guest), guestAge == "$param"|doSomething();| > Failing workaround 2: Adding an extra, hidden column with that condition does not work when new rows are added because condition columns with an empty cell are ignored. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-879) Support Drools Rule Template in KIE API

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-879?page=com.atlassian.jira.plugi... ] Guilherme Gomes closed DROOLS-879. ---------------------------------- Resolution: Out of Date > Support Drools Rule Template in KIE API > --------------------------------------- > > Key: DROOLS-879 > URL: https://issues.redhat.com/browse/DROOLS-879 > Project: Drools > Issue Type: Feature Request > Reporter: Mario Fusco > Assignee: Toni Rikkola > Priority: Major > > Drools Rule Template (.drt) are currently not supported with KIE API but only with legacy API as in this example: https://github.com/droolsjbpm/drools/blob/master/drools-examples/src/main... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-737) Ability to export zip or tarball of git repository

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-737?page=com.atlassian.jira.plugi... ] Guilherme Gomes closed DROOLS-737. ---------------------------------- Resolution: Out of Date > Ability to export zip or tarball of git repository > -------------------------------------------------- > > Key: DROOLS-737 > URL: https://issues.redhat.com/browse/DROOLS-737 > Project: Drools > Issue Type: Feature Request > Components: tools > Affects Versions: 6.2.0.Final > Reporter: William Decoste > Assignee: Toni Rikkola > Priority: Minor > > For users without or unable to use git -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2020