[JBoss JIRA] (JGRP-2249) CENTRAL_LOCK2: reconciliation protocol on coord change
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2249?page=com.atlassian.jira.plugin.... ]
Bela Ban resolved JGRP-2249.
----------------------------
Resolution: Done
Done, design doc is [1].
Next step is to think whether distributed conditions really make sense, unless we have distributed state, too. See my email below:
I'm implementing a new version of the locking protocol, CENTRAL_LOCK2, and am currently looking at conditions.
Since you're the author of the Condition part of the LockService...
Do you think distributed conditions make sense?
Usually, a condition is associated with some state, and the await()/signal() methods check/modify that state.
However, to be truly distributed, that state would have to be present in every member, and be changed in every member accordingly, too.
Do you assume these state changes (e.g. before a signal()) happen outside of the scope of the LockService, e.g. via messages/RPCs?
I'm think whether we should pull support for conditions, ie. Lock.newCondition() would throw an UnsupportedOperationException.
How do you guys handle this in the Infinispan locking service (Pedro)?
WDYT?
[1] https://github.com/belaban/JGroups/blob/master/doc/design/CENTRAL_LOCK2.txt
> CENTRAL_LOCK2: reconciliation protocol on coord change
> ------------------------------------------------------
>
> Key: JGRP-2249
> URL: https://issues.jboss.org/browse/JGRP-2249
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 4.0.13
>
>
> Implement a reconciliation protocol when the coord changes: instead of backing up all lock information to another member, the new coord asks all members for their current lock information (acquired locks, pending acquire and release requests) and constructs the lock table accordingly.
> This is described in https://issues.jboss.org/browse/JGRP-2234 (later comments).
> Comment from 2234:
> Clients need to have the following information:
> * Locks they acquired
> * Pending lock requests; locks which they want to acquire but for which they haven't yet received a LOCK_GRANTED response
> * Pending lock release requests; lock that have been released, but for which no RELEASE_LOCK_OK response has been received
> * Ditto for conditions, but we'll tackle them in a second stage
> The reconciliation protocol queues all new requests on the coord and asks all members for their lock information. Once the coord has received this information from all members, it applies this and then drains the queue of pending requests.
> It is important that the requests are ordered per member, ie. a release(L) cannot come before a lock(L).
> Since {{CENTRAL_LOCK}} allows for multiple members to hold the same lock in a split brain scenario, we need to think about how to handle merging where the coord detects that multiple members hold the same lock...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (DROOLS-2708) Icon for test results dock
by Brian Dellascio (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2708?page=com.atlassian.jira.plugi... ]
Brian Dellascio closed DROOLS-2708.
-----------------------------------
Release Notes Text: Made suggestion for FontAwesome icon + size in comments.
Resolution: Done
> Icon for test results dock
> --------------------------
>
> Key: DROOLS-2708
> URL: https://issues.jboss.org/browse/DROOLS-2708
> Project: Drools
> Issue Type: Sub-task
> Components: Scenario Simulation and Testing, Test Scenarios Editor
> Reporter: Liz Clayton
> Assignee: Brian Dellascio
> Labels: UX, UXTeam, VisualDesign
>
> As a practitioner I need to know which docked tab indicates the Scenario Test results panel within the test editor.
> Notes:
> Icon needed for the right panel dock (functions as a tab) - same behavior as all Process Designer docks. Additional details outlined in icon spreadsheet and parent jira.
> Reasonable icon concept could be something like the font awesome "play-circle" icon: https://fontawesome.com/cheatsheet?from=io
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (DROOLS-2708) Icon for test results dock
by Brian Dellascio (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2708?page=com.atlassian.jira.plugi... ]
Brian Dellascio commented on DROOLS-2708:
-----------------------------------------
Let's go ahead and use .fa-play-circle for that icon. I'd recommend the FontAwesome icons in that panel be sized at 14px.
Thanks,
Brian
> Icon for test results dock
> --------------------------
>
> Key: DROOLS-2708
> URL: https://issues.jboss.org/browse/DROOLS-2708
> Project: Drools
> Issue Type: Sub-task
> Components: Scenario Simulation and Testing, Test Scenarios Editor
> Reporter: Liz Clayton
> Assignee: Brian Dellascio
> Labels: UX, UXTeam, VisualDesign
>
> As a practitioner I need to know which docked tab indicates the Scenario Test results panel within the test editor.
> Notes:
> Icon needed for the right panel dock (functions as a tab) - same behavior as all Process Designer docks. Additional details outlined in icon spreadsheet and parent jira.
> Reasonable icon concept could be something like the font awesome "play-circle" icon: https://fontawesome.com/cheatsheet?from=io
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (WFCORE-3962) Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3962?page=com.atlassian.jira.plugi... ]
James Perkins commented on WFCORE-3962:
---------------------------------------
This would also have to be fixed in the {{ManagedServerBootCmdFactory}}.
> Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se
> -------------------------------------------------------------------------------
>
> Key: WFCORE-3962
> URL: https://issues.jboss.org/browse/WFCORE-3962
> Project: WildFly Core
> Issue Type: Bug
> Components: Modules
> Affects Versions: 6.0.0.Alpha3
> Reporter: Matej Novotny
> Assignee: David Lloyd
> Priority: Blocker
> Labels: Java11
>
> As per request, copying MODULES-372 to WFCORE as well.
> Starting WFLY with JDK 11 using {{standalone.sh}} yields:
> {code}
> org.jboss.modules.ModuleNotFoundException: java.se
> at org.jboss.modules.Module.addPaths(Module.java:1266)
> at org.jboss.modules.Module.link(Module.java:1622)
> at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650)
> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296)
> at org.jboss.modules.Main.main(Main.java:437)
> {code}
> Output of {{java -version}}:
> {code}
> openjdk version "11-ea" 2018-09-25
> OpenJDK Runtime Environment 18.9 (build 11-ea+21)
> OpenJDK 64-Bit Server VM 18.9 (build 11-ea+21, mixed mode)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (DROOLS-2708) Icon for test results dock
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2708?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2708:
--------------------------------
Labels: UX UXTeam VisualDesign (was: UX UXTeam)
> Icon for test results dock
> --------------------------
>
> Key: DROOLS-2708
> URL: https://issues.jboss.org/browse/DROOLS-2708
> Project: Drools
> Issue Type: Sub-task
> Components: Scenario Simulation and Testing, Test Scenarios Editor
> Reporter: Liz Clayton
> Assignee: Brian Dellascio
> Labels: UX, UXTeam, VisualDesign
>
> As a practitioner I need to know which docked tab indicates the Scenario Test results panel within the test editor.
> Notes:
> Icon needed for the right panel dock (functions as a tab) - same behavior as all Process Designer docks. Additional details outlined in icon spreadsheet and parent jira.
> Reasonable icon concept could be something like the font awesome "play-circle" icon: https://fontawesome.com/cheatsheet?from=io
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (DROOLS-2586) CSS/HTML for scenario simulation UX
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2586?page=com.atlassian.jira.plugi... ]
Liz Clayton closed DROOLS-2586.
-------------------------------
Resolution: Done
Work being covered in smaller jiras.
> CSS/HTML for scenario simulation UX
> -----------------------------------
>
> Key: DROOLS-2586
> URL: https://issues.jboss.org/browse/DROOLS-2586
> Project: Drools
> Issue Type: Task
> Reporter: Liz Clayton
> Assignee: Sarah Rambacher
> Labels: UX, UXTeam
> Attachments: Screen Shot 2018-06-05 at 3.44.15 PM.png
>
>
> As Aimee or Cameron I want to:
> * Easily create a test scenario template through the use of variable/data object placeholders so that I can create test scenarios against a single decision.
> * Define test scenarios through a UI so I can develop basic task scenarios with minimal engagement from IT.
> * Run a test scenario simulation so that I can verify the expected results against test simulation results.
> Verification conditions:
> Provide CSS/HTML to support wireframe designs which includes the following:
> * Overview (properties)
> * Scenario Template
> * Scenarios Input Screen
> * Results
> * Code View
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (DROOLS-2586) CSS/HTML for scenario simulation UX
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2586?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-2586:
-------------------------------------
[~srambach] I had created this as a general jira to offer heads-up, will close it out because we're dealing with specific issues in smaller jiras, such as https://issues.jboss.org/browse/DROOLS-2730
> CSS/HTML for scenario simulation UX
> -----------------------------------
>
> Key: DROOLS-2586
> URL: https://issues.jboss.org/browse/DROOLS-2586
> Project: Drools
> Issue Type: Task
> Reporter: Liz Clayton
> Assignee: Sarah Rambacher
> Labels: UX, UXTeam
> Attachments: Screen Shot 2018-06-05 at 3.44.15 PM.png
>
>
> As Aimee or Cameron I want to:
> * Easily create a test scenario template through the use of variable/data object placeholders so that I can create test scenarios against a single decision.
> * Define test scenarios through a UI so I can develop basic task scenarios with minimal engagement from IT.
> * Run a test scenario simulation so that I can verify the expected results against test simulation results.
> Verification conditions:
> Provide CSS/HTML to support wireframe designs which includes the following:
> * Overview (properties)
> * Scenario Template
> * Scenarios Input Screen
> * Results
> * Code View
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (DROOLS-2728) UX for custom data-types
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-2728:
-------------------------------------
[~tirelli] [~karreiro] [~manstis] Can I mark this as Done given the plan to use the http://www.patternfly.org/pattern-library/widgets/#treegrid-table?
> UX for custom data-types
> ------------------------
>
> Key: DROOLS-2728
> URL: https://issues.jboss.org/browse/DROOLS-2728
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-2700.png, Screen Shot 2018-07-13 at 11.26.43 AM.png, Screen Shot 2018-07-13 at 11.34.15 AM.png, nested.png, prop-panel.png
>
>
> As a practitioner I want to be able to:
> * select an existing data type
> * create a simple or structured data type
> * create a “compound” (or complex) data type, easily.
> *
expand/collapse views of compound data types, so that I can___
> *
navigate between levels in a compound data type, so that I can___
> * edit an existing data type
> * remove an existing data type
>
…so that I can use the data type when creating a decision related asset.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (DROOLS-2706) New "Scenario Test" asset list option (UX)
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2706?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-2706:
-------------------------------------
[~stetson.robinson] Should this task get handed over to [~g.dey18]?
> New "Scenario Test" asset list option (UX)
> ------------------------------------------
>
> Key: DROOLS-2706
> URL: https://issues.jboss.org/browse/DROOLS-2706
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Stetson Robinson
> Labels: UX, UXTeam
>
> As a practitioner - I want to be able to distinguish the new Scenario Test tool option, from the existing one, within the Asset list so that I can quickly/easily create a test using the new editor.
> *Verification conditions:*
> The new Scenario Test tool is distinguishable from the existing test tool within the asset list, through visual inspection by the user (no hover/click required.)
> Notes:
> Need a way to identify "experimental" tools from existing (to be deprecated?) tools. Solution might include distinct names for each, or parenthetical append (e.g. "experimental, beta, preview...) Or visual indicator, such as an icon, flag, etc.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months