June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4257) DMN UX - overlay information about an entire simulation execution

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4257?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4257: -------------------------------- Affects Version/s: 7.24.0.Final > DMN UX - overlay information about an entire simulation execution > ----------------------------------------------------------------- > > Key: DROOLS-4257 > URL: https://issues.jboss.org/browse/DROOLS-4257 > Project: Drools > Issue Type: Story > Components: DMN Editor > Affects Versions: 7.24.0.Final > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam, drools-tools > > Related to https://issues.jboss.org/browse/DROOLS-3731 > This task will cover this use case: > - user creates a DMN model > - user creates a Test Scenario with some scenarios > - user executes the Test Scenario > - user open Coverage Report > - user wants to analyze coverage information of the *whole* simulation > - user clicks on "a link" near global coverage information > - user lands on DMN editor with overlay information about number of time each decision has been executed, number of time each decision succeed/fail (maybe with different colors?) -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4258) DMN UX - overlay information about a single scenario run

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4258?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4258: -------------------------------- Affects Version/s: 7.24.0.Final > DMN UX - overlay information about a single scenario run > -------------------------------------------------------- > > Key: DROOLS-4258 > URL: https://issues.jboss.org/browse/DROOLS-4258 > Project: Drools > Issue Type: Story > Components: DMN Editor > Affects Versions: 7.24.0.Final > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam, drools-tools > > Related to https://issues.jboss.org/browse/DROOLS-3731 > This task will cover this use case: > - user creates a DMN model > - user creates a Test Scenario with some scenarios > - user executes the Test Scenario > - user open Coverage Report > - user wants to analyze the execution of a *single scenario* in the DMN model > - user clicks on "a link" related to the scenario to analyze > - user lands on DMN editor with overlay information about decision executed, decision failed and for each decision the possibility see actual and expected value (from the scenario) and to open an executed decision table to see which row has been evaluated -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4259) Scenario can not access parent data object fields

by Jozef Marko (Jira)

Jozef Marko created DROOLS-4259: ----------------------------------- Summary: Scenario can not access parent data object fields Key: DROOLS-4259 URL: https://issues.jboss.org/browse/DROOLS-4259 Project: Drools Issue Type: Bug Components: Scenario Simulation and Testing Affects Versions: 7.24.0.Final Reporter: Jozef Marko Assignee: Daniele Zonca Attachments: Screenshot from 2019-06-26 08-56-23.png, inheritance.zip Scenario Designer can not access parent data object fields, even if the field has public getter and setter. If you check the attached project there are two fields - *price* and *size* while *size* is declared in parent class. If you try to run the scenario, error about not possible initialization of the data object appears. If you move the *size* field from *Picture* into *Advertisement* class and rerun the scenario, everything works fine. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4257) DMN UX - overlay information about an entire simulation execution

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-4257?page=com.atlassian.jira.plugi... ] Klara Kufova commented on DROOLS-4257: -------------------------------------- [~zhutaojiajia], [~danielezonca], should this task be in the current sprint? > DMN UX - overlay information about an entire simulation execution > ----------------------------------------------------------------- > > Key: DROOLS-4257 > URL: https://issues.jboss.org/browse/DROOLS-4257 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam, drools-tools > > Related to https://issues.jboss.org/browse/DROOLS-3731 > This task will cover this use case: > - user creates a DMN model > - user creates a Test Scenario with some scenarios > - user executes the Test Scenario > - user open Coverage Report > - user wants to analyze coverage information of the *whole* simulation > - user clicks on "a link" near global coverage information > - user lands on DMN editor with overlay information about number of time each decision has been executed, number of time each decision succeed/fail (maybe with different colors?) -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4258) DMN UX - overlay information about a single scenario run

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-4258?page=com.atlassian.jira.plugi... ] Klara Kufova commented on DROOLS-4258: -------------------------------------- [~zhutaojiajia], [~danielezonca], should this task be in the current sprint? > DMN UX - overlay information about a single scenario run > -------------------------------------------------------- > > Key: DROOLS-4258 > URL: https://issues.jboss.org/browse/DROOLS-4258 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam, drools-tools > > Related to https://issues.jboss.org/browse/DROOLS-3731 > This task will cover this use case: > - user creates a DMN model > - user creates a Test Scenario with some scenarios > - user executes the Test Scenario > - user open Coverage Report > - user wants to analyze the execution of a *single scenario* in the DMN model > - user clicks on "a link" related to the scenario to analyze > - user lands on DMN editor with overlay information about decision executed, decision failed and for each decision the possibility see actual and expected value (from the scenario) and to open an executed decision table to see which row has been evaluated -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3731) DMN UX - More info overlaid on models.

by Tao Zhu (Jira)

[ https://issues.jboss.org/browse/DROOLS-3731?page=com.atlassian.jira.plugi... ] Tao Zhu commented on DROOLS-3731: --------------------------------- [~uxdlc] Hi Liz, there are new sub tasks had been created: https://issues.jboss.org/browse/DROOLS-4257 and https://issues.jboss.org/browse/DROOLS-4258 could we close this task? > DMN UX - More info overlaid on models. > -------------------------------------- > > Key: DROOLS-3731 > URL: https://issues.jboss.org/browse/DROOLS-3731 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam, drools-tools > Attachments: Screen Shot 2019-05-29 at 2.49.21 PM.png, colors.png, download (1).png, download.png, multi.gif, single.gif, tmp.png, 屏幕快照 2019-06-11 下午3.02.19.png, 屏幕快照 2019-06-11 下午3.10.26.png > > > As a practitioner, there are situations where I need to show additional information about a model... for instance: test coverage report: I need to draw a model and color code the nodes to show which nodes were executed by tests, or which rows on a DT were a match. Or when I execute a single test, what was the actual value of a given node or expression. > Note: Maybe in read-only mode with an "overlay" on top of the model the additional metadata information. See process instance diagram design examples. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12212) Restore LastNodeToLeaveRemoteEJBTestCase, disabled for JDK 11 runs if necessary

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-12212?page=com.atlassian.jira.plugin... ] Paul Ferraro reassigned WFLY-12212: ----------------------------------- Assignee: Paul Ferraro (was: Richard Achmatowicz) > Restore LastNodeToLeaveRemoteEJBTestCase, disabled for JDK 11 runs if necessary > ------------------------------------------------------------------------------- > > Key: WFLY-12212 > URL: https://issues.jboss.org/browse/WFLY-12212 > Project: WildFly > Issue Type: Task > Components: Clustering, EJB > Affects Versions: 17.0.0.Final > Reporter: Brian Stansberry > Assignee: Paul Ferraro > Priority: Critical > > The WLFY-11682 work[1] originally included a test, but that test was removed before the PR was merged. AIUI the test was removed because it could not work on JDK 11 due to byteman/arquillian issues.[2] The test did seem to work on JDK 8. > Having the test removed means this functionality isn't guarded against regression. So this issue is to track getting it restored. If it can be disabled on JDK 11 runs pending the arquillian/byteman issue being resolved, that's ok. > [1] https://github.com/wildfly/wildfly/pull/12133 > [2] https://github.com/arquillian/arquillian-extension-byteman/issues/25 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12226) IJ020017: Invalid archive: file://RaActivatoractivemq-ra WARN during start with standalone-full*.xml

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12226?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-12226: ----------------------------------------- Well, it is kind of possible to override the return type for the *property*, just not for the method. Add a 'get' getter method to go along with the 'is'. Hacky but stops the WARN https://github.com/wildfly/wildfly/pull/12388 That would just be a temp fix though; the real fix needs to be in Artemis. > IJ020017: Invalid archive: file://RaActivatoractivemq-ra WARN during start with standalone-full*.xml > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-12226 > URL: https://issues.jboss.org/browse/WFLY-12226 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 18.0.0.Beta1 > Reporter: Ondrej Kotek > Assignee: Emmanuel Hugonnet > Priority: Critical > > There is a warning during start with standalone-full*.xml: > {noformat} > 12:19:04,432 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0007: Registered connection factory java:/JmsXA > 12:19:04,440 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 84) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 12:19:04,441 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 83) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory > 12:19:04,441 WARN [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020017: Invalid archive: file://RaActivatoractivemq-ra > 12:19:04,486 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-3) AMQ151007: Resource adaptor started > 12:19:04,486 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020002: Deployed: file://RaActivatoractivemq-ra > 12:19:04,492 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-6) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 12:19:04,493 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0118: Binding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory > {noformat} > For an automation checking the server log for issues, this WARN causes false positive. Hence, I set the Priority to Critical. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12226) IJ020017: Invalid archive: file://RaActivatoractivemq-ra WARN during start with standalone-full*.xml

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12226?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-12226: --------------------------------------- Component/s: JMS (was: JCA) Assignee: Emmanuel Hugonnet (was: Stefano Maestri) [~ehugonnet] This is an Artemis bug. Here's the org.jboss.jca.validator.Failure that is triggering this WARN message: Severity: WARNING Section: 20.7 Description: Invalid config-property-type for ResourceAdapter. Code: Class: org.wildfly.extension.messaging.activemq.ActiveMQResourceAdapter Property: useTopologyForLoadBalancing Type: boolean That property is inherited from org.apache.activemq.artemis.ra.ActiveMQResourceAdapter which has 'boolean' as the return type. Apparently these RA getters are meant to use object wrappers, not primitives. See org.jboss.jca.validator.rules.ConfigPropertiesHelper.containGetOrIsMethod Unfortunately java doesn't let org.wildfly.extension.messaging.activemq.ActiveMQResourceAdapter override this method and broaden the return type. :) > IJ020017: Invalid archive: file://RaActivatoractivemq-ra WARN during start with standalone-full*.xml > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-12226 > URL: https://issues.jboss.org/browse/WFLY-12226 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 18.0.0.Beta1 > Reporter: Ondrej Kotek > Assignee: Emmanuel Hugonnet > Priority: Critical > > There is a warning during start with standalone-full*.xml: > {noformat} > 12:19:04,432 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0007: Registered connection factory java:/JmsXA > 12:19:04,440 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 84) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 12:19:04,441 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 83) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory > 12:19:04,441 WARN [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020017: Invalid archive: file://RaActivatoractivemq-ra > 12:19:04,486 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-3) AMQ151007: Resource adaptor started > 12:19:04,486 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020002: Deployed: file://RaActivatoractivemq-ra > 12:19:04,492 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-6) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 12:19:04,493 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0118: Binding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory > {noformat} > For an automation checking the server log for issues, this WARN causes false positive. Hence, I set the Priority to Critical. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12031) Memory leak in wildfly transaction client

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12031?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-12031: ----------------------------------------- [~cfang] Is this fixed now? WFTC was upgraded. > Memory leak in wildfly transaction client > ----------------------------------------- > > Key: WFLY-12031 > URL: https://issues.jboss.org/browse/WFLY-12031 > Project: WildFly > Issue Type: Bug > Components: Transactions > Affects Versions: 15.0.1.Final > Environment: wildfly-transaction-client-1.1.3.Final > wildfly.15.0.1.Final > Windows 10 > Reporter: Joachim Petrich > Assignee: Cheng Fang > Priority: Critical > > After a volume run of our system we recognized millions of entries in the openFilePaths Object of class FileSystemXAResourceRegistry. When enabling traces for org.wildfly.transaction it seems that for adding an entry a xid string is used > {code:java} > XAResourceRegistryFile(Xid xid) throws SystemException { > xaRecoveryPath.toFile().mkdir(); // create dir if non existent > final String xidString = SimpleXid.of(xid).toHexString('_'); > this.filePath = xaRecoveryPath.resolve(xidString); > openFilePaths.add(*xidString*); > {code} > and for removing the entire file path: > {code:java} > protected void removeResource(XAResource resource) throws XAException { > if (resources.remove(resource)) { > if (resources.isEmpty()) { > // delete file > try { > if (fileChannel != null) { > fileChannel.close(); > } > Files.delete(filePath); > // deleting using the filepath as key caused a memory leak, > // if xid string have been added, therefore build the xid string for removing > openFilePaths.remove(*filePath.toString()*); > {code} > We didn't find any code where this xid are cleaned up. > As workaround we additionally extract the xid String from the file path and remove the corresponding entry. > {code:java} > String xidString = filePath.toString().substring(filePath.toString().indexOf( > xaRecoveryPath.toString()) + xaRecoveryPath.toString().length() + 1); > openFilePaths.remove(xidString); > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2019