April 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10207) [Artemis 2.x upgrade] journal-jdbc-lock-acquisition-timeout attribute should be removed

by Erich Duda (JIRA)

Erich Duda created WFLY-10207: --------------------------------- Summary: [Artemis 2.x upgrade] journal-jdbc-lock-acquisition-timeout attribute should be removed Key: WFLY-10207 URL: https://issues.jboss.org/browse/WFLY-10207 Project: WildFly Issue Type: Bug Components: JMS Reporter: Erich Duda Assignee: Jeff Mesnil Priority: Blocker The new integration code which integrates Artemis 2.x contains new attribute {{journal-jdbc-lock-acquisition-timeout}}. However this attribute has been removed recently in Artemis \[1\] and its value has been hard-coded to -1. Messaging layer should drop this attribute either. \[1\] https://github.com/apache/activemq-artemis/pull/1972 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-124) Fix or replace the CNCF CI OpenShift Cluster

by Kevin Earls (JIRA)

[ https://issues.jboss.org/browse/SWSQE-124?page=com.atlassian.jira.plugin.... ] Kevin Earls commented on SWSQE-124: ----------------------------------- [~mmahoney] So far I have only seen this on the CNCF CI openshift. I'm not sure exactly what "containerized OpenShift" means, but I haven't had any problems with deletions on minishift on my Mac. > Fix or replace the CNCF CI OpenShift Cluster > -------------------------------------------- > > Key: SWSQE-124 > URL: https://issues.jboss.org/browse/SWSQE-124 > Project: Kiali QE > Issue Type: QE Task > Reporter: Kevin Earls > Assignee: Matt Mahoney > > As we've discussed in email, the CNCF CI OpenShift cluster is currently in a state where deleting some resources is impossible, which makes it impossible to run Jenkins tests. I first saw this when a test tried to delete ElasticSearch. Then after a cluster restart I saw the same problem with Cassandra. > We either need to figure out how to resolve the problem, or replace the cluster. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-109) Allocate OpenShift and Jenkins resources for Jaeger performance testing

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-109?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reassigned SWSQE-109: --------------------------------------------- Assignee: Guilherme Baufaker Rêgo (was: Michael Foley) > Allocate OpenShift and Jenkins resources for Jaeger performance testing > ----------------------------------------------------------------------- > > Key: SWSQE-109 > URL: https://issues.jboss.org/browse/SWSQE-109 > Project: Kiali QE > Issue Type: QE Task > Reporter: Kevin Earls > Assignee: Guilherme Baufaker Rêgo > > This JIRA is to track what I've mentioned in a few of the Infrastructure team meetings, the need for OpenShift and Jenkins resources to run Jaeger performance tests. > Initial requirements for this are for something similar to what we've been using on the CNCF CI OpenShift, which is an "Intel E3-1240 v3" with 32g of memory and 250g of ssd. Longer term this will need to grow, although I don't really have any idea at this point what requirements will be. Perhaps Jaeger testing and Kiali/Istio testing can use the same resources. > As this is required for performance testing whatever resources we use will need to be isolated from other OpenShift users so that test results are repeatable. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2458) [DMN Designer] Error while removing connected decision

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2458?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2458: ---------------------------------------- [~jomarko] I tried with the lastest {{master}} and deletion of connectors worked OK without problem. I also tried saving and reloading a diagram with connectors; to check it was a marshalling problem but I could delete connectors after re-opening too. Did this problem only exist when testing the JBPM-6777 PR? > [DMN Designer] Error while removing connected decision > ------------------------------------------------------ > > Key: DROOLS-2458 > URL: https://issues.jboss.org/browse/DROOLS-2458 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Critical > Fix For: 7.8.0.Final > > Attachments: Screenshot from 2018-04-06 14-41-28.png, Screenshot from 2018-04-06 14-42-45.png > > > If there are connected decisions, user is unable to delete them. Issue was found during JBPM-6777 review, however probably there is no relation. > h2. Acceptance test > Prepare DRG diagram with all combinations of connections, be sure all node types used, try to delete each node type in situation it is either source or target of connection. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2462) kie-docs 6.5.x doesn't build offline

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2462?page=com.atlassian.jira.plugi... ] Marek Novotny commented on DROOLS-2462: --------------------------------------- I see it is required to be in ~/.m2/repository/net/sf/docbook/docbook-xsl/1.76.1/docbook-xsl-1.76.1-resources.zip, we have maven repository cache where that zip file is available, so there should not be any reason to download it again as that won't change. We can have wrong maven settings.xml for the released version or there is another issue connected to this build error. > kie-docs 6.5.x doesn't build offline > ------------------------------------ > > Key: DROOLS-2462 > URL: https://issues.jboss.org/browse/DROOLS-2462 > Project: Drools > Issue Type: Bug > Components: docs > Affects Versions: 6.5.0.Final > Reporter: Michael Biarnes Kiefer > Assignee: Marek Novotny > > when the repository kie-docs 6.5.x is build offline > _man clean install -Dfull -o_ (and without internet connection) this error is thrown: [error|https://gist.github.com/mbiarnes/bb3a46bebf788225f663f249fc9dc361] > The general suspicion is that <xsl:import href="http://docbook.sourceforge.net/release/xsl/1.76.1/fo/docbook.xsl"/> can't be downloaded and this causes the error. > We have on Jenkins each "some days" period that kie-docs fails, but when building again it builds successful. So when it fails it has no connection problems and this file can't be downloaded. > A build without internet connection is not possible. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-124) Fix or replace the CNCF CI OpenShift Cluster

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-124?page=com.atlassian.jira.plugin.... ] Matt Mahoney commented on SWSQE-124: ------------------------------------ [~kearls] is this issue happening on Openshift CNCF only (aka: containerized Openshift), or also other clusters that are not running in a container? > Fix or replace the CNCF CI OpenShift Cluster > -------------------------------------------- > > Key: SWSQE-124 > URL: https://issues.jboss.org/browse/SWSQE-124 > Project: Kiali QE > Issue Type: QE Task > Reporter: Kevin Earls > Assignee: Matt Mahoney > > As we've discussed in email, the CNCF CI OpenShift cluster is currently in a state where deleting some resources is impossible, which makes it impossible to run Jenkins tests. I first saw this when a test tried to delete ElasticSearch. Then after a cluster restart I saw the same problem with Cassandra. > We either need to figure out how to resolve the problem, or replace the cluster. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2425) [DMN Designer] Undo of relation column deletion is not proper

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2425?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2425: ----------------------------------- Sprint: 2018 Week 13-14, 2018 Week 15-16 (was: 2018 Week 13-14) > [DMN Designer] Undo of relation column deletion is not proper > ------------------------------------------------------------- > > Key: DROOLS-2425 > URL: https://issues.jboss.org/browse/DROOLS-2425 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Attachments: Screenshot from 2018-03-27 12-12-05.png, Screenshot from 2018-03-27 12-14-47.png, Screenshot from 2018-03-27 12-14-55.png > > > This issue was spotted during DROOLS-2392 review. > In special cases undo of delete relation column is not proper. > h2. Acceptance test > # Steps to reproduce fixed (/) > # Deletion is undone properly > ## Deletion of con. entry (/) > ## Deletion of Dec. table row (/) > ## Deletion of Dec. table column (x) > ## Deletion of Relation column > ## Deletion of Relation row > ## Deletion of Function parameter > # Clear of expression type is undone properly -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2439) Manage empty relation cell as null

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2439?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2439: ----------------------------------- Sprint: 2018 Week 13-14, 2018 Week 15-16 (was: 2018 Week 13-14) > Manage empty relation cell as null > ---------------------------------- > > Key: DROOLS-2439 > URL: https://issues.jboss.org/browse/DROOLS-2439 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Attachments: image-2018-03-30-09-38-46-944.png > > > In a relation containing empty cell > !image-2018-03-30-09-38-46-944.png! > manage empty cell as {{null}} expression -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2441) DMN runtime not using the kiecontainer root classloader to load classes

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2441?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2441: ----------------------------------- Sprint: 2018 Week 13-14, 2018 Week 15-16 (was: 2018 Week 13-14) > DMN runtime not using the kiecontainer root classloader to load classes > ----------------------------------------------------------------------- > > Key: DROOLS-2441 > URL: https://issues.jboss.org/browse/DROOLS-2441 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.6.0.Final > Reporter: Edson Tirelli > Assignee: Matteo Mortari > Priority: Blocker > Fix For: 7.8.0.Final > > Attachments: Standard Deviation.dmn, StandardDeviation.java > > > The FunctionDefNode is not using the kie container root classloader to load classes. I even added a comment for that, just a shame comments are not executable: > https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-feel/src/m... > {code:title=FunctionDefNode.java} > // might need to explicitly use a classloader here > Class<?> clazz = Class.forName( clazzName ); > {code} > To reproduce the problem, create a java class with a static method, add it to the kjar, create a DMN model that invokes that model, and try to execute. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2454) [DMN Designer] Decision content not visible after reopen

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2454?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2454: ----------------------------------- Sprint: 2018 Week 13-14, 2018 Week 15-16 (was: 2018 Week 13-14) > [DMN Designer] Decision content not visible after reopen > -------------------------------------------------------- > > Key: DROOLS-2454 > URL: https://issues.jboss.org/browse/DROOLS-2454 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Fix For: 7.8.0.Final > > Attachments: Screenshot from 2018-04-05 14-35-20.png, Screenshot from 2018-04-05 14-35-52.png > > > If the decision with bigger context table is reopened, its content is not visible. > h2. Acceptance test > In each scenario, width of columns don't have to be same as before closing, however each column should has some minimal/default width. > # Steps to reproduce fixed > # Define top level as Literal expression, reopen > # Define top level as Decision table, add columns, reopen > # Define top level as Relation, add columns, reopen > # Define top level as Invocation, specify complex parameters, reopen > # Define top level as Function, add a lot of parameters, reopen > # Define top level as Context, recursively add more Contexts, reopen -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 April 2018