March 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5195) Review modules in droolsjbpm-integration and eventually remove the no longer supported ones

by Mario Fusco (Jira)

Mario Fusco created DROOLS-5195: ----------------------------------- Summary: Review modules in droolsjbpm-integration and eventually remove the no longer supported ones Key: DROOLS-5195 URL: https://issues.redhat.com/browse/DROOLS-5195 Project: Drools Issue Type: Task Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13286) Messages are being added to topic even if there are no subscribers

by James Perkins (Jira)

James Perkins created WFLY-13286: ------------------------------------ Summary: Messages are being added to topic even if there are no subscribers Key: WFLY-13286 URL: https://issues.redhat.com/browse/WFLY-13286 Project: WildFly Issue Type: Bug Components: JMS Affects Versions: 19.0.0.Final Reporter: Emmanuel Hugonnet Assignee: Emmanuel Hugonnet Fix For: 20.0.0.Beta1 After applying EAP 7.2 Update 7 , messages seem to be added to a topic even when there are no subscribers on the topic. When subscribers are attached to a topic they seem to consume messages from a topic but the messages is not removed from the underlying physical queue resulting in the destination growing indefinitely in size. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13284) Fix incorrect method call in EJB3IIOPResource write-attribute handler

by Richard Achmatowicz (Jira)

[ https://issues.redhat.com/browse/WFLY-13284?page=com.atlassian.jira.plugi... ] Richard Achmatowicz commented on WFLY-13284: -------------------------------------------- Thanks, Brian. Apologies. > Fix incorrect method call in EJB3IIOPResource write-attribute handler > --------------------------------------------------------------------- > > Key: WFLY-13284 > URL: https://issues.redhat.com/browse/WFLY-13284 > Project: WildFly > Issue Type: Bug > Components: EJB, IIOP > Affects Versions: 19.0.0.Final > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Priority: Major > Fix For: 20.0.0.Beta1 > > > In the write-attribute handler for the ENABLE_BY_DEFAULT attribute, the wrong method is being called when adjusting the Runtime service to reflect the change to the attribute value. This was due to an inadvertent error when setting up write handlers for two attributes. In short, in the write handler for ENABLE_BY_DEFAULT: > {noformat} > service.setUseQualifiedName(value); > {noformat} > should be > {noformat} > service.setEnableByDefault(value); > {noformat} > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4746) UX for DMN "quick test" tool

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-4746?page=com.atlassian.jira.plug... ] Elizabeth Clayton updated DROOLS-4746: -------------------------------------- Sprint: 2020 Week 13-15 (from Mar 23) > UX for DMN "quick test" tool > ---------------------------- > > Key: DROOLS-4746 > URL: https://issues.redhat.com/browse/DROOLS-4746 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > > As a DMN author, I'd like to probe the DMN model during the authoring phase without leaving the DMN Editor. Actually, it's really important to explore the DMN model to understand with values are required by the test. > When the user run the test he can get back the results of the DMN execution. > Moreover, it would be handy to add those input/output to an existing (or new) test scenario. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4746) UX for DMN "quick test" tool

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-4746?page=com.atlassian.jira.plug... ] Elizabeth Clayton updated DROOLS-4746: -------------------------------------- Story Points: 8 (was: 5) > UX for DMN "quick test" tool > ---------------------------- > > Key: DROOLS-4746 > URL: https://issues.redhat.com/browse/DROOLS-4746 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > > As a DMN author, I'd like to probe the DMN model during the authoring phase without leaving the DMN Editor. Actually, it's really important to explore the DMN model to understand with values are required by the test. > When the user run the test he can get back the results of the DMN execution. > Moreover, it would be handy to add those input/output to an existing (or new) test scenario. -- 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: ------------------------------------- [~rvansa] have you heard of any problems with the pending_puts cache causing OOM failures? Is there a trace log setting that would help tell if the wrong key is used when attempting to remove entries from the pending_puts cache? >From the last comment, it sounds like this problem only started with the Hibernate 5.3 release (in WildFly 13, running in EE 8 mode, it doesn't recreate with Hibernate 5.1 in WildFly 13, in EE 7 mode). > 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, 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 month

1
0
0 / 0

[JBoss JIRA] (ELY-1948) wildfly-elytron HTTP JWT Bearer realm CORS

by Jan Bárta (Jira)

[ https://issues.redhat.com/browse/ELY-1948?page=com.atlassian.jira.plugin.... ] Jan Bárta commented on ELY-1948: -------------------------------- Understand. Thanks for reponse. I changed issue as "Feature Request". > wildfly-elytron HTTP JWT Bearer realm CORS > ------------------------------------------ > > Key: ELY-1948 > URL: https://issues.redhat.com/browse/ELY-1948 > Project: WildFly Elytron > Issue Type: Feature Request > Reporter: Jan Bárta > Assignee: Darran Lofthouse > Priority: Optional > > Hi, > i found possible problem with HTTP Bearer JWT. > If you need create dynamically CORS by +own policy JAXRS filter+, then it will be problem with expired/invalid (any other problem) JWT token. You will see CORS exception on expired/invalid JWT because wildfly-elytron refuse request before own policy JAXRS filters (as e.g. @PreMatching ContainerRequestFilter, ContainerResponseFilter). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1948) wildfly-elytron HTTP JWT Bearer realm CORS

by Jan Bárta (Jira)

[ https://issues.redhat.com/browse/ELY-1948?page=com.atlassian.jira.plugin.... ] Jan Bárta edited comment on ELY-1948 at 3/25/20 8:48 AM: --------------------------------------------------------- Understand. Thanks for response. I changed issue as "Feature Request". was (Author: janbarta): Understand. Thanks for reponse. I changed issue as "Feature Request". > wildfly-elytron HTTP JWT Bearer realm CORS > ------------------------------------------ > > Key: ELY-1948 > URL: https://issues.redhat.com/browse/ELY-1948 > Project: WildFly Elytron > Issue Type: Feature Request > Reporter: Jan Bárta > Assignee: Darran Lofthouse > Priority: Optional > > Hi, > i found possible problem with HTTP Bearer JWT. > If you need create dynamically CORS by +own policy JAXRS filter+, then it will be problem with expired/invalid (any other problem) JWT token. You will see CORS exception on expired/invalid JWT because wildfly-elytron refuse request before own policy JAXRS filters (as e.g. @PreMatching ContainerRequestFilter, ContainerResponseFilter). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1948) wildfly-elytron HTTP JWT Bearer realm CORS

by Jan Bárta (Jira)

[ https://issues.redhat.com/browse/ELY-1948?page=com.atlassian.jira.plugin.... ] Jan Bárta updated ELY-1948: --------------------------- Issue Type: Feature Request (was: Bug) > wildfly-elytron HTTP JWT Bearer realm CORS > ------------------------------------------ > > Key: ELY-1948 > URL: https://issues.redhat.com/browse/ELY-1948 > Project: WildFly Elytron > Issue Type: Feature Request > Reporter: Jan Bárta > Assignee: Darran Lofthouse > Priority: Optional > > Hi, > i found possible problem with HTTP Bearer JWT. > If you need create dynamically CORS by +own policy JAXRS filter+, then it will be problem with expired/invalid (any other problem) JWT token. You will see CORS exception on expired/invalid JWT because wildfly-elytron refuse request before own policy JAXRS filters (as e.g. @PreMatching ContainerRequestFilter, ContainerResponseFilter). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1948) wildfly-elytron HTTP JWT Bearer realm CORS

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELY-1948?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on ELY-1948: --------------------------------------- I think this will always be the nature of custom filters vs server managed authentication, the authentication will always occur before the request is allowed through and be turned around if it fails. Having said that specific support for CORS before authentication may be a valid feature request. > wildfly-elytron HTTP JWT Bearer realm CORS > ------------------------------------------ > > Key: ELY-1948 > URL: https://issues.redhat.com/browse/ELY-1948 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Jan Bárta > Assignee: Darran Lofthouse > Priority: Optional > > Hi, > i found possible problem with HTTP Bearer JWT. > If you need create dynamically CORS by +own policy JAXRS filter+, then it will be problem with expired/invalid (any other problem) JWT token. You will see CORS exception on expired/invalid JWT because wildfly-elytron refuse request before own policy JAXRS filters (as e.g. @PreMatching ContainerRequestFilter, ContainerResponseFilter). -- 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