April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3940) DMN Editor: Update contextual menus (headers and cells.)

by Elizabeth Clayton (Jira)

Elizabeth Clayton created DROOLS-3940: ----------------------------------------- Summary: DMN Editor: Update contextual menus (headers and cells.) Key: DROOLS-3940 URL: https://issues.jboss.org/browse/DROOLS-3940 Project: Drools Issue Type: Enhancement Components: DMN Editor Reporter: Elizabeth Clayton Assignee: Elizabeth Clayton Attachments: Screen Shot 2019-04-18 at 5.04.49 PM.png, header-context.png, header-context2b.png As a user of this feature I want to have the possibility to add columns or rows in a DT when right-clicking on the table header. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3940) DMN Editor: Update contextual menus (headers and cells.)

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3940?page=com.atlassian.jira.plugi... ] Elizabeth Clayton reassigned DROOLS-3940: ----------------------------------------- Assignee: Michael Anstis (was: Elizabeth Clayton) > DMN Editor: Update contextual menus (headers and cells.) > -------------------------------------------------------- > > Key: DROOLS-3940 > URL: https://issues.jboss.org/browse/DROOLS-3940 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Michael Anstis > Priority: Major > Labels: Field, UX, UXTeam, drools-tools > Attachments: Screen Shot 2019-04-18 at 5.04.49 PM.png, header-context.png, header-context2b.png > > > As a user of this feature I want to have the possibility to add columns or rows in a DT when right-clicking on the table header. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3877) DMN Decision table headers: Add edit table actions to contextual menu.

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3877?page=com.atlassian.jira.plugi... ] Elizabeth Clayton resolved DROOLS-3877. --------------------------------------- Resolution: Done per review by [~manstis] > DMN Decision table headers: Add edit table actions to contextual menu. > ---------------------------------------------------------------------- > > Key: DROOLS-3877 > URL: https://issues.jboss.org/browse/DROOLS-3877 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: Field, UX, UXTeam, drools-tools > Attachments: Screen Shot 2019-04-18 at 5.04.49 PM.png, header-context.png, header-context2b.png > > > As a user of this feature I want to have the possibility to add columns or rows in a DT when right-clicking on the table header. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12015) WFLYUT0017 warning appears once xml-jaxp quickstart is undeployed

by Lukas Burda (Jira)

Lukas Burda created WFLY-12015: ---------------------------------- Summary: WFLYUT0017 warning appears once xml-jaxp quickstart is undeployed Key: WFLY-12015 URL: https://issues.jboss.org/browse/WFLY-12015 Project: WildFly Issue Type: Bug Components: Quickstarts Reporter: Lukas Burda Assignee: Eduardo Martins Since we have started running actual quickstarts on Windows OS all (except _xml-jaxp_) of them ran smoothly. While undeploying _xml-jaxp_ quickstart the following warning appears in server log: {noformat} WARN [org.wildfly.extension.undertow] (ServerService Thread Pool -- 78) WFLYUT0017: Could not delete servlet temp file C:\j\workspace\eap-7.x-quick---ec6481ca\b9367ec8\manu-eap-1.1.124\out\xml-jaxp.DownloadEap\workspace\jboss-eap-7.2\standalone\tmp\xml-jaxp.war\undertow7293344395514676051upload WARN [org.wildfly.extension.undertow] (ServerService Thread Pool -- 78) WFLYUT0017: Could not delete servlet temp file C:\j\workspace\eap-7.x-quick---ec6481ca\b9367ec8\manu-eap-1.1.124\out\xml-jaxp.DownloadEap\workspace\jboss-eap-7.2\standalone\tmp\xml-jaxp.war {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4442) Migrate UndertowHttpManagementService & HttpShutdownService to use new MSC service builder API

by Richard Opalka (Jira)

Richard Opalka created WFCORE-4442: -------------------------------------- Summary: Migrate UndertowHttpManagementService & HttpShutdownService to use new MSC service builder API Key: WFCORE-4442 URL: https://issues.jboss.org/browse/WFCORE-4442 Project: WildFly Core Issue Type: Task Components: Server Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 9.0.0.Beta4 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11978) EAR with 2+ JPA does not shutdown cleanly

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-11978?page=com.atlassian.jira.plugin... ] Scott Marlow commented on WFLY-11978: ------------------------------------- [~dlmiles] does this recreate if the application has not actually serviced any user requests? I tried to recreate with a very simple jar that contains: {code} <?xml version="1.0" encoding="UTF-8"?> <persistence xmlns="http://java.sun.com/xml/ns/persistence" version="1.0"> <persistence-unit name="TEST_PU"> <jta-data-source>java:jboss/datasources/ExampleDS</jta-data-source> <shared-cache-mode>ENABLE_SELECTIVE</shared-cache-mode> <properties> <property name="hibernate.enhancer.enableDirtyTracking" value="true"/> <property name="hibernate.generate_statistics" value="true"/> <property name="hibernate.cache.use_second_level_cache" value="true"/> <property name="hibernate.cache.use_query_cache" value="true"/> </properties> </persistence-unit> <persistence-unit name="second_PU"> <jta-data-source>java:jboss/datasources/ExampleDS</jta-data-source> <properties> <property name="hibernate.enhancer.enableDirtyTracking" value="false"/> <property name="hibernate.generate_statistics" value="false"/> <property name="hibernate.cache.use_second_level_cache" value="true"/> <property name="hibernate.cache.use_query_cache" value="true"/> </properties> </persistence-unit> </persistence> {code} I did a jstack thread dump and don't see the same issue after undeployment (using the latest [WildFly master branch code|https://github.com/wildfly/wildfly]). Do you have a simple test ear that recreates this that you could attach? Best if it uses java:jboss/datasources/ExampleDS, as I show in my ^ persistence.xml. Also, from a quick look at the Infinispan [https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o...], I don't really understand where the code is that does the notify() to wake this thread up. I wonder if its a race where the state is ComponentStatus.STOPPING but changes by time wait() is called. > EAR with 2+ JPA does not shutdown cleanly > ----------------------------------------- > > Key: WFLY-11978 > URL: https://issues.jboss.org/browse/WFLY-11978 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 16.0.0.Final > Environment: Windows JDK8 WF16 > Reporter: Darryl Miles > Assignee: Scott Marlow > Priority: Major > Attachments: td8948.txt > > > EAR with 2+ JPA does not shutdown cleanly. > I see in the logs each JPA project have an entry: > WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'blah....jpa.project1' > WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'blah....jpa.project2' > then a few lines later: > WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'blah....jpa.project2' > I never see the "phase 1 of 2" entry for "jpa.project1" in the log. > The container will wait 300 seconds and timeout. > The management console during the time shows > Operation: undeploy > Execution Status: awaiting-stablility. > The container is killed and the configuration.xml still contains the EAR deployment info, as undeploy did not complete. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3438) Cancel Scenario Simulation edit mode

by Ivo Bek (Jira)

[ https://issues.jboss.org/browse/DROOLS-3438?page=com.atlassian.jira.plugi... ] Ivo Bek updated DROOLS-3438: ---------------------------- Priority: Critical (was: Major) > Cancel Scenario Simulation edit mode > ------------------------------------ > > Key: DROOLS-3438 > URL: https://issues.jboss.org/browse/DROOLS-3438 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.16.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Critical > Labels: FieldEnablementFeedbackNA73, drools-tools > Fix For: 7.21.0.Final > > > User is able to edit grid cell by pressing an enter. Currently the edit mode is cancelled by *Shift + Tab* combination. We have to change this to: > - *Tab* for cancel edit mode and *store* the value > - *Esc* for cancel edit mode and *discard* the value > This defect is caused by keyboard shortcuts implemented as part of DROOLS-2932. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3932) [DMN Designer] Replace BPMN specific parsing error message

by Ivo Bek (Jira)

[ https://issues.jboss.org/browse/DROOLS-3932?page=com.atlassian.jira.plugi... ] Ivo Bek updated DROOLS-3932: ---------------------------- Labels: FieldEnablementFeedbackNA73 drools-tools (was: drools-tools) > [DMN Designer] Replace BPMN specific parsing error message > ---------------------------------------------------------- > > Key: DROOLS-3932 > URL: https://issues.jboss.org/browse/DROOLS-3932 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.20.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: FieldEnablementFeedbackNA73, drools-tools > Fix For: 7.21.0.Final > > > When opening an invalid DMN file (one that fails parsing) the editor displays the error message "An error was produced during process diagram parsing. There might be bpm nodes not yet supported by current Process Designer version, or the xml content can contain errors. You can try to open the file with the Legacy Process Designer or repair it manually". This needs changing to something more DMN friendly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3438) Cancel Scenario Simulation edit mode

by Ivo Bek (Jira)

[ https://issues.jboss.org/browse/DROOLS-3438?page=com.atlassian.jira.plugi... ] Ivo Bek updated DROOLS-3438: ---------------------------- Labels: FieldEnablementFeedbackNA73 drools-tools (was: drools-tools) > Cancel Scenario Simulation edit mode > ------------------------------------ > > Key: DROOLS-3438 > URL: https://issues.jboss.org/browse/DROOLS-3438 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.16.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Labels: FieldEnablementFeedbackNA73, drools-tools > Fix For: 7.21.0.Final > > > User is able to edit grid cell by pressing an enter. Currently the edit mode is cancelled by *Shift + Tab* combination. We have to change this to: > - *Tab* for cancel edit mode and *store* the value > - *Esc* for cancel edit mode and *discard* the value > This defect is caused by keyboard shortcuts implemented as part of DROOLS-2932. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-724) Increase disk space available for PSI

by Kevin Earls (Jira)

[ https://issues.jboss.org/browse/SWSQE-724?page=com.atlassian.jira.plugin.... ] Kevin Earls commented on SWSQE-724: ----------------------------------- See https://redhat.service-now.com/pnt?id=ticket&table=x_redha_pnt_devops_tab... for more info. > Increase disk space available for PSI > ------------------------------------- > > Key: SWSQE-724 > URL: https://issues.jboss.org/browse/SWSQE-724 > Project: Kiali QE > Issue Type: QE Task > Reporter: Kevin Earls > Priority: Major > > Currently we only have 2TB of disk allocated on PSI (See https://rhos-d.infra.prod.upshift.rdu2.redhat.com/dashboard/project/) We've already used 700g of this, even though we've used very few of our other resources. > This is very likely to be a problem long term and should be increased. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2019