[JBoss JIRA] (WFLY-13790) Memory leak caused by org.eclipse.yasson.internal.JsonBinding
by Alessio Soldano (Jira)
[ https://issues.redhat.com/browse/WFLY-13790?page=com.atlassian.jira.plugi... ]
Alessio Soldano reassigned WFLY-13790:
--------------------------------------
Assignee: r searls (was: Alessio Soldano)
> Memory leak caused by org.eclipse.yasson.internal.JsonBinding
> -------------------------------------------------------------
>
> Key: WFLY-13790
> URL: https://issues.redhat.com/browse/WFLY-13790
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 20.0.1.Final
> Reporter: Ahcene Kessal
> Assignee: r searls
> Priority: Major
>
> org.eclipse.yasson.internal.JsonBinding keeps a reference on an enum after the war is undeployed which results in a classloader leak.
> 1- Deploy the following application:
>
> {code:java}
> package au.com.spatiumxl.model;
> public class Book {
> public enum Status { READ, UNREAD }
> private String title;
> private Book.Status status;
> public Book(String title) {
> this.title = title;
> this.status = Book.Status.UNREAD;
> }
> public String getTitle() {
> return title;
> }
> public Book.Status getStatus() {
> return status;
> }
> }
> {code}
>
> {code:java}
> package au.com.spatiumxl.ejb;
> [...]
> import au.com.spatiumxl.model.Book;
> @Stateless
> @LocalBean
> public class BookService {
> public List<Book> getBooks() {
> List<Book> books = new ArrayList<>();
> books.add(new Book("title1"));
> return books;
> }
> }
> {code}
>
> {code:java}
> package au.com.spatiumxl.rest;
> [...]
> import au.com.spatiumxl.ejb.BookService;
> import au.com.spatiumxl.model.Book;
> @RequestScoped
> @Path("")public
> class BookEndPoint {
> @Inject BookService bookService;
> @GET @Path("/get-books")
> @Produces("application/json")
> public List<Book> getBooks() {
> return bookService.getBooks();
> }
> }
> {code}
>
> 2- On the browser go to: http://<host>/<context-root>/.../get-books
> 3- Undeploy the war
> 4- The memory analyser shows:
> {code:java}
> java.lang.Thread
> org.jboss.modules.ModuleClassLoader
> org.jboss.modules.Module
> org.jboss.modules.LocalModuleLoader
> java.util.concurrent.ConcurrentHashMap
> java.util.concurrent.ConcurrentHashMap$Node[]
> java.util.concurrent.ConcurrentHashMap$Node
> org.jboss.modules.ModuleLoader$FutureModule
> org.jboss.modules.Module
> org.jboss.modules.ModuleClassLoader
> java.util.Vector
> java.lang.Object[]
> org.jboss.resteasy.plugins.providers.jsonb.AbstractJsonBindingProvider
> org.eclipse.yasson.internal.JsonBinding
> org.eclipse.yasson.internal.JsonbContext
> org.eclipse.yasson.internal.MappingContext
> java.util.concurrent.ConcurrentHashMap
> java.util.concurrent.ConcurrentHashMap$Node[]
> java.util.concurrent.ConcurrentHashMap$Node
> org.eclipse.yasson.internal.model.ClassModel
> org.eclipse.yasson.internal.model.PropertyModel[]
> org.eclipse.yasson.internal.model.PropertyModel
> au.com.spatiumxl.model.Book$Status
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 8 months
[JBoss JIRA] (DROOLS-5649) [DMN XML] Signavio Profile - ZipFunction: parameter do not match
by Matteo Mortari (Jira)
[ https://issues.redhat.com/browse/DROOLS-5649?page=com.atlassian.jira.plug... ]
Matteo Mortari updated DROOLS-5649:
-----------------------------------
Component/s: dmn engine
> [DMN XML] Signavio Profile - ZipFunction: parameter do not match
> ----------------------------------------------------------------
>
> Key: DROOLS-5649
> URL: https://issues.redhat.com/browse/DROOLS-5649
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Reporter: Tommy Neubert
> Assignee: Matteo Mortari
> Priority: Minor
> Attachments: Screenshot 2020-09-17 at 16.18.25.png
>
>
> h2. 1. Synopsis
> In order to allow the execution of dmn.xml files exported by the Signavio Process Manager, the Signavio Profile ([https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-signavio|h...]) contains all custom made functions.
> The zip-function that is contained in this profile however expects its parameters in a different format then the Signavio Process Manager exports. This causes the parsing/execution of such dmn.xml files to fail. Customers have to manually adjust the xml file in order to get there executions running. This is both inconvenient and error prone and should be fixed.
> h2. 2. Technical Details
> As described above the parameters of the zip-function do not match
> Signavio Process Manager Export:
> {code:java}
> zip(["name", "age"], [names, ages]){code}
> Signavio Profiles expected parameters:
> {code:java}
> zip(["name", "age"], names, ages)
> {code}
> Codepointer:
> [https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-signavio/s...]
> h2. 3. Acceptance Criteria
> # zip-function exported by the Signavio Process Manager should be executable without manual adjustments
> # [backwards compatible]existing dmn.xml files (with manual adjustments) should still be exectuable
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 8 months
[JBoss JIRA] (DROOLS-5649) [DMN XML] Signavio Profile - ZipFunction: parameter do not match
by Matteo Mortari (Jira)
[ https://issues.redhat.com/browse/DROOLS-5649?page=com.atlassian.jira.plug... ]
Matteo Mortari updated DROOLS-5649:
-----------------------------------
Sprint: 2020 Week 37-39 (from Sep 7)
> [DMN XML] Signavio Profile - ZipFunction: parameter do not match
> ----------------------------------------------------------------
>
> Key: DROOLS-5649
> URL: https://issues.redhat.com/browse/DROOLS-5649
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Reporter: Tommy Neubert
> Assignee: Matteo Mortari
> Priority: Minor
> Attachments: Screenshot 2020-09-17 at 16.18.25.png
>
>
> h2. 1. Synopsis
> In order to allow the execution of dmn.xml files exported by the Signavio Process Manager, the Signavio Profile ([https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-signavio|h...]) contains all custom made functions.
> The zip-function that is contained in this profile however expects its parameters in a different format then the Signavio Process Manager exports. This causes the parsing/execution of such dmn.xml files to fail. Customers have to manually adjust the xml file in order to get there executions running. This is both inconvenient and error prone and should be fixed.
> h2. 2. Technical Details
> As described above the parameters of the zip-function do not match
> Signavio Process Manager Export:
> {code:java}
> zip(["name", "age"], [names, ages]){code}
> Signavio Profiles expected parameters:
> {code:java}
> zip(["name", "age"], names, ages)
> {code}
> Codepointer:
> [https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-signavio/s...]
> h2. 3. Acceptance Criteria
> # zip-function exported by the Signavio Process Manager should be executable without manual adjustments
> # [backwards compatible]existing dmn.xml files (with manual adjustments) should still be exectuable
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 8 months