September 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3001) Add support to run value mapped to an entire DO

by Daniele Zonca (JIRA)

Daniele Zonca created DROOLS-3001: ------------------------------------- Summary: Add support to run value mapped to an entire DO Key: DROOLS-3001 URL: https://issues.jboss.org/browse/DROOLS-3001 Project: Drools Issue Type: Enhancement Components: Scenario Simulation and Testing Reporter: Daniele Zonca Assignee: Daniele Zonca Add the possibility into Scenario runner to have values mapped to an entire DO (for instance a String) without the need to specify a field -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-372) Use ServiceLoader to locate mod_cluster custom load metrics

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-372?page=com.atlassian.jira.plugin.s... ] Paul Ferraro commented on WFLY-372: ----------------------------------- I think we can close this. The ServiceLoader approach requires that discovered metrics be unconfigurable, which I think is quite limiting. Now that we support loading custom metrics from a configured module, I think this is sufficiently flexible for users. > Use ServiceLoader to locate mod_cluster custom load metrics > ----------------------------------------------------------- > > Key: WFLY-372 > URL: https://issues.jboss.org/browse/WFLY-372 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Solves the problem of having to identify load metrics by class names. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-372) Use ServiceLoader to locate mod_cluster custom load metrics

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-372?page=com.atlassian.jira.plugin.s... ] Paul Ferraro closed WFLY-372. ----------------------------- Resolution: Won't Do > Use ServiceLoader to locate mod_cluster custom load metrics > ----------------------------------------------------------- > > Key: WFLY-372 > URL: https://issues.jboss.org/browse/WFLY-372 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Solves the problem of having to identify load metrics by class names. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2921) [DMN Designer] Stack overflow when a Context has two Relations

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2921?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2921: -------------------------------- Description: Create a {{Context}} with two {{ContextEntries}}. Set both to be a {{Relation}}. Stack overflow :-( You can have multiple {{Relation}} in different {{Contexts}} it only happens when within the same {{Context}}. h2. Manual acceptance test - Top level context, multiple entries of different kinds (/) - Nested level context, multiple entries of different kinds (/) was: Create a {{Context}} with two {{ContextEntries}}. Set both to be a {{Relation}}. Stack overflow :-( You can have multiple {{Relation}} in different {{Contexts}} it only happens when within the same {{Context}}. h2. Manual acceptance test - Top level context, multiple entries of different kinds - Nested level context, multiple entries of different kinds > [DMN Designer] Stack overflow when a Context has two Relations > -------------------------------------------------------------- > > Key: DROOLS-2921 > URL: https://issues.jboss.org/browse/DROOLS-2921 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.10.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > > Create a {{Context}} with two {{ContextEntries}}. Set both to be a {{Relation}}. Stack overflow :-( > You can have multiple {{Relation}} in different {{Contexts}} it only happens when within the same {{Context}}. > h2. Manual acceptance test > - Top level context, multiple entries of different kinds (/) > - Nested level context, multiple entries of different kinds (/) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3000) UX: Add restrictions to data type from DMN decision tables.

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-3000?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3000: -------------------------------- Sprint: 2018 Week 33-35, 2018 Week 39-41 (was: 2018 Week 33-35, 2018 Week 42-44) > UX: Add restrictions to data type from DMN decision tables. > ----------------------------------------------------------- > > Key: DROOLS-3000 > URL: https://issues.jboss.org/browse/DROOLS-3000 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, Screen Shot 2018-08-24 at 8.38.37 AM.png, pop-overc.png, pop-overcSpecs.png, select.png > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions inline from a decision table (pop-over). > Functional considerations/ pre conditions: > * Required elements could be space intensive. > * If using the pop-over: Can implement a responsive HTML that looks good horizontally in the Data Type dialog.. and vertically in the popover. Although even if laid out horizontally in the DT dialog a big enum def will take up a lot of space text enums are ok, a textbox is good enough but a enum for a date/time field with >1 entry will start eating lots of room > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3000) UX: Add restrictions to data type from DMN decision tables.

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-3000?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3000: -------------------------------- Description: *Background* Persona: Business analyst or Rules practitioner Use Cases: * From the DMN canvas view - as a user I want to define data type restrictions inline from a decision table (pop-over). Functional considerations/ pre conditions: * Required elements could be space intensive. * If using the pop-over: Can implement a responsive HTML that looks good horizontally in the Data Type dialog.. and vertically in the popover. Although even if laid out horizontally in the DT dialog a big enum def will take up a lot of space text enums are ok, a textbox is good enough but a enum for a date/time field with >1 entry will start eating lots of room Verification conditions: * Scrum team and PO review. was: *Background* Persona: Business analyst or Rules practitioner Use Cases: * From the DMN canvas view - as a user I want to *select* a data type inline from a decision table. * Functional considerations/ pre conditions: * Actions will be offered or spawned inline within the cells of decision tables. * Design needs to be consistent with Stunner and PF components. Verification conditions: * Scrum team and PO review. Story Points: 5 (was: 3) Sprint: 2018 Week 33-35, 2018 Week 42-44 (was: 2018 Week 33-35) Summary: UX: Add restrictions to data type from DMN decision tables. (was: UX: Add restrictions to data type, inline, from DMN decision tables.) > UX: Add restrictions to data type from DMN decision tables. > ----------------------------------------------------------- > > Key: DROOLS-3000 > URL: https://issues.jboss.org/browse/DROOLS-3000 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, Screen Shot 2018-08-24 at 8.38.37 AM.png, pop-overc.png, pop-overcSpecs.png, select.png > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions inline from a decision table (pop-over). > Functional considerations/ pre conditions: > * Required elements could be space intensive. > * If using the pop-over: Can implement a responsive HTML that looks good horizontally in the Data Type dialog.. and vertically in the popover. Although even if laid out horizontally in the DT dialog a big enum def will take up a lot of space text enums are ok, a textbox is good enough but a enum for a date/time field with >1 entry will start eating lots of room > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3000) UX: Add restrictions to data type, inline, from DMN decision tables.

by Liz Clayton (JIRA)

Liz Clayton created DROOLS-3000: ----------------------------------- Summary: UX: Add restrictions to data type, inline, from DMN decision tables. Key: DROOLS-3000 URL: https://issues.jboss.org/browse/DROOLS-3000 Project: Drools Issue Type: Story Components: DMN Editor Reporter: Liz Clayton Assignee: Liz Clayton Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, Screen Shot 2018-08-24 at 8.38.37 AM.png, pop-overc.png, pop-overcSpecs.png, select.png *Background* Persona: Business analyst or Rules practitioner Use Cases: * From the DMN canvas view - as a user I want to *select* a data type inline from a decision table. * Functional considerations/ pre conditions: * Actions will be offered or spawned inline within the cells of decision tables. * Design needs to be consistent with Stunner and PF components. Verification conditions: * Scrum team and PO review. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2288) S3_PING: Under certain conditions, subclusters fail to merge after network partition

by Nick Sawadsky (JIRA)

[ https://issues.jboss.org/browse/JGRP-2288?page=com.atlassian.jira.plugin.... ] Nick Sawadsky commented on JGRP-2288: ------------------------------------- [~belaban] I noticed you tagged this for the next release of 4.0 and 3.6 -- thanks for that! I wanted to check when the next release of 3.6 containing this fix might be available. We have a customer who seems to be running into this with some regularity. > S3_PING: Under certain conditions, subclusters fail to merge after network partition > ------------------------------------------------------------------------------------ > > Key: JGRP-2288 > URL: https://issues.jboss.org/browse/JGRP-2288 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.15 > Reporter: Nick Sawadsky > Assignee: Bela Ban > Fix For: 3.6.16, 4.0.15 > > > Repro steps: > 1. Set up a cluster of four nodes, two on one machine (Host 1) and two on another (Host 2). Let's call the nodes A, B, C, and D. > 2. Configure all 4 nodes with S3_PING as the discovery mechanism. Set remove_all_files_on_view_change to true. > 3. Start up nodes in the order A, B, C, D. > 4. In the S3 bucket, there should be a single file with all four nodes listed. Node A should be flagged as the coordinator. Ensure that the UUID for node B is larger than the UUID for node C, when compared as two's complement integers. If this is not the case, shut down all nodes and restart in order. Repeat until the desired relationship is achieved. Note that with two's complement, a UUID having a first hex digit of 8 or higher is treated as negative for comparison purposes. So, for example, a UUID starting with 'a' is less than a UUID starting with 'b' which is less than a UUID starting with '1'. > 5. On Host 1, use iptables to block all traffic going to and coming from Host 2. > sudo iptables -A INPUT -s <Host 2 IP addr> -j DROP > sudo iptables -A OUTPUT -d <Host 2 IP addr> -j DROP > 6. Allow a few minutes for the nodes to detect the network partition. Eventually you should see two files in the S3 bucket. > 7. Using Ctrl-C, stop node A. > 8. You should soon find only a single file in the bucket, containing a single entry for node B. This is a result of the remove_all_files_on_view_change setting on S3_PING, which we set to true to avoid accumulation of old files in the bucket. > 9. Resolve the network partition: > sudo iptables -F OUTPUT > sudo iptables -F INPUT > 10. You will find that, even after many minutes, the subclusters are not merged. > I believe the reason why the subclusters are never merged is as follows: > - MERGE3 on nodes B, C and D uses S3_PING to find members to send INFO messages to. Each one finds only node B in the discovery file. As a result, only node B's view consistency checker has anything to work with. > - On node B, the consistency checker can see that there are two coordinators, B and C. However, node C has a lower UUID, so node B defers to it to perform the merge. Node C never performs the merge because, as mentioned above, it is not receiving any INFO messages. > I this this problem would affect FILE_PING as well, and other protocols derived from FILE_PING. Looking at the latest 4.x code, it appears the problem still exists there. > I think the crux of the issue is that the coordinator on Host 2 (node C) does not re-create its discovery file after it is deleted by node B. Would it be reasonable for FILE_PING.findMembers() to create the discovery file if the node is a coordinator and the file doesn't exist? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2999) [DMN Editor] UX to support the use of imported models

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2999?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2999: -------------------------------- Story Points: 5 Sprint: 2018 Week 39-41 > [DMN Editor] UX to support the use of imported models > ----------------------------------------------------- > > Key: DROOLS-2999 > URL: https://issues.jboss.org/browse/DROOLS-2999 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: reported-by-qe > > "Support use of 'imported' data-types". DMN supports referencing other DMN files and importing types from that into the diagram being authored. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2999) [DMN Editor] UX to support the use of imported models

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2999?page=com.atlassian.jira.plugi... ] Liz Clayton reassigned DROOLS-2999: ----------------------------------- Assignee: Liz Clayton (was: Michael Anstis) > [DMN Editor] UX to support the use of imported models > ----------------------------------------------------- > > Key: DROOLS-2999 > URL: https://issues.jboss.org/browse/DROOLS-2999 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: reported-by-qe > > "Support use of 'imported' data-types". DMN supports referencing other DMN files and importing types from that into the diagram being authored. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 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 September 2018