[JBoss JIRA] (WFLY-11064) Undelivered messages in remote jca topology after restart
by Miroslav Novak (JIRA)
Miroslav Novak created WFLY-11064:
-------------------------------------
Summary: Undelivered messages in remote jca topology after restart
Key: WFLY-11064
URL: https://issues.jboss.org/browse/WFLY-11064
Project: WildFly
Issue Type: Bug
Components: Clustering, JMS
Reporter: Miroslav Novak
Assignee: Martyn Taylor
Priority: Blocker
There are undelivered messages in scenario with where servers in remote JCA topology are restarted. There are undelivered message after test.
Test scenario:
* Start 2 server in Artemis cluster
* Start 2 servers with MDB connected to Artemis cluster
** MDB resends messages from InQueue to OutQueue from/to remote cluster
* Send messages to InQueue
* Restart all server (one by one)
* Consumes messages from OutQueue
Results:
After the test there are missing messages in OutQueue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (DROOLS-2788) UX to support selection of multiple data/domain object instances
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2788?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2788:
--------------------------------
Sprint: 2018 Week 33-35, 2018 Week 36-38 (was: 2018 Week 33-35, 2018 Week 36-38, 2018 Week 39-41)
> UX to support selection of multiple data/domain object instances
> ----------------------------------------------------------------
>
> Key: DROOLS-2788
> URL: https://issues.jboss.org/browse/DROOLS-2788
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: ScenarioSimulation, UX, UXTeam
> Attachments: Screen Shot 2018-07-24 at 2.22.20 PM.png, Screen Shot 2018-09-18 at 1.35.43 PM.png, Screen Shot 2018-09-19 at 11.44.07 AM.png, now-headers.png
>
>
> As a user I want to define multiple data/domain object instances per scenario (i.e. possible to have a scenario with more than one instance of “Person”), so that I can create a test scenario.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (DROOLS-3015) [DMN Designer] Prohibit parallel item definition edition
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3015?page=com.atlassian.jira.plugi... ]
Michael Anstis reassigned DROOLS-3015:
--------------------------------------
Assignee: Guilherme Carreiro (was: Michael Anstis)
> [DMN Designer] Prohibit parallel item definition edition
> --------------------------------------------------------
>
> Key: DROOLS-3015
> URL: https://issues.jboss.org/browse/DROOLS-3015
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.12.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: DMCommunity Challenge - March 2017.dmn, Screenshot from 2018-09-24 13-00-45.png
>
>
> We should prohibit parallel edit operation of item definitions in managa custom data type dialog. It brings troubles in different scenarios:
> h2. Save parent item
> # Open attached dmn model
> # Invoke manage custom data type dialog
> # Expand *tProfile* item
> # Click on edit next to *tProfile (Structure)*
> # Click on edit next to *Name (string)*
> # Change *Name* to *Name_updated*
> # Change *tProfile* to *tProfile_updated*
> # Click *Save* next *tProfile_updated*
> # Save button for *Name_updated* will disappear
> # Changes saved just for parent item *tProfile_updated*
> h2. Save referred items
> # Open attached dmn model
> # Invoke manage custom data type dialog
> # Click on edit next to *tGender (string)*
> # Click on edit next to *tGenders (tGender)*
> # Rename *tGender* to *tGender_updated*
> # Click *Save* next *tGender_updated*
> # The data type select box for *tGenders* will disappear, see
> ## !Screenshot from 2018-09-24 13-00-45.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (DROOLS-2877) Update the top level data type, considering changes in an external/nested sub data type
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2877?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2877:
--------------------------------
Description:
User is able to achieve inconsistent state in *Manage custom data type dialog* See the attached picture. There is changed top level itemDefinition *Address* to *Adress111* however the itemDefinition *Person* stil shows it address field as *Adress*, it should be *Adress111* too.
h2. Steps to reproduce
- Open the attached model
- Invoke manage custom data type dialog
- Change the Address item definition as shown in picture
-- Person item definition should update its fields
- Reopen the manage dialog
- Person will still have field of *Adress* type
- Click edito to this field
-- Nothing selected will be shown
-- It should select *Adress111*
h2. Acceptance test
- Steps to reproduce fixed (/)
- Change item definition that should affect multiple item definitions (/)
- Changing multiple item definititons in parallel is prohibited (x) DROOLS-3015
was:
User is able to achieve inconsistent state in *Manage custom data type dialog* See the attached picture. There is changed top level itemDefinition *Address* to *Adress111* however the itemDefinition *Person* stil shows it address field as *Adress*, it should be *Adress111* too.
h2. Steps to reproduce
- Open the attached model
- Invoke manage custom data type dialog
- Change the Address item definition as shown in picture
-- Person item definition should update its fields
- Reopen the manage dialog
- Person will still have field of *Adress* type
- Click edito to this field
-- Nothing selected will be shown
-- It should select *Adress111*
h2. Acceptance test
- Steps to reproduce fixed (/)
- Change item definition that should affect multiple item definitions (/)
- Changing multiple item definititons in parallel is prohibited (x)
> Update the top level data type, considering changes in an external/nested sub data type
> ---------------------------------------------------------------------------------------
>
> Key: DROOLS-2877
> URL: https://issues.jboss.org/browse/DROOLS-2877
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.11.0.Final
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: Screenshot from 2018-08-31 14-59-52.png, itemDef-dependency.dmn
>
>
> User is able to achieve inconsistent state in *Manage custom data type dialog* See the attached picture. There is changed top level itemDefinition *Address* to *Adress111* however the itemDefinition *Person* stil shows it address field as *Adress*, it should be *Adress111* too.
> h2. Steps to reproduce
> - Open the attached model
> - Invoke manage custom data type dialog
> - Change the Address item definition as shown in picture
> -- Person item definition should update its fields
> - Reopen the manage dialog
> - Person will still have field of *Adress* type
> - Click edito to this field
> -- Nothing selected will be shown
> -- It should select *Adress111*
> h2. Acceptance test
> - Steps to reproduce fixed (/)
> - Change item definition that should affect multiple item definitions (/)
> - Changing multiple item definititons in parallel is prohibited (x) DROOLS-3015
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months