[JBoss JIRA] (WFWIP-23) [Artemis 2.x upgrade] Stuck messages in artemis.internal.sf.my-cluster... queue after restarting nodes in cluster
by Michal Toth (JIRA)
[ https://issues.jboss.org/browse/WFWIP-23?page=com.atlassian.jira.plugin.s... ]
Michal Toth commented on WFWIP-23:
----------------------------------
I am checking this one using EAP QE test suite again. Make it running 20 times.
My further tests shown error in our QE Core client, needing to handle Exception during failover.
This has been resolved.
> [Artemis 2.x upgrade] Stuck messages in artemis.internal.sf.my-cluster... queue after restarting nodes in cluster
> -----------------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-23
> URL: https://issues.jboss.org/browse/WFWIP-23
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis
> Reporter: Miroslav Novak
> Assignee: Jiri Ondrusek
> Priority: Blocker
> Labels: activemq, feature-branch-blocker
> Attachments: journal-node-2.txt
>
>
> There are lost messages in scenario where nodes in cluster are cleanly stopped and started again. This issue was hit with Artemis 2.5.0.Final and WF Jeff's integration branch WFLY-9407_upgrade_artemis_2.4.0_with_prefix.
> Test Scenario:
> * start two servers in cluster (JGroups used for discovery)
> * send messages to testQueue0 on node-1 and node-2
> * wait until consumers on both nodes receive 300 messages
> * cleanly shut down 1st and then 2nd server
> * leave servers shut down for one minute
> * start both servers
> * wait until both consumers receive 500 messages
> * stop sending messages and receive all remaining messages
> Pass Criteria: All send messages are received by consumer
> Actual Result: There are lost messages.
> Investigation:
> There are lost messages which were sent to 2nd node. However they got stuck in queue {{.artemis.internal.sf.my-cluster.8a7e9e98-2c36-11e8-9737-fa163ea20b26}} during load balancing to 1st server.
> I'm attaching trace logs from client and servers and content of journal from 2nd server.
> This is regression against Artemis 1.5.5 thus setting blocker priority.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2654) [DMN Designer] Automatically show (Name) edit control when adding new ContextEntries
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2654?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-2654:
-----------------------------------
Sprint: 2018 Week 25-26, 2018 Week 27-29 (was: 2018 Week 25-26)
> [DMN Designer] Automatically show (Name) edit control when adding new ContextEntries
> ------------------------------------------------------------------------------------
>
> Key: DROOLS-2654
> URL: https://issues.jboss.org/browse/DROOLS-2654
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Labels: UX, UXTeam
>
> When a new {{ContextEntry}} is added the User must double click on the {{Name}} cell to change the default value.
> [~tari_manga] suggested it would be good if the {{Name}} editor was automatically shown and focused when the User creates a new {{ContextEntry}}.
> h3. Manual Acceptance test
> For each column/row agreed in comments that should support this feature:
> - Append row/column, fill name, save reopen, check value stored
> - Append such row/column that could affect name in DRG, fill name, check DRG and rename there, check expression editor again
> - Try undo/redo after appending row/column
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2655) [DMN Designer]: Decision Table: Automatically create input columns for each InputData element
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2655?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-2655:
-----------------------------------
Sprint: 2018 Week 25-26, 2018 Week 27-29 (was: 2018 Week 25-26)
> [DMN Designer]: Decision Table: Automatically create input columns for each InputData element
> ---------------------------------------------------------------------------------------------
>
> Key: DROOLS-2655
> URL: https://issues.jboss.org/browse/DROOLS-2655
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> [~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}}/{{BusinessKnowledgeModel}} containing the {{DecisionTable}} expression. For example, if a BKM has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a BKM has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created.
> - For simple data types the input column names should correspond exactly to InputData elements.
> - For complex data types, we should use dot notation, e.g. Person.name, Person.salary ...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years