[JBoss JIRA] (JGRP-2327) UNICAST3: create receiver table when non-first message is received first
by Bela Ban (Jira)
[ https://issues.jboss.org/browse/JGRP-2327?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-2327:
--------------------------------
The first seqno for a new connection is always *1*.
> UNICAST3: create receiver table when non-first message is received first
> ------------------------------------------------------------------------
>
> Key: JGRP-2327
> URL: https://issues.jboss.org/browse/JGRP-2327
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Major
> Fix For: 4.1.4
>
>
> * A and B
> * B sends 2 messages to A: B1 and B2
> * A receives B2 _before_ B1 (both B1 and B2 are OOB)
> * The current code has A drop B2 and send a SEND_FIRST_SEQNO message to B
> * B resends B1, but _not_ B2
> * Retransmission needs to kick in before A receives B2. This might take up to {{xmit_interval * 2}} ms before B2 is retransmitted and delivered
> h4. Scenario (JGRP-2293):
> * A installs a new view
> * B sends a LEAVE-REQ to A (B is leaving, too) on the view installation and a VIEW-ACK for the view. Both messages are unicasts to A and OOB
> * The VIEW-ACK (B2) is received first and dropped, so it will have to be retransmitted
> * This delays the view installation, as A waits for {{view_ack_collection_timeout}} ms until it has received all VIEW-ACKs
> h4. Workaround
> * Set GMS.leave_timeout to a higher value (say 8000ms)
> h4. Solution
> * When B2 is received, and it is not the first message and we don't have a receiver table for B yet, investigate whether we can create the receiver table anyway
> * However, this requires the first seqno from B *to always be 0*
> --> Investigate whether the first seqno in UNICAST3 is always 0, then this solution will work
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-4084) Export to Excel for decision tables 7.5
by Toni Rikkola (Jira)
[ https://issues.jboss.org/browse/DROOLS-4084?page=com.atlassian.jira.plugi... ]
Toni Rikkola reassigned DROOLS-4084:
------------------------------------
Assignee: Toni Rikkola (was: Michael Anstis)
> Export to Excel for decision tables 7.5
> ---------------------------------------
>
> Key: DROOLS-4084
> URL: https://issues.jboss.org/browse/DROOLS-4084
> Project: Drools
> Issue Type: Epic
> Components: Guided Decision Table Editor
> Affects Versions: 7.23.0.Final
> Reporter: Jozef Marko
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
>
> This is a community epic for the BAPL-1169. The epic was created according to the [definition of done|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4o...] that advices what needs to be agreed before each feature implementation.
> h1. Requirement
> - As a user of the feature I want to convert guided decision table by single click to xls (Excel) format.
> - The converted table should have the same format as is supported for importing into business central.
> - The converted table should visually differentiate column and row types (constraint vs. action, metadata vs. data)
> - The conversion should support Simple GDT column
> - The conversion should support Brl GDT column
> - The conversion should support Attribute and Metadata columns
> - The converted table can be opened on Windows and Linux
> - The converted table split lines
> - The converted table support multibyte characters
> - The conversion of GDT graph is possible
> - User is prompted to save changes before conversion
> - Converted table is not stored in kie project, just downloaded via browser
> h1. UX design
> - Placement of the conversion button
> - Text of the conversion button
> - Dialog for case we support save changes before conversion
> h1. Documentation
> - Replace picture of GDT editor where they become obsolete
> - Comprehensive doc is probably not needed
> h1. Acceptance test
> - Convert table that
> -- Has more that 100 lines
> -- Has one Metadata column
> -- Has one Attribute column
> -- Has three constraint columns( two over same fact )
> -- Has three action columns( two over same fact )
> -- Has not all cells filled in
> -- Operates over String, Number, Boolean fields
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months