March 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4984) Enable the executable model in Optaplanner

by Lukáš Petrovický (Jira)

[ https://issues.redhat.com/browse/DROOLS-4984?page=com.atlassian.jira.plug... ] Lukáš Petrovický resolved DROOLS-4984. -------------------------------------- Fix Version/s: 7.35.0.Final Resolution: Done The PR was recently merged. > Enable the executable model in Optaplanner > ------------------------------------------ > > Key: DROOLS-4984 > URL: https://issues.redhat.com/browse/DROOLS-4984 > Project: Drools > Issue Type: Bug > Components: executable model > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > Fix For: 7.35.0.Final > > > Currently it's disabled -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13259) Memory leak in Hibernate pending-puts cache when L2 cache is enabled

by Scott Marlow (Jira)

[ https://issues.redhat.com/browse/WFLY-13259?page=com.atlassian.jira.plugi... ] Scott Marlow commented on WFLY-13259: ------------------------------------- The attached test does seem to run easily enough, so created a local heapdump in MAT also. > Memory leak in Hibernate pending-puts cache when L2 cache is enabled > -------------------------------------------------------------------- > > Key: WFLY-13259 > URL: https://issues.redhat.com/browse/WFLY-13259 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 18.0.1.Final, 19.0.0.Final > Reporter: Sorin Potra > Assignee: Scott Marlow > Priority: Critical > Attachments: PathToGCRoots_strong_refs.PNG, pending-puts-leak.PNG, simple-hibernate-war-client.zip, simple-hibernate-war.war, simple-hibernate-war.zip > > > Under certain conditions, described below, WildFly / Hibernate can leak memory into the pending-puts cache eventually causing an OutOfMemoryError. Attached you can find a web application and a standalone client that can be used to reproduce the problem. The web app defines two entities: a Parent and a Child. There is a bidirectional one-to-many relationship between the Parent and the Child. JPA L2 cache is enabled (Infinispan is the cache provider). > Repeatedly executing a transaction that creates a new Child and adds it to the list of children in the Parent will cause the memory usage to increase steadily until OOM is encountered. If the execution of these transactions is stopped before reaching OOM, the memory will be reclaimed after a few minutes of inactivity. > Attached you can find the following: > - simple-hibernate-war.war - the web app that can be deployed in WildFly to reproduce the issue. > - simple-hibernate-war.zip - the source code for the above web app. The servlet that is invoked by the client to create and persist a new Child is com.microfocus.sa.web.AddChildServlet > - simple-hibernate-war-client.zip - the standalone client that can be used to invoke the AddChildServlet. After unzipping the archive, the client can be run with the following command from the client folder: > > java -cp bin com.microfocus.sa.client.AddChildClient > > If you need to run the client multiple times, you have to restart WildFly in between the runs, to start from a fresh state (the web app uses the h2 in memory databasewhich is reset at each restart). > - pending-puts-leak.PNG - a screeshot from Memory Analyzer showing a leaked SessionImpl instance -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13259) Memory leak in Hibernate pending-puts cache when L2 cache is enabled

by Scott Marlow (Jira)

[ https://issues.redhat.com/browse/WFLY-13259?page=com.atlassian.jira.plugi... ] Scott Marlow commented on WFLY-13259: ------------------------------------- >From your description: {quote} Repeatedly executing a transaction that creates a new Child and adds it to the list of children in the Parent will cause the memory usage to increase steadily until OOM is encountered. If the execution of these transactions is stopped before reaching OOM, the memory will be reclaimed after a few minutes of inactivity. {quote} Obviously, in your real application, you have this occurring as its part of your design, likely for many different items being added to the list of children, which reflects what you are actually doing. Correct me if I am wrong or not describing this correctly. I assume you are doing some extensive in-memory processing and relying on the cache, to avoid re-loading of the database items, to enhance performance during this long processing. Sound close? Also, regarding the wetransfer.com exchange of heap dump, I don't have an account on that. Is the zipped up heapdump too large to attach to this jira? Scott > Memory leak in Hibernate pending-puts cache when L2 cache is enabled > -------------------------------------------------------------------- > > Key: WFLY-13259 > URL: https://issues.redhat.com/browse/WFLY-13259 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 18.0.1.Final, 19.0.0.Final > Reporter: Sorin Potra > Assignee: Scott Marlow > Priority: Critical > Attachments: PathToGCRoots_strong_refs.PNG, pending-puts-leak.PNG, simple-hibernate-war-client.zip, simple-hibernate-war.war, simple-hibernate-war.zip > > > Under certain conditions, described below, WildFly / Hibernate can leak memory into the pending-puts cache eventually causing an OutOfMemoryError. Attached you can find a web application and a standalone client that can be used to reproduce the problem. The web app defines two entities: a Parent and a Child. There is a bidirectional one-to-many relationship between the Parent and the Child. JPA L2 cache is enabled (Infinispan is the cache provider). > Repeatedly executing a transaction that creates a new Child and adds it to the list of children in the Parent will cause the memory usage to increase steadily until OOM is encountered. If the execution of these transactions is stopped before reaching OOM, the memory will be reclaimed after a few minutes of inactivity. > Attached you can find the following: > - simple-hibernate-war.war - the web app that can be deployed in WildFly to reproduce the issue. > - simple-hibernate-war.zip - the source code for the above web app. The servlet that is invoked by the client to create and persist a new Child is com.microfocus.sa.web.AddChildServlet > - simple-hibernate-war-client.zip - the standalone client that can be used to invoke the AddChildServlet. After unzipping the archive, the client can be run with the following command from the client folder: > > java -cp bin com.microfocus.sa.client.AddChildClient > > If you need to run the client multiple times, you have to restart WildFly in between the runs, to start from a fresh state (the web app uses the h2 in memory databasewhich is reset at each restart). > - pending-puts-leak.PNG - a screeshot from Memory Analyzer showing a leaked SessionImpl instance -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4562) DMN validation semantic rules for DMNDI

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4562?page=com.atlassian.jira.plug... ] Toshiya Kobayashi reassigned DROOLS-4562: ----------------------------------------- Assignee: Toshiya Kobayashi (was: Matteo Mortari) > DMN validation semantic rules for DMNDI > --------------------------------------- > > Key: DROOLS-4562 > URL: https://issues.redhat.com/browse/DROOLS-4562 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Toshiya Kobayashi > Priority: Major > Labels: good-first-issue > > Provide rules for the -validator module which can semantically inspect the DMNDI element to ensure the minimal requirements from the DMN specification are (semantically) respected in the .dmn xml file. > These rules can be implemented in the subset of the KB for the DMN v1.2 and greater, to leverage use of the standard DMNDI elements. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4562) DMN validation semantic rules for DMNDI

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4562?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-4562: -------------------------------------- Sprint: 2020 Week 13-15 (from Mar 23) > DMN validation semantic rules for DMNDI > --------------------------------------- > > Key: DROOLS-4562 > URL: https://issues.redhat.com/browse/DROOLS-4562 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Toshiya Kobayashi > Priority: Major > Labels: good-first-issue > > Provide rules for the -validator module which can semantically inspect the DMNDI element to ensure the minimal requirements from the DMN specification are (semantically) respected in the .dmn xml file. > These rules can be implemented in the subset of the KB for the DMN v1.2 and greater, to leverage use of the standard DMNDI elements. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5191) Automate with ansible Kogito deploy on CRC

by Massimiliano Dessi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5191?page=com.atlassian.jira.plug... ] Massimiliano Dessi updated DROOLS-5191: --------------------------------------- Summary: Automate with ansible Kogito deploy on CRC (was: Automate with ansible Kogito deploy o CRC) > Automate with ansible Kogito deploy on CRC > ------------------------------------------ > > Key: DROOLS-5191 > URL: https://issues.redhat.com/browse/DROOLS-5191 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4916) Investigate modify parsing bug in executable model

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4916?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-4916: -------------------------------------- Sprint: 2020 Week 13-15 (from Mar 23) > Investigate modify parsing bug in executable model > -------------------------------------------------- > > Key: DROOLS-4916 > URL: https://issues.redhat.com/browse/DROOLS-4916 > Project: Drools > Issue Type: Bug > Components: executable model > Reporter: Luca Molteni > Assignee: Toshiya Kobayashi > Priority: Major > Labels: good-first-issue > > declare Application > categories : Set = new HashSet() > Then I had a modify statement scattered about: > modify ($a) { > $a.getCategories().add("hello"); > } > The ExecutableModel did not seem to like any of those. I changed it to: > $a.getCategories().add("hello"); > update($a); -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5149) Able to specify a releaseId with KieHelper

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5149?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5149: -------------------------------------- Sprint: 2020 Week 13-15 (from Mar 23) > Able to specify a releaseId with KieHelper > ------------------------------------------ > > Key: DROOLS-5149 > URL: https://issues.redhat.com/browse/DROOLS-5149 > Project: Drools > Issue Type: Enhancement > Components: core engine > Affects Versions: 7.34.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > KieHelper builds a KieModule with a default releaseId org.default:artifact:1.0.0 and we cannot change it. It could be an issue when testing with multithread. > This JIRA is to add a method to specify a releaseId. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5191) Automate with ansible Kogito deploy o CRC

by Massimiliano Dessi (Jira)

Massimiliano Dessi created DROOLS-5191: ------------------------------------------ Summary: Automate with ansible Kogito deploy o CRC Key: DROOLS-5191 URL: https://issues.redhat.com/browse/DROOLS-5191 Project: Drools Issue Type: Task Reporter: Massimiliano Dessi Assignee: Massimiliano Dessi -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5191) Automate with ansible Kogito deploy o CRC

by Massimiliano Dessi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5191?page=com.atlassian.jira.plug... ] Massimiliano Dessi commented on DROOLS-5191: -------------------------------------------- https://github.com/desmax74/openshift-kogito-automation > Automate with ansible Kogito deploy o CRC > ----------------------------------------- > > Key: DROOLS-5191 > URL: https://issues.redhat.com/browse/DROOLS-5191 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

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 March 2020