May 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2442) Performance tests

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2442?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2442: --------------------------- Fix Version/s: 5.0.0.Beta1 (was: 5.0.0.Alpha6) > Performance tests > ----------------- > > Key: JGRP-2442 > URL: https://issues.redhat.com/browse/JGRP-2442 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0.0.Beta1 > > > Run UPerf/MPerf before releasing 5.0.0.Final. > Performance should be slightly better due to reduced memory pressure (LongMessage, EmptyMessage, one less memory allocation)... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2407) CompositeMessage: collapse into BytesMessage at the receiver

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2407?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2407: --------------------------- Fix Version/s: 5.0.0.Beta1 (was: 5.0.0.Alpha6) > CompositeMessage: collapse into BytesMessage at the receiver > ------------------------------------------------------------ > > Key: JGRP-2407 > URL: https://issues.redhat.com/browse/JGRP-2407 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0.0.Beta1 > > > If a sender sends a CompositeMessage, say of an NioMessage of 500 bytes and a BytesMessage of 10 bytes, provide the option to unmarshal the message into a BytesMessage of 510 bytes at the receiver. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5293) can't create new user in the aplication

by Michael Biarnes Kiefer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5293?page=com.atlassian.jira.plug... ] Michael Biarnes Kiefer closed DROOLS-5293. ------------------------------------------ Resolution: Won't Fix > can't create new user in the aplication > --------------------------------------- > > Key: DROOLS-5293 > URL: https://issues.redhat.com/browse/DROOLS-5293 > Project: Drools > Issue Type: Bug > Reporter: Michael Biarnes Kiefer > Assignee: Mario Fusco > Priority: Major > > when deploying the [business-central.war|https://repository.jboss.org/nexus/content/groups/pu...] to a [Wildfly14|https://download.jboss.org/wildfly/14.0.1.Final/wildfly-14.0.1....] and create a user with ./add-user.sh (i.e. michael) and start the application you can login as user michael. > When the user michael (added as user a) Management user or b) Application user) adds in the application a user X with a pwd Y this user can't login. > Seems to wrok only for the very fist time you add a user with ./add-user. If you repeat this for adding more user this doesn't work. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5293) can't create new user in the aplication

by Michael Biarnes Kiefer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5293?page=com.atlassian.jira.plug... ] Michael Biarnes Kiefer commented on DROOLS-5293: ------------------------------------------------ this works - was because I maybe didn't remove the .niogit and .security - but building from scratch this worked - will close this JIRA > can't create new user in the aplication > --------------------------------------- > > Key: DROOLS-5293 > URL: https://issues.redhat.com/browse/DROOLS-5293 > Project: Drools > Issue Type: Bug > Reporter: Michael Biarnes Kiefer > Assignee: Mario Fusco > Priority: Major > > when deploying the [business-central.war|https://repository.jboss.org/nexus/content/groups/pu...] to a [Wildfly14|https://download.jboss.org/wildfly/14.0.1.Final/wildfly-14.0.1....] and create a user with ./add-user.sh (i.e. michael) and start the application you can login as user michael. > When the user michael (added as user a) Management user or b) Application user) adds in the application a user X with a pwd Y this user can't login. > Seems to wrok only for the very fist time you add a user with ./add-user. If you repeat this for adding more user this doesn't work. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2457) Make time and byte values more legible

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2457?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2457. ---------------------------- Resolution: Done > Make time and byte values more legible > -------------------------------------- > > Key: JGRP-2457 > URL: https://issues.redhat.com/browse/JGRP-2457 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 5.0.0.Alpha6 > > > In an XML configuration, we can already define {{send_buf_size=20M}}, but when printing protocol attribute values, we'll print {{20000000}} instead. > Change this to print time and bytes values in a more readable format, for all protocol attributes. > Examples: > * {{max_credits=3000000}} -> {{max_credits=3m}} // bytes > * {{time=45000}} -> {{time=45s}} // time > * {{avg_delivery_time=250.09us}} (note the suffix) // time > * {{number_of_blockings=234986}} -> {{number_of_blockings=234'986}} // scalar -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4136) R&D how to run scenario simulation tests inside VSCode

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4136?page=com.atlassian.jira.plug... ] Yeser Amer edited comment on DROOLS-4136 at 5/5/20 8:13 AM: ------------------------------------------------------------ [~ederign] I think we can consider this ticket solved, WDYT? was (Author: yamer): [~ederign] I think we can consider this ticket closed, WDYT? > R&D how to run scenario simulation tests inside VSCode > ------------------------------------------------------ > > Key: DROOLS-4136 > URL: https://issues.redhat.com/browse/DROOLS-4136 > Project: Drools > Issue Type: Task > Reporter: Eder Ignatowicz > Assignee: Yeser Amer > Priority: Major > > The main goal of this JIRA is to research what are the best approaches in order to run scenario simulation tests inside VSCode client-side only distribution. > Eder's first ideas: > [1] Run kie-server inside a docker image and run scenario tests via REST API > [2] Show the result of test execution inside scenario simulation editor > <add your idea here> > On future: [1] + investigate if it's possible to show tests execution results inside another junit vscode extension -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4136) R&D how to run scenario simulation tests inside VSCode

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4136?page=com.atlassian.jira.plug... ] Yeser Amer commented on DROOLS-4136: ------------------------------------ [~ederign] I think we can consider this ticket closed, WDYT? > R&D how to run scenario simulation tests inside VSCode > ------------------------------------------------------ > > Key: DROOLS-4136 > URL: https://issues.redhat.com/browse/DROOLS-4136 > Project: Drools > Issue Type: Task > Reporter: Eder Ignatowicz > Assignee: Yeser Amer > Priority: Major > > The main goal of this JIRA is to research what are the best approaches in order to run scenario simulation tests inside VSCode client-side only distribution. > Eder's first ideas: > [1] Run kie-server inside a docker image and run scenario tests via REST API > [2] Show the result of test execution inside scenario simulation editor > <add your idea here> > On future: [1] + investigate if it's possible to show tests execution results inside another junit vscode extension -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13141) JASPIC module's initialize() is called multiple times

by Moulali Shikalwadi (Jira)

[ https://issues.redhat.com/browse/WFLY-13141?page=com.atlassian.jira.plugi... ] Moulali Shikalwadi reassigned WFLY-13141: ----------------------------------------- Assignee: (was: Moulali Shikalwadi) > JASPIC module's initialize() is called multiple times > ----------------------------------------------------- > > Key: WFLY-13141 > URL: https://issues.redhat.com/browse/WFLY-13141 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 20.0.0.Beta1 > Reporter: Hisanobu Okuda > Priority: Major > Attachments: reproducer.tar.gz > > > JASPIC module's initialize() is called multiple times. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

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

by Sorin Potra (Jira)

[ https://issues.redhat.com/browse/WFLY-13259?page=com.atlassian.jira.plugi... ] Sorin Potra commented on WFLY-13259: ------------------------------------ [~smarlow] [~gbadner] I can try to disable the L2 cache on this particular flow as you suggested. However we are dealing with a large JEE application. It exposes around 150 services (EJBs) with thousands of operations (public methods). Identifying all the operations that exhibit this "import" pattern is a huge undertaking. We might have operations that do not cause OOM but still require more memory due to this behavior. Out clients might have to use large heap sizes to avoid issues in Production. The fact that, each time a new entity is persisted, the Hibernate session is leaked into the pending-puts cache for 60s seems not normal to me. If we have multiple transactions going on in parallel, each creating a new entity among other things, can lead to a huge number of Hibernate sessions hanging around until they are evicted from pending-puts cache. So we might have to stick with our workaround which basically removes the leaked pending-puts entry after each entity is persisted by calling PutFromLoadValidator.acquirePutFromLoadLock(). I noticed that the fix attempted tried to avoid the creation of the pending-put entry. But how about trying to remove the entry in case of new entities? This might be a silly suggestion as I don't have the knowledge to really asses if it is feasible. But the workaround that I did seems to be working (see JPAUtil.removePendingPutAfterCreate() in my test app) although it looks like a terrible hack as it uses non public APIs. > 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: Enhancement > Components: JPA / Hibernate > Affects Versions: 18.0.1.Final, 19.0.0.Final > Reporter: Sorin Potra > Assignee: Scott Marlow > Priority: Optional > Attachments: PathToGCRoots_strong_refs.PNG, afterOOM.hprof.zip, beforeOOM.hprof.zip, pending-puts-leak.PNG, simple-hibernate-war-client.zip, simple-hibernate-war-client.zip.2020-03-25, simple-hibernate-war.war, simple-hibernate-war.war.2020-03-25, simple-hibernate-war.zip, simple-hibernate-war.zip.2020-03-25 > > > 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
0
0 / 0

[JBoss JIRA] (DROOLS-5297) DMN small test reorganization

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-5297: -------------------------------------- Summary: DMN small test reorganization Key: DROOLS-5297 URL: https://issues.redhat.com/browse/DROOLS-5297 Project: Drools Issue Type: Task Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

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