December 2020 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (DROOLS-5909) [DMN Designer] Not able to auto update decision table inputs when a new input added in its DMN model

by Shahzad Raza (Jira)

[ https://issues.redhat.com/browse/DROOLS-5909?page=com.atlassian.jira.plug... ] Shahzad Raza updated DROOLS-5909: --------------------------------- Attachment: DMN-File .dmn > [DMN Designer] Not able to auto update decision table inputs when a new input added in its DMN model > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-5909 > URL: https://issues.redhat.com/browse/DROOLS-5909 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.31.0.Final > Reporter: Shahzad Raza > Assignee: Guilherme Gomes > Priority: Critical > Labels: drools-tools > Attachments: DMN-File .dmn > > > With the attached DMN model, user is unable to do changes and save them. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5908) NPE in IntervalTrigger when timestamp + delay > endTime

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5908?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-5908: -------------------------------- Sprint: 2020 Week 49-51 (from Nov 30) > NPE in IntervalTrigger when timestamp + delay > endTime > ------------------------------------------------------- > > Key: DROOLS-5908 > URL: https://issues.redhat.com/browse/DROOLS-5908 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.47.0.Final > Reporter: Thomas Huriaux > Assignee: Mario Fusco > Priority: Minor > > If using timer(expr: $d, $p; end=$e) with $e > now + $d > We have the following stack trace: > {code:java} > Exception in thread "Thread-1" java.lang.NullPointerException: Cannot invoke "java.util.Date.getTime()" because "this.nextFireTime" is null at org.drools.core.time.impl.IntervalTrigger.getTimeAfter(IntervalTrigger.java:224) > {code} > It should probably just not fire anything in that situation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5909) [DMN Designer] Not able to auto update decision table inputs when a new input added in its DMN model

by Shahzad Raza (Jira)

Shahzad Raza created DROOLS-5909: ------------------------------------ Summary: [DMN Designer] Not able to auto update decision table inputs when a new input added in its DMN model Key: DROOLS-5909 URL: https://issues.redhat.com/browse/DROOLS-5909 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.31.0.Final Reporter: Shahzad Raza Assignee: Guilherme Gomes With the attached DMN model, user is unable to do changes and save them. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1257) Get list of SM image shas installed on the cluster

by Filip Brychta (Jira)

Filip Brychta created SWSQE-1257: ------------------------------------ Summary: Get list of SM image shas installed on the cluster Key: SWSQE-1257 URL: https://issues.redhat.com/browse/SWSQE-1257 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta When installing SM on cluster, different catalog sources might be used and it's easy to do a mistake. We need something which will list actually installed images so we can easily compare that we are testing expected payload. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5559) Kie-workbench and kie-server going OOM with subsequent build and deployment

by Sachin Kamath (Jira)

[ https://issues.redhat.com/browse/DROOLS-5559?page=com.atlassian.jira.plug... ] Sachin Kamath updated DROOLS-5559: ---------------------------------- Labels: DecisionTables Excel (was: ) > Kie-workbench and kie-server going OOM with subsequent build and deployment > --------------------------------------------------------------------------- > > Key: DROOLS-5559 > URL: https://issues.redhat.com/browse/DROOLS-5559 > Project: Drools > Issue Type: Bug > Components: Examples (Workbench), kie server > Affects Versions: 7.31.0.Final > Reporter: Sachin Kamath > Assignee: David Gutierrez > Priority: Critical > Labels: DecisionTables, Excel > > Hi Team, > We are using kie-workbench and kie-server for managing the rules using decision table spreadsheet. What we see is that, with continuous build and deployments being done, the servers are going out of memory. This is resulting in instability of the environment and frequent restarts are required to fix the issue. > Here are the parameters: > *kie-workbench* : > Xms: 20G > Xmx: 20G > Metaspace Xmx:8G Xms:8G > Using G1GC algorithm. > *kie-server:* > Xms: 4G > Xmx: 4G > Metaspace: Xmx:2G Xms:2G > Using G1GC algorithm. > *Steps for replication :* > # Excel sheet has 50k rows. > # Build the artifacts and deploy with version V1. The first deployment would be successful. > # Change the version to V2 and deploy once again. Now we will have version V1 and V2 both in the kie-servers but V2 would be serving he requests. > # Before deploying version V3, remove version V1. Build and deploy V3. > # Now when deploying version V4, after removing the version V2, the kie-servers are going out of memory. > Even though we are making sure that only last 2 valid versions are present, the servers are going out of memory. After restarting the servers, the last two valid versions V3 and V4 are successfully deployed again. The error in kie-servers clearly says Java heap space issue. But the point here is, it is fine after restart. I could sense there is some other problem. With visual VM, i could see that the memory consumption gradually increases with deployment of different versions but its not released as we remove the old version. > Any pointers would be helpful here. > Im really unsure if its a bug or im missing some parameters around it. > > Thanks > Sachin > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5908) NPE in IntervalTrigger when timestamp + delay > endTime

by Thomas Huriaux (Jira)

[ https://issues.redhat.com/browse/DROOLS-5908?page=com.atlassian.jira.plug... ] Thomas Huriaux updated DROOLS-5908: ----------------------------------- Description: If using timer(expr: $d, $p; end=$e) with $e > now + $d We have the following stack trace: {code:java} Exception in thread "Thread-1" java.lang.NullPointerException: Cannot invoke "java.util.Date.getTime()" because "this.nextFireTime" is null at org.drools.core.time.impl.IntervalTrigger.getTimeAfter(IntervalTrigger.java:224) {code} It should probably just not fire anything in that situation. was: If using timer(expr: $d, $p; end=$e) with $e > now + $d We have the following stack trace: {code:java} Exception in thread "Thread-1" java.lang.NullPointerException: Cannot invoke "java.util.Date.getTime()" because "this.nextFireTime" is nullException in thread "Thread-1" java.lang.NullPointerException: Cannot invoke "java.util.Date.getTime()" because "this.nextFireTime" is null at org.drools.core.time.impl.IntervalTrigger.getTimeAfter(IntervalTrigger.java:224) {code} It should probably just not fire anything in that situation. > NPE in IntervalTrigger when timestamp + delay > endTime > ------------------------------------------------------- > > Key: DROOLS-5908 > URL: https://issues.redhat.com/browse/DROOLS-5908 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.47.0.Final > Reporter: Thomas Huriaux > Assignee: Mario Fusco > Priority: Minor > > If using timer(expr: $d, $p; end=$e) with $e > now + $d > We have the following stack trace: > {code:java} > Exception in thread "Thread-1" java.lang.NullPointerException: Cannot invoke "java.util.Date.getTime()" because "this.nextFireTime" is null at org.drools.core.time.impl.IntervalTrigger.getTimeAfter(IntervalTrigger.java:224) > {code} > It should probably just not fire anything in that situation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5908) NPE in IntervalTrigger when timestamp + delay > endTime

by Thomas Huriaux (Jira)

Thomas Huriaux created DROOLS-5908: -------------------------------------- Summary: NPE in IntervalTrigger when timestamp + delay > endTime Key: DROOLS-5908 URL: https://issues.redhat.com/browse/DROOLS-5908 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.47.0.Final Reporter: Thomas Huriaux Assignee: Mario Fusco If using timer(expr: $d, $p; end=$e) with $e > now + $d We have the following stack trace: {code:java} Exception in thread "Thread-1" java.lang.NullPointerException: Cannot invoke "java.util.Date.getTime()" because "this.nextFireTime" is nullException in thread "Thread-1" java.lang.NullPointerException: Cannot invoke "java.util.Date.getTime()" because "this.nextFireTime" is null at org.drools.core.time.impl.IntervalTrigger.getTimeAfter(IntervalTrigger.java:224) {code} It should probably just not fire anything in that situation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13538) Add Java 9+ version of ConcurrentDirectDeque

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13538?page=com.atlassian.jira.plugi... ] Paul Ferraro commented on WFLY-13538: ------------------------------------- This should have been resolved. Will fix. > Add Java 9+ version of ConcurrentDirectDeque > -------------------------------------------- > > Key: WFLY-13538 > URL: https://issues.redhat.com/browse/WFLY-13538 > Project: WildFly > Issue Type: Task > Components: Clustering > Affects Versions: 20.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > The clustering code uses ConcurrentDirectDeque for its local scheduler implementation. While a portable implementation exists, a faster implementation that relies on sun.misc.Unsafe will be used when running with a compatible JVM. > Now that jboss-parent includes profiles for multi-release jars, we can add a fast implementation (ported from Undertow) that uses VarHandle that will work on all Java9+ JVMs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14137) Typo in JWT_CAPABILITY_NAME

by Petr Beran (Jira)

[ https://issues.redhat.com/browse/WFLY-14137?page=com.atlassian.jira.plugi... ] Petr Beran reassigned WFLY-14137: --------------------------------- Assignee: Petr Beran (was: Darran Lofthouse) > Typo in JWT_CAPABILITY_NAME > --------------------------- > > Key: WFLY-14137 > URL: https://issues.redhat.com/browse/WFLY-14137 > Project: WildFly > Issue Type: Bug > Components: MP JWT > Reporter: Brian Stansberry > Assignee: Petr Beran > Priority: Minor > > static final String JWT_CAPABILITY_NAME = "org.wildlfly.microprofile.jwt"; > The 'wildfly' has an extra 'l'. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14241) [GSS](7.3.z) The messageID cannot be used in a filter expressing via JBoss CLI

by Ranabir Chakraborty (Jira)

[ https://issues.redhat.com/browse/WFLY-14241?page=com.atlassian.jira.plugi... ] Ranabir Chakraborty moved JBEAP-20738 to WFLY-14241: ---------------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-14241 (was: JBEAP-20738) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: JMS) Affects Version/s: 22.0.0.Beta1 (was: 7.3.4.GA) Fix Version/s: (was: 7.3.6.GA) > [GSS](7.3.z) The messageID cannot be used in a filter expressing via JBoss CLI > ------------------------------------------------------------------------------ > > Key: WFLY-14241 > URL: https://issues.redhat.com/browse/WFLY-14241 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 22.0.0.Beta1 > Reporter: Ranabir Chakraborty > Assignee: Ranabir Chakraborty > Priority: Major > > The messageID header property holds a java.lang.Long value, however, it is not possible to use filter operators on the messageID header property. > For example, the following expression would not work besides messageID in each message was greater than '0'. > [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/jms-queue=A:count-messages(filter="messageID>0") > -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 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 December 2020