[JBoss JIRA] (WFWIP-268) Specifying empty list of headers causes fatal error
by Darran Lofthouse (Jira)
[ https://issues.jboss.org/browse/WFWIP-268?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse resolved WFWIP-268.
------------------------------------
Resolution: Done
https://github.com/darranl/wildfly-core/commit/7b28a80f01617b8dd0f93e791b...
> Specifying empty list of headers causes fatal error
> ---------------------------------------------------
>
> Key: WFWIP-268
> URL: https://issues.jboss.org/browse/WFWIP-268
> Project: WildFly WIP
> Issue Type: Bug
> Components: Security
> Reporter: Tomas Terem
> Assignee: Darran Lofthouse
> Priority: Blocker
> Labels: management
>
> Specifying empty list of headers causes fatal error.
> {code:java}
> 17:15:30,603 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("management-interface" => "http-interface")
> ]) - failure description: "WFLYCTL0155: 'headers' may not be null"
> 17:15:30,604 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 17:15:30,614 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0050: WildFly Core 11.0.0.Beta3-SNAPSHOT stopped in 6ms
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4735) [DMN Designer] Grid performance is dire
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4735?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4735:
--------------------------------
Attachment: (was: drag-scroll.webm)
> [DMN Designer] Grid performance is dire
> ---------------------------------------
>
> Key: DROOLS-4735
> URL: https://issues.jboss.org/browse/DROOLS-4735
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.29.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
> Attachments: aTable.dmn, add-new-column.webm, cell-edit-mode.webm, delete-column.webm, dtable-500-rows.dmn, reorder-columns.webm, reorder-rows.webm, resized-column-save.webm, search-trough-grid.webm
>
>
> There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
> On closer inspection the following issues were found:
> - Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
> - Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
> h2. Manual Acceptance test
> Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
> h3. GDT
> - Merge view (/)
> - Pinned mode (/)
> - Change column width, save and reopen (/)
> - Search the table (/)
> - Scroll the table (/)
> - Edit the cell (/)
> - Reorder columns (/)
> - Reorder rows (/)
> h3. DMN decision table
> - Save and reopen (x) not able to save in reasonable time
> - Change column width (/)
> - Search the grid (/) [^search-trough-grid.webm]
> - Scroll the grid (/)
> - Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
> - Reorder rows (/) assuming performance of other actions and size of the table [^reorder-rows.webm]
> - Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
> - Removing column (/) fine, acceptable ignoring time of showing menu reported above [^delete-column.webm]
> - Edit the cell (x) invoking the edit mode by double click is very slow, by keyboard it is fine [^cell-edit-mode.webm]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4735) [DMN Designer] Grid performance is dire
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4735?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4735:
--------------------------------
Attachment: (was: resize-column.webm)
> [DMN Designer] Grid performance is dire
> ---------------------------------------
>
> Key: DROOLS-4735
> URL: https://issues.jboss.org/browse/DROOLS-4735
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.29.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
> Attachments: aTable.dmn, add-new-column.webm, cell-edit-mode.webm, delete-column.webm, drag-scroll.webm, dtable-500-rows.dmn, reorder-columns.webm, reorder-rows.webm, resized-column-save.webm, search-trough-grid.webm
>
>
> There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
> On closer inspection the following issues were found:
> - Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
> - Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
> h2. Manual Acceptance test
> Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
> h3. GDT
> - Merge view (/)
> - Pinned mode (/)
> - Change column width, save and reopen (/)
> - Search the table (/)
> - Scroll the table (/)
> - Edit the cell (/)
> - Reorder columns (/)
> - Reorder rows (/)
> h3. DMN decision table
> - Save and reopen (x) not able to save in reasonable time
> - Change column width (/)
> - Search the grid (/) [^search-trough-grid.webm]
> - Scroll the grid (?) scrolling seems working in reasonable time assuming number of rows, however dragging canvas is slower [^drag-scroll.webm]
> - Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
> - Reorder rows (/) assuming performance of other actions and size of the table [^reorder-rows.webm]
> - Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
> - Removing column (/) fine, acceptable ignoring time of showing menu reported above [^delete-column.webm]
> - Edit the cell (x) invoking the edit mode by double click is very slow, by keyboard it is fine [^cell-edit-mode.webm]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4735) [DMN Designer] Grid performance is dire
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4735?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4735:
--------------------------------
Description:
There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
On closer inspection the following issues were found:
- Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
- Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
h2. Manual Acceptance test
Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
h3. GDT
- Merge view (/)
- Pinned mode (/)
- Change column width, save and reopen (/)
- Search the table (/)
- Scroll the table (/)
- Edit the cell (/)
- Reorder columns (/)
- Reorder rows (/)
h3. DMN decision table
- Save and reopen (x) not able to save in reasonable time
- Change column width (/)
- Search the grid (/) [^search-trough-grid.webm]
- Scroll the grid (/)
- Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
- Reorder rows (/) assuming performance of other actions and size of the table [^reorder-rows.webm]
- Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
- Removing column (/) fine, acceptable ignoring time of showing menu reported above [^delete-column.webm]
- Edit the cell (x) invoking the edit mode by double click is very slow, by keyboard it is fine [^cell-edit-mode.webm]
was:
There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
On closer inspection the following issues were found:
- Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
- Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
h2. Manual Acceptance test
Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
h3. GDT
- Merge view (/)
- Pinned mode (/)
- Change column width, save and reopen (/)
- Search the table (/)
- Scroll the table (/)
- Edit the cell (/)
- Reorder columns (/)
- Reorder rows (/)
h3. DMN decision table
- Save and reopen (x) not able to save in reasonable time
- Change column width (/)
- Search the grid (/) [^search-trough-grid.webm]
- Scroll the grid (?) scrolling seems working in reasonable time assuming number of rows, however dragging canvas is slower [^drag-scroll.webm]
- Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
- Reorder rows (/) assuming performance of other actions and size of the table [^reorder-rows.webm]
- Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
- Removing column (/) fine, acceptable ignoring time of showing menu reported above [^delete-column.webm]
- Edit the cell (x) invoking the edit mode by double click is very slow, by keyboard it is fine [^cell-edit-mode.webm]
> [DMN Designer] Grid performance is dire
> ---------------------------------------
>
> Key: DROOLS-4735
> URL: https://issues.jboss.org/browse/DROOLS-4735
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.29.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
> Attachments: aTable.dmn, add-new-column.webm, cell-edit-mode.webm, delete-column.webm, drag-scroll.webm, dtable-500-rows.dmn, reorder-columns.webm, reorder-rows.webm, resized-column-save.webm, search-trough-grid.webm
>
>
> There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
> On closer inspection the following issues were found:
> - Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
> - Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
> h2. Manual Acceptance test
> Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
> h3. GDT
> - Merge view (/)
> - Pinned mode (/)
> - Change column width, save and reopen (/)
> - Search the table (/)
> - Scroll the table (/)
> - Edit the cell (/)
> - Reorder columns (/)
> - Reorder rows (/)
> h3. DMN decision table
> - Save and reopen (x) not able to save in reasonable time
> - Change column width (/)
> - Search the grid (/) [^search-trough-grid.webm]
> - Scroll the grid (/)
> - Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
> - Reorder rows (/) assuming performance of other actions and size of the table [^reorder-rows.webm]
> - Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
> - Removing column (/) fine, acceptable ignoring time of showing menu reported above [^delete-column.webm]
> - Edit the cell (x) invoking the edit mode by double click is very slow, by keyboard it is fine [^cell-edit-mode.webm]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4735) [DMN Designer] Grid performance is dire
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4735?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4735:
--------------------------------
Description:
There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
On closer inspection the following issues were found:
- Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
- Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
h2. Manual Acceptance test
Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
h3. GDT
- Merge view (/)
- Pinned mode (/)
- Change column width, save and reopen (/)
- Search the table (/)
- Scroll the table (/)
- Edit the cell (/)
- Reorder columns (/)
- Reorder rows (/)
h3. DMN decision table
- Save and reopen (x) not able to save in reasonable time
- Change column width (/)
- Search the grid (/) [^search-trough-grid.webm]
- Scroll the grid (?) scrolling seems working in reasonable time assuming number of rows, however dragging canvas is slower [^drag-scroll.webm]
- Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
- Reorder rows (/) assuming performance of other actions and size of the table [^reorder-rows.webm]
- Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
- Removing column (/) fine, acceptable ignoring time of showing menu reported above [^delete-column.webm]
- Edit the cell (x) invoking the edit mode by double click is very slow, by keyboard it is fine [^cell-edit-mode.webm]
was:
There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
On closer inspection the following issues were found:
- Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
- Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
h2. Manual Acceptance test
Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
h3. GDT
- Merge view (/)
- Pinned mode (/)
- Change column width, save and reopen (/)
- Search the table (/)
- Scroll the table (/)
- Edit the cell (/)
- Reorder columns (/)
- Reorder rows (/)
h3. DMN decision table
- Change column width, save and reopen (x) [^resize-column.webm] [^resized-column-save.webm]
- Search the grid (/) [^search-trough-grid.webm]
- Scroll the grid (?) scrolling seems working in reasonable time assuming number of rows, however dragging canvas is slower [^drag-scroll.webm]
- Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
- Reorder rows (/) assuming performance of other actions and size of the table [^reorder-rows.webm]
- Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
- Removing column (/) fine, acceptable ignoring time of showing menu reported above [^delete-column.webm]
- Edit the cell (x) invoking the edit mode by double click is very slow, by keyboard it is fine [^cell-edit-mode.webm]
> [DMN Designer] Grid performance is dire
> ---------------------------------------
>
> Key: DROOLS-4735
> URL: https://issues.jboss.org/browse/DROOLS-4735
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.29.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
> Attachments: aTable.dmn, add-new-column.webm, cell-edit-mode.webm, delete-column.webm, drag-scroll.webm, dtable-500-rows.dmn, reorder-columns.webm, reorder-rows.webm, resize-column.webm, resized-column-save.webm, search-trough-grid.webm
>
>
> There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
> On closer inspection the following issues were found:
> - Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
> - Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
> h2. Manual Acceptance test
> Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
> h3. GDT
> - Merge view (/)
> - Pinned mode (/)
> - Change column width, save and reopen (/)
> - Search the table (/)
> - Scroll the table (/)
> - Edit the cell (/)
> - Reorder columns (/)
> - Reorder rows (/)
> h3. DMN decision table
> - Save and reopen (x) not able to save in reasonable time
> - Change column width (/)
> - Search the grid (/) [^search-trough-grid.webm]
> - Scroll the grid (?) scrolling seems working in reasonable time assuming number of rows, however dragging canvas is slower [^drag-scroll.webm]
> - Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
> - Reorder rows (/) assuming performance of other actions and size of the table [^reorder-rows.webm]
> - Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
> - Removing column (/) fine, acceptable ignoring time of showing menu reported above [^delete-column.webm]
> - Edit the cell (x) invoking the edit mode by double click is very slow, by keyboard it is fine [^cell-edit-mode.webm]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFLY-12806) Upgrade to Wildfly 17, can't find persistence unit
by Emilio Cuberos (Jira)
[ https://issues.jboss.org/browse/WFLY-12806?page=com.atlassian.jira.plugin... ]
Emilio Cuberos updated WFLY-12806:
----------------------------------
Issue Type: Bug (was: Feature Request)
> Upgrade to Wildfly 17, can't find persistence unit
> --------------------------------------------------
>
> Key: WFLY-12806
> URL: https://issues.jboss.org/browse/WFLY-12806
> Project: WildFly
> Issue Type: Bug
> Reporter: Emilio Cuberos
> Assignee: Brian Stansberry
> Priority: Major
> Attachments: persistence.xml
>
>
> Hi,
> Could you give us some advice? We upgraded from Java 8 / Wildfly 10, to Java 11 and Wildfly 17.
> Now the persistence units (attached persistence.xml) are no longer found:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: WFLYWELD0037: Error injecting persistence unit into CDI managed bean. Can't find a persistence unit named 'healthtrender-core' in deployment healthtrender-cloud-1.0.0.war for injection point private javax.persistence.EntityManager com.hemocue.cloud.repository.UserProfileRepository.em"}}
> {code}
> Here is an example of class where we inject a persistence-unit called "healthtrender-core" which is present in the persistence.xml:
> {code:java}
> package com.hemocue.cloud.repository;
> import com.hemocue.cloud.entity.user.Program;
> import javax.enterprise.context.Dependent;
> import javax.persistence.EntityManager;
> import javax.persistence.PersistenceContext;
> /**
> *
> * @author Ivar Grimstad (ivar.grimstad(a)gmail.com)
> */
> @Dependent
> public class ProgramRepository extends AbstractRepository<Program> {
> @PersistenceContext(unitName = "healthtrender-core")
> private EntityManager em;
> @Override
> EntityManager entityManager() {
> return em;
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4735) [DMN Designer] Grid performance is dire
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4735?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4735:
--------------------------------
Description:
There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
On closer inspection the following issues were found:
- Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
- Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
h2. Manual Acceptance test
Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
h3. GDT
- Merge view (/)
- Pinned mode (/)
- Change column width, save and reopen (/)
- Search the table (/)
- Scroll the table (/)
- Edit the cell (/)
- Reorder columns (/)
- Reorder rows (/)
h3. DMN decision table
- Change column width, save and reopen (x) [^resize-column.webm] [^resized-column-save.webm]
- Search the grid (/) [^search-trough-grid.webm]
- Scroll the grid (?) scrolling seems working in reasonable time assuming number of rows, however dragging canvas is slower [^drag-scroll.webm]
- Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
- Reorder rows (/) assuming performance of other actions and size of the table [^reorder-rows.webm]
- Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
- Removing column (/) fine, acceptable ignoring time of showing menu reported above [^delete-column.webm]
- Edit the cell (x) invoking the edit mode by double click is very slow, by keyboard it is fine [^cell-edit-mode.webm]
was:
There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
On closer inspection the following issues were found:
- Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
- Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
h2. Manual Acceptance test
Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
h3. GDT
- Merge view (/)
- Pinned mode (/)
- Change column width, save and reopen (/)
- Search the table (/)
- Scroll the table (/)
- Edit the cell (/)
- Reorder columns (/)
- Reorder rows (/)
h3. DMN decision table
- Change column width, save and reopen (x) [^resize-column.webm] [^resized-column-save.webm]
- Search the grid (/) [^search-trough-grid.webm]
- Scroll the grid (?) scrolling seems working in reasonable time assuming number of rows, however dragging canvas is slower [^drag-scroll.webm]
- Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
- Reorder rows
- Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
- Removing column (/) fine, acceptable ignoring time of showing menu reported above [^delete-column.webm]
- Edit the cell (x) invoking the edit mode by double click is very slow, by keyboard it is fine [^cell-edit-mode.webm]
> [DMN Designer] Grid performance is dire
> ---------------------------------------
>
> Key: DROOLS-4735
> URL: https://issues.jboss.org/browse/DROOLS-4735
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.29.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
> Attachments: aTable.dmn, add-new-column.webm, cell-edit-mode.webm, delete-column.webm, drag-scroll.webm, dtable-500-rows.dmn, reorder-columns.webm, reorder-rows.webm, resize-column.webm, resized-column-save.webm, search-trough-grid.webm
>
>
> There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
> On closer inspection the following issues were found:
> - Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
> - Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
> h2. Manual Acceptance test
> Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
> h3. GDT
> - Merge view (/)
> - Pinned mode (/)
> - Change column width, save and reopen (/)
> - Search the table (/)
> - Scroll the table (/)
> - Edit the cell (/)
> - Reorder columns (/)
> - Reorder rows (/)
> h3. DMN decision table
> - Change column width, save and reopen (x) [^resize-column.webm] [^resized-column-save.webm]
> - Search the grid (/) [^search-trough-grid.webm]
> - Scroll the grid (?) scrolling seems working in reasonable time assuming number of rows, however dragging canvas is slower [^drag-scroll.webm]
> - Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
> - Reorder rows (/) assuming performance of other actions and size of the table [^reorder-rows.webm]
> - Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
> - Removing column (/) fine, acceptable ignoring time of showing menu reported above [^delete-column.webm]
> - Edit the cell (x) invoking the edit mode by double click is very slow, by keyboard it is fine [^cell-edit-mode.webm]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4735) [DMN Designer] Grid performance is dire
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4735?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4735:
--------------------------------
Attachment: reorder-rows.webm
> [DMN Designer] Grid performance is dire
> ---------------------------------------
>
> Key: DROOLS-4735
> URL: https://issues.jboss.org/browse/DROOLS-4735
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.29.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
> Attachments: aTable.dmn, add-new-column.webm, cell-edit-mode.webm, delete-column.webm, drag-scroll.webm, dtable-500-rows.dmn, reorder-columns.webm, reorder-rows.webm, resize-column.webm, resized-column-save.webm, search-trough-grid.webm
>
>
> There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
> On closer inspection the following issues were found:
> - Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
> - Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
> h2. Manual Acceptance test
> Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
> h3. GDT
> - Merge view (/)
> - Pinned mode (/)
> - Change column width, save and reopen (/)
> - Search the table (/)
> - Scroll the table (/)
> - Edit the cell (/)
> - Reorder columns (/)
> - Reorder rows (/)
> h3. DMN decision table
> - Change column width, save and reopen (x) [^resize-column.webm] [^resized-column-save.webm]
> - Search the grid (/) [^search-trough-grid.webm]
> - Scroll the grid (?) scrolling seems working in reasonable time assuming number of rows, however dragging canvas is slower [^drag-scroll.webm]
> - Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
> - Reorder rows
> - Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
> - Removing column (/) fine, acceptable ignoring time of showing menu reported above [^delete-column.webm]
> - Edit the cell (x) invoking the edit mode by double click is very slow, by keyboard it is fine [^cell-edit-mode.webm]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4735) [DMN Designer] Grid performance is dire
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4735?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4735:
--------------------------------
Description:
There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
On closer inspection the following issues were found:
- Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
- Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
h2. Manual Acceptance test
Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
h3. GDT
- Merge view (/)
- Pinned mode (/)
- Change column width, save and reopen (/)
- Search the table (/)
- Scroll the table (/)
- Edit the cell (/)
- Reorder columns (/)
- Reorder rows (/)
h3. DMN decision table
- Change column width, save and reopen (x) [^resize-column.webm] [^resized-column-save.webm]
- Search the grid (/) [^search-trough-grid.webm]
- Scroll the grid (?) scrolling seems working in reasonable time assuming number of rows, however dragging canvas is slower [^drag-scroll.webm]
- Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
- Reorder rows
- Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
- Removing column (/) fine, acceptable ignoring time of showing menu reported above [^delete-column.webm]
- Edit the cell (x) invoking the edit mode by double click is very slow, by keyboard it is fine
was:
There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
On closer inspection the following issues were found:
- Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
- Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
h2. Manual Acceptance test
Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
h3. GDT
- Merge view (/)
- Pinned mode (/)
- Change column width, save and reopen (/)
- Search the table (/)
- Scroll the table (/)
- Edit the cell (/)
- Reorder columns (/)
- Reorder rows (/)
h3. DMN decision table
- Change column width, save and reopen (x) [^resize-column.webm] [^resized-column-save.webm]
- Search the grid (/) [^search-trough-grid.webm]
- Scroll the grid (?) scrolling seems working in reasonable time assuming number of rows, however dragging canvas is slower [^drag-scroll.webm]
- Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
- Reorder rows
- Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
- Removing column (/) fine, acceptable ignoring time of showing menu reported above [^delete-column.webm]
> [DMN Designer] Grid performance is dire
> ---------------------------------------
>
> Key: DROOLS-4735
> URL: https://issues.jboss.org/browse/DROOLS-4735
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.29.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
> Attachments: aTable.dmn, add-new-column.webm, cell-edit-mode.webm, delete-column.webm, drag-scroll.webm, dtable-500-rows.dmn, reorder-columns.webm, resize-column.webm, resized-column-save.webm, search-trough-grid.webm
>
>
> There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
> On closer inspection the following issues were found:
> - Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
> - Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
> h2. Manual Acceptance test
> Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
> h3. GDT
> - Merge view (/)
> - Pinned mode (/)
> - Change column width, save and reopen (/)
> - Search the table (/)
> - Scroll the table (/)
> - Edit the cell (/)
> - Reorder columns (/)
> - Reorder rows (/)
> h3. DMN decision table
> - Change column width, save and reopen (x) [^resize-column.webm] [^resized-column-save.webm]
> - Search the grid (/) [^search-trough-grid.webm]
> - Scroll the grid (?) scrolling seems working in reasonable time assuming number of rows, however dragging canvas is slower [^drag-scroll.webm]
> - Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
> - Reorder rows
> - Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
> - Removing column (/) fine, acceptable ignoring time of showing menu reported above [^delete-column.webm]
> - Edit the cell (x) invoking the edit mode by double click is very slow, by keyboard it is fine
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months