January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4367) Tests in drools coverage are not really using the executable model

by Tibor Zimanyi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4367?page=com.atlassian.jira.plug... ] Tibor Zimanyi updated DROOLS-4367: ---------------------------------- Sprint: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9) (was: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > Tests in drools coverage are not really using the executable model > ------------------------------------------------------------------ > > Key: DROOLS-4367 > URL: https://issues.redhat.com/browse/DROOLS-4367 > Project: Drools > Issue Type: Bug > Reporter: Luca Molteni > Assignee: Tibor Zimanyi > Priority: Minor > > Such as > https://github.com/kiegroup/drools/blob/ba9c79c4bfaf9cfc1ec2363bee3865c3d... > Even if the test itself is parametrized, in the body it calls directly buildAll therefore discarding the executable model -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-298) Full reload is needed after microprofile-jwt-smallrye subsystem removal

by Jan Kasik (Jira)

[ https://issues.redhat.com/browse/WFWIP-298?page=com.atlassian.jira.plugin... ] Jan Kasik updated WFWIP-298: ---------------------------- Affects: User Experience > Full reload is needed after microprofile-jwt-smallrye subsystem removal > ----------------------------------------------------------------------- > > Key: WFWIP-298 > URL: https://issues.redhat.com/browse/WFWIP-298 > Project: WildFly WIP > Issue Type: Bug > Components: MP JWT > Reporter: Jan Kasik > Assignee: Darran Lofthouse > Priority: Major > > When user is removing MP subsystem, full reload is required. This is partly a benefit because it provides a fast fail solution for deployments which requires classes from this subsystem. On the other hand, reload might not be feasible for user under in their current conditions. This is why it has to be reduced as much as possible. > Is there other way to provide fast fail without requiring full reload? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-482) Add log4j2 support for WildFly

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFCORE-482?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-482: -------------------------------------- It definitely will have a dependency and ship a forked version of log4j v1 for a while. At least I don't see it being removed in the near future. > Add log4j2 support for WildFly > ------------------------------ > > Key: WFCORE-482 > URL: https://issues.redhat.com/browse/WFCORE-482 > Project: WildFly Core > Issue Type: Task > Components: Logging > Environment: Spring 3, Hibernate, Wicket, JBoss AS7 > Reporter: Amarkanth Ranganamayna > Assignee: James Perkins > Priority: Major > > I am trying to use Flume Appender which comes with Log4j2 (log4j 1.x doesn't support flume appender) (AND) inorder to acheive this, I am looking at how to configure JBoss AS7 to use log4j2. > Looks like Jboss AS7 by default use log4j 1.x > Are you guys already working on using log4j2 ? > If NOT, can you please suggest how to configure Jboss AS7 such that it picks up "log4j2.xml" file and doesn't use its own logging. > Thanks, > Amar -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-482) Add log4j2 support for WildFly

by Andrew Marlow (Jira)

[ https://issues.redhat.com/browse/WFCORE-482?page=com.atlassian.jira.plugi... ] Andrew Marlow commented on WFCORE-482: -------------------------------------- Running the maven dependency analyser on the latest wildly shows that it still depends on log4j-v1. Andrew marlow http://www.andrewpetermarlow.co.uk > Add log4j2 support for WildFly > ------------------------------ > > Key: WFCORE-482 > URL: https://issues.redhat.com/browse/WFCORE-482 > Project: WildFly Core > Issue Type: Task > Components: Logging > Environment: Spring 3, Hibernate, Wicket, JBoss AS7 > Reporter: Amarkanth Ranganamayna > Assignee: James Perkins > Priority: Major > > I am trying to use Flume Appender which comes with Log4j2 (log4j 1.x doesn't support flume appender) (AND) inorder to acheive this, I am looking at how to configure JBoss AS7 to use log4j2. > Looks like Jboss AS7 by default use log4j 1.x > Are you guys already working on using log4j2 ? > If NOT, can you please suggest how to configure Jboss AS7 such that it picks up "log4j2.xml" file and doesn't use its own logging. > Thanks, > Amar -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4930) [DMN Designer] Remove UUID from Alerts panel validation messages

by Edson Tirelli (Jira)

[ https://issues.redhat.com/browse/DROOLS-4930?page=com.atlassian.jira.plug... ] Edson Tirelli commented on DROOLS-4930: --------------------------------------- either removal or at least split them into a separate column to avoid messing with the human readable message. > [DMN Designer] Remove UUID from Alerts panel validation messages > ----------------------------------------------------------------- > > Key: DROOLS-4930 > URL: https://issues.redhat.com/browse/DROOLS-4930 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.31.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > Validation of a DMN diagram can lead to messages being shown in the Alerts Panel. > Stunner is appending the UUID to the message. See [CoreTranslationMessages.getElementValidationMessage()|https://github.com/...] > [~tirelli] has requested their removal. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-482) Add log4j2 support for WildFly

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFCORE-482?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-482: -------------------------------------- [~walkerca] that has already been resolved for WildFly with this PR https://github.com/jboss-logging/log4j-jboss-logmanager/pull/15. > Add log4j2 support for WildFly > ------------------------------ > > Key: WFCORE-482 > URL: https://issues.redhat.com/browse/WFCORE-482 > Project: WildFly Core > Issue Type: Task > Components: Logging > Environment: Spring 3, Hibernate, Wicket, JBoss AS7 > Reporter: Amarkanth Ranganamayna > Assignee: James Perkins > Priority: Major > > I am trying to use Flume Appender which comes with Log4j2 (log4j 1.x doesn't support flume appender) (AND) inorder to acheive this, I am looking at how to configure JBoss AS7 to use log4j2. > Looks like Jboss AS7 by default use log4j 1.x > Are you guys already working on using log4j2 ? > If NOT, can you please suggest how to configure Jboss AS7 such that it picks up "log4j2.xml" file and doesn't use its own logging. > Thanks, > Amar -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12926) Upgrade Infinispan to 9.4.18.Final

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-12926?page=com.atlassian.jira.plugi... ] Paul Ferraro commented on WFLY-12926: ------------------------------------- [~ivassile] 9.4.18.Final is not yet been released. > Upgrade Infinispan to 9.4.18.Final > ---------------------------------- > > Key: WFLY-12926 > URL: https://issues.redhat.com/browse/WFLY-12926 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System, Clustering > Affects Versions: 18.0.1.Final > Reporter: Chao Wang > Assignee: Paul Ferraro > Priority: Major > Labels: downstream_dependency > > https://issues.redhat.com/projects/ISPN/versions/12343651 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

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 04-06 (from Jan 20) > 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, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12836) Large allocations in EJBContextImpl#isCallerInRole

by Ashley Abdel-Sayed (Jira)

[ https://issues.redhat.com/browse/WFLY-12836?page=com.atlassian.jira.plugi... ] Ashley Abdel-Sayed reassigned WFLY-12836: ----------------------------------------- Assignee: Ashley Abdel-Sayed (was: Cheng Fang) > Large allocations in EJBContextImpl#isCallerInRole > -------------------------------------------------- > > Key: WFLY-12836 > URL: https://issues.redhat.com/browse/WFLY-12836 > Project: WildFly > Issue Type: Bug > Components: EJB, Security > Affects Versions: 18.0.1.Final > Reporter: Philippe Marschall > Assignee: Ashley Abdel-Sayed > Priority: Major > Attachments: elytron_allocations_redacted.PNG > > > In our application we have the need to know the roles of the current user. We would like to do this using Java / Jakarta EE APIs rather than rely on WildFly implementation classes. We do this by iterating over all roles, which we know statically, and calling {{EJBContext#isCallerInRole}} for each one. This seem to be a common technique, see [How to get user roles in a JSP / Servlet|https://stackoverflow.com/questions/344117/how-to-get-user-roles-...]. > That's about 100 roles for us. We were expecting that would be a lookup into a {{HashMap}} or similar with O(1) complexity and almost no allocations. > This however does not seem to be case as {{EJBContextImpl#isCallerInRole}} seems to do the role mapping for every call. This results in a large amount of allocations. In our case this completely dominates our allocation profile. See attached screenshot from JFR. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4529) BPMN processes don't work when CanonicalKieModule is used

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4529?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-4529: -------------------------------- Fix Version/s: 7.28.0.Final (was: 7.27.0.Final) > BPMN processes don't work when CanonicalKieModule is used > --------------------------------------------------------- > > Key: DROOLS-4529 > URL: https://issues.redhat.com/browse/DROOLS-4529 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.26.0.Final > Reporter: Tibor Zimanyi > Assignee: Tibor Zimanyi > Priority: Major > Fix For: 7.28.0.Final > > > When using executable model in a kjar that contains BPMN process definitions in the form of bpmn files, the processes don't work. > To reproduce the problem, run RuleFlowIntegrationTest [1], with executable model enabled in the ruleflow-group kjar. > [1] https://github.com/kiegroup/droolsjbpm-integration/blob/78cb770577679cb46... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

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