February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4963) [DMN Designer] Type designer does not show save/cancel when many constraints are presents and the inspector is open

by Edoardo Vacchi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4963?page=com.atlassian.jira.plug... ] Edoardo Vacchi commented on DROOLS-4963: ---------------------------------------- I had uploaded them twice inadvertently sorry > [DMN Designer] Type designer does not show save/cancel when many constraints are presents and the inspector is open > ------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4963 > URL: https://issues.redhat.com/browse/DROOLS-4963 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.32.0.Final > Reporter: Edoardo Vacchi > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2020-01-22 16-16-29.png > > > hiding the inspector on the right-hand side uncovers the save/cancel buttons > !Screenshot from 2020-01-22 16-16-29.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4963) [DMN Designer] Type designer does not show save/cancel when many constraints are presents and the inspector is open

by Edoardo Vacchi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4963?page=com.atlassian.jira.plug... ] Edoardo Vacchi updated DROOLS-4963: ----------------------------------- Attachment: (was: Screenshot from 2020-01-22 16-16-29.png) > [DMN Designer] Type designer does not show save/cancel when many constraints are presents and the inspector is open > ------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4963 > URL: https://issues.redhat.com/browse/DROOLS-4963 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.32.0.Final > Reporter: Edoardo Vacchi > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2020-01-22 16-16-29.png > > > hiding the inspector on the right-hand side uncovers the save/cancel buttons > !Screenshot from 2020-01-22 16-16-29.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12778) EAR deployed on colocated master/slave servers does not wait for the embedded JMS services to startup properly

by Bartosz Spyrko (Jira)

[ https://issues.redhat.com/browse/WFLY-12778?page=com.atlassian.jira.plugi... ] Bartosz Spyrko commented on WFLY-12778: --------------------------------------- [~parsharma] I think so, it just needs to be a clustered messaging setup if I remember right. The problem is AMQ server starts in async way, if the data recovery/replication takes too long, the deployment will fail because jms services depending on active AMQ are not available. > EAR deployed on colocated master/slave servers does not wait for the embedded JMS services to startup properly > -------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12778 > URL: https://issues.redhat.com/browse/WFLY-12778 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Bartosz Spyrko > Assignee: Bartosz Spyrko > Priority: Major > > When an EAR containing MDBS is deployed in one of the colocated master/slave servers, the application does not wait for the embedded broker to start up and generates these errors in the logs: > {code:java} > /14:48:11,134 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "EJB_MDBEAR.ear")]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => [ > "jboss.ra.activemq-ra", > "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory" > ], > {code} > When the broker is eventually started, these MDBs get deployed and start working fine without any redeployment but these errors are not desirable in the logs. > Defining the resource-ref in ejb-jar.xml or annotating with @Resource does not help either. > The application should wait for its dependencies to be available. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4963) [DMN Designer] Type designer does not show save/cancel when many constraints are presents and the inspector is open

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4963?page=com.atlassian.jira.plug... ] Jozef Marko commented on DROOLS-4963: ------------------------------------- [~manstis] I spot the same in KOGITO-1244. Does details there explain you the issue? > [DMN Designer] Type designer does not show save/cancel when many constraints are presents and the inspector is open > ------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4963 > URL: https://issues.redhat.com/browse/DROOLS-4963 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.32.0.Final > Reporter: Edoardo Vacchi > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2020-01-22 16-16-29.png, Screenshot from 2020-01-22 16-16-29.png > > > hiding the inspector on the right-hand side uncovers the save/cancel buttons > !Screenshot from 2020-01-22 16-16-29.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13158) Upgrade smallrye-config from 1.6.1 to 1.6.2

by Lin Gao (Jira)

[ https://issues.redhat.com/browse/WFLY-13158?page=com.atlassian.jira.plugi... ] Lin Gao updated WFLY-13158: --------------------------- Labels: downstream_dependency (was: ) > Upgrade smallrye-config from 1.6.1 to 1.6.2 > ------------------------------------------- > > Key: WFLY-13158 > URL: https://issues.redhat.com/browse/WFLY-13158 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System, MP Config > Reporter: Lin Gao > Assignee: Jeff Mesnil > Priority: Major > Labels: downstream_dependency > > To include CVE-2020-1729 fix. > https://github.com/smallrye/smallrye-config/compare/1.6.1...1.6.2 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13158) Upgrade smallrye-config from 1.6.1 to 1.6.2

by Lin Gao (Jira)

[ https://issues.redhat.com/browse/WFLY-13158?page=com.atlassian.jira.plugi... ] Lin Gao updated WFLY-13158: --------------------------- Description: To include CVE-2020-1729 fix. https://github.com/smallrye/smallrye-config/compare/1.6.1...1.6.2 was: To include CVE-2020-1729 fix. > Upgrade smallrye-config from 1.6.1 to 1.6.2 > ------------------------------------------- > > Key: WFLY-13158 > URL: https://issues.redhat.com/browse/WFLY-13158 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System, MP Config > Reporter: Lin Gao > Assignee: Jeff Mesnil > Priority: Major > > To include CVE-2020-1729 fix. > https://github.com/smallrye/smallrye-config/compare/1.6.1...1.6.2 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13158) Upgrade smallrye-config from 1.6.1 to 1.6.2

by Lin Gao (Jira)

Lin Gao created WFLY-13158: ------------------------------ Summary: Upgrade smallrye-config from 1.6.1 to 1.6.2 Key: WFLY-13158 URL: https://issues.redhat.com/browse/WFLY-13158 Project: WildFly Issue Type: Component Upgrade Components: Build System, MP Config Reporter: Lin Gao Assignee: Jeff Mesnil To include CVE-2020-1729 fix. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12778) EAR deployed on colocated master/slave servers does not wait for the embedded JMS services to startup properly

by Parul Sharma (Jira)

[ https://issues.redhat.com/browse/WFLY-12778?page=com.atlassian.jira.plugi... ] Parul Sharma commented on WFLY-12778: ------------------------------------- Hi [~spyrkob], In JBEAP [http://issues.redhat.com/browse/JBEAP-17990] also can we reproduced this issue without colocated setup? > EAR deployed on colocated master/slave servers does not wait for the embedded JMS services to startup properly > -------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12778 > URL: https://issues.redhat.com/browse/WFLY-12778 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Bartosz Spyrko > Assignee: Bartosz Spyrko > Priority: Major > > When an EAR containing MDBS is deployed in one of the colocated master/slave servers, the application does not wait for the embedded broker to start up and generates these errors in the logs: > {code:java} > /14:48:11,134 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "EJB_MDBEAR.ear")]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => [ > "jboss.ra.activemq-ra", > "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory" > ], > {code} > When the broker is eventually started, these MDBs get deployed and start working fine without any redeployment but these errors are not desirable in the logs. > Defining the resource-ref in ejb-jar.xml or annotating with @Resource does not help either. > The application should wait for its dependencies to be available. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5102) DMN npe when xml defines empty default expression for DT

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5102?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-5102: ----------------------------------- Tester: Daniel Rosa > DMN npe when xml defines empty default expression for DT > -------------------------------------------------------- > > Key: DROOLS-5102 > URL: https://issues.redhat.com/browse/DROOLS-5102 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.33.0.Final > Reporter: Eugenio Romano > Assignee: Matteo Mortari > Priority: Critical > Attachments: different-all.dmn > > > If you execute the DMN table in attach in the last version you will have a NullPointerException in case your input value is not matching any output. > We are moving from version 23 to 33 and one of our tests are catching this issue > The ProcessedExpression Class seems can be responsible of causing this NullPointerException. > {code:java} > this.ast = (BaseNode)tree.accept(new ASTBuilderVisitor(ctx.getInputVariableTypes(), ctx.getFEELFeelTypeRegistry())) > {code} > If you try with > "inputString", "hi" > "inputInteger", 12 > "inputBoolean", false > "inputDate", "2019-09-26T00:00:00.000+0000" > you can replicate the error > I guess the expected behavior should be a null output as before -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5102) DMN npe when xml defines empty default expression for DT

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5102?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-5102: ----------------------------------- Story Points: 3 > DMN npe when xml defines empty default expression for DT > -------------------------------------------------------- > > Key: DROOLS-5102 > URL: https://issues.redhat.com/browse/DROOLS-5102 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.33.0.Final > Reporter: Eugenio Romano > Assignee: Matteo Mortari > Priority: Critical > Attachments: different-all.dmn > > > If you execute the DMN table in attach in the last version you will have a NullPointerException in case your input value is not matching any output. > We are moving from version 23 to 33 and one of our tests are catching this issue > The ProcessedExpression Class seems can be responsible of causing this NullPointerException. > {code:java} > this.ast = (BaseNode)tree.accept(new ASTBuilderVisitor(ctx.getInputVariableTypes(), ctx.getFEELFeelTypeRegistry())) > {code} > If you try with > "inputString", "hi" > "inputInteger", 12 > "inputBoolean", false > "inputDate", "2019-09-26T00:00:00.000+0000" > you can replicate the error > I guess the expected behavior should be a null output as before -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 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 February 2020