August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-1004) Allow the ** role to be disabled

by Brad Maxwell (Jira)

Brad Maxwell created SECURITY-1004: -------------------------------------- Summary: Allow the ** role to be disabled Key: SECURITY-1004 URL: https://issues.jboss.org/browse/SECURITY-1004 Project: PicketBox Issue Type: Enhancement Components: JBossSX, Security-SPI Reporter: Brad Maxwell Assignee: Ilia Vassilev Allow the ** role to be disabled as it cause a performance degradation -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4399) KIE Server kie-server-7.24.0.Final-webc fails with ClassNotFoundException

by Simon Dallaway (Jira)

Simon Dallaway created DROOLS-4399: -------------------------------------- Summary: KIE Server kie-server-7.24.0.Final-webc fails with ClassNotFoundException Key: DROOLS-4399 URL: https://issues.jboss.org/browse/DROOLS-4399 Project: Drools Issue Type: Bug Components: kie server Affects Versions: 7.24.0.Final Environment: Windows 8.1 x64 Tomcat 9.0.16 Reporter: Simon Dallaway Assignee: Maciej Swiderski Attachments: catalina.2019-08-05.log, context.xml, libDir.txt, server.xml, setenv.bat, tomcat-users.xml, xa-recovery-properties.xml Attempting to deploy KIE Server on Tomcat 9 fails with a ClassNotFoundException org.jboss.narayana.tomcat.jta.NarayanaJtaServletContextListener when trying to setup application listener -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2364) simply lock and unlock JGroups lock repeatedly will create chaos

by Yong Deng (Jira)

[ https://issues.jboss.org/browse/JGRP-2364?page=com.atlassian.jira.plugin.... ] Yong Deng edited comment on JGRP-2364 at 8/3/19 10:42 AM: ---------------------------------------------------------- For your scenario step 4, _acquired_ and _denied_ were set to false, it will only affect ClientLock status. Before RELEASE_LOCK is processed by new coordinate B in step 5, no one would ever be able to acquire the lock X, right? Setting _acquired_ and _denied_ to false is a defensive fix. Without this defensive fix, in case RELEASE_LOCK_OK is never sent back, this client lock will stay locked status for ever. The same thread can acquire the lock even it did not acquire the lock from the coordinate. was (Author: dengyong): For your scenario step 4, _acquired_ and _denied _ were set to false, it will only affect ClientLock status. Before RELEASE_LOCK is processed by new coordinate B in step 5, no one would ever be able to acquire the lock X, right? Setting _acquired_ and _denied _ to false is a defensive fix. Without this defensive fix, in case RELEASE_LOCK_OK is never sent back, this client lock will stay locked status for ever. The same thread can acquire the lock even it did not acquire the lock from the coordinate. > simply lock and unlock JGroups lock repeatedly will create chaos > ---------------------------------------------------------------- > > Key: JGRP-2364 > URL: https://issues.jboss.org/browse/JGRP-2364 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.1.1 > Environment: JDK: 1.8 > JGroups: 4.1.1 > Lock: CENTRAL_LOCK > Reporter: Yong Deng > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.2 > > Attachments: LockSimpleTest.java > > > I have one simple use case to reproduce the issue. In same thread, just lock/unlock the lock repeatedly. Turn the log level to TRACE, you will find the communication chaos between the client and the coordinate. *JGroups unlock will return immediately after sending out RELEASE_LOCK currently. Why unlock don’t wait and only return after receiving the RELEASE_LOCK_OK response?* > * Current log: > {code:java} > 16:56:40,399 TRACE [CENTRAL_LOCK] A --> A: GRANT_LOCK[sample-lock, lock_id=1, owner=A::31, trylock, timeout=10000] > 16:56:40,404 TRACE [CENTRAL_LOCK] A <-- A: GRANT_LOCK[sample-lock, lock_id=1, owner=A::31, trylock, timeout=10000, sender=A] > 16:56:40,410 TRACE [CENTRAL_LOCK] A --> A: LOCK_GRANTED[sample-lock, lock_id=1, owner=A::31] > 16:56:40,411 TRACE [CENTRAL_LOCK] A <-- A: LOCK_GRANTED[sample-lock, lock_id=1, owner=A::31, sender=A] > 16:56:40,413 TRACE [CENTRAL_LOCK] A --> A: RELEASE_LOCK[sample-lock, lock_id=1, owner=A::31] > 16:56:40,414 TRACE [CENTRAL_LOCK] A <-- A: RELEASE_LOCK[sample-lock, lock_id=1, owner=A::31, sender=A] > 16:56:40,414 TRACE [CENTRAL_LOCK] A --> A: RELEASE_LOCK[sample-lock, lock_id=1, owner=A::31] > 16:56:40,415 TRACE [CENTRAL_LOCK] A --> A: RELEASE_LOCK_OK[sample-lock, lock_id=1, owner=A::31] > 16:56:40,415 TRACE [CENTRAL_LOCK] A --> A: RELEASE_LOCK[sample-lock, lock_id=1, owner=A::31] > {code} > * The expected log: > {code:java} > 2019-07-24 17:01:52,849 TRACE [org.jgroups.protocols.CENTRAL_LOCK] [A] --> [A] GRANT_LOCK [sample-lock, lock_id=1, owner=A::63, trylock (timeout=10000) > 2019-07-24 17:01:52,849 TRACE [org.jgroups.protocols.CENTRAL_LOCK] [A] <-- [A] GRANT_LOCK [sample-lock, lock_id=1, owner=A::63, trylock (timeout=10000) > 2019-07-24 17:01:52,852 TRACE [org.jgroups.protocols.CENTRAL_LOCK] [A] --> [A] LOCK_GRANTED [sample-lock, lock_id=1, owner=A::63 ] > 2019-07-24 17:01:52,852 TRACE [org.jgroups.protocols.CENTRAL_LOCK] [A] <-- [A] LOCK_GRANTED [sample-lock, lock_id=1, owner=A::63 ] > 2019-07-24 17:01:52,853 TRACE [org.jgroups.protocols.CENTRAL_LOCK] [A] --> [A] RELEASE_LOCK [sample-lock, lock_id=1, owner=A::63 ] > 2019-07-24 17:01:52,853 TRACE [org.jgroups.protocols.CENTRAL_LOCK] [A] <-- [A] RELEASE_LOCK [sample-lock, lock_id=1, owner=A::63 ] > 2019-07-24 17:01:52,853 TRACE [org.jgroups.protocols.CENTRAL_LOCK] [A] --> [A] RELEASE_LOCK_OK [sample-lock, lock_id=1, owner=A::63 ] > 2019-07-24 17:01:52,854 TRACE [org.jgroups.protocols.CENTRAL_LOCK] [A] <-- [A] RELEASE_LOCK_OK [sample-lock, lock_id=1, owner=A::63 ] > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2364) simply lock and unlock JGroups lock repeatedly will create chaos

by Yong Deng (Jira)

[ https://issues.jboss.org/browse/JGRP-2364?page=com.atlassian.jira.plugin.... ] Yong Deng commented on JGRP-2364: --------------------------------- For your scenario step 4, _acquired_ and _denied _ were set to false, it will only affect ClientLock status. Before RELEASE_LOCK is processed by new coordinate B in step 5, no one would ever be able to acquire the lock X, right? Setting _acquired_ and _denied _ to false is a defensive fix. Without this defensive fix, in case RELEASE_LOCK_OK is never sent back, this client lock will stay locked status for ever. The same thread can acquire the lock even it did not acquire the lock from the coordinate. > simply lock and unlock JGroups lock repeatedly will create chaos > ---------------------------------------------------------------- > > Key: JGRP-2364 > URL: https://issues.jboss.org/browse/JGRP-2364 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.1.1 > Environment: JDK: 1.8 > JGroups: 4.1.1 > Lock: CENTRAL_LOCK > Reporter: Yong Deng > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.2 > > Attachments: LockSimpleTest.java > > > I have one simple use case to reproduce the issue. In same thread, just lock/unlock the lock repeatedly. Turn the log level to TRACE, you will find the communication chaos between the client and the coordinate. *JGroups unlock will return immediately after sending out RELEASE_LOCK currently. Why unlock don’t wait and only return after receiving the RELEASE_LOCK_OK response?* > * Current log: > {code:java} > 16:56:40,399 TRACE [CENTRAL_LOCK] A --> A: GRANT_LOCK[sample-lock, lock_id=1, owner=A::31, trylock, timeout=10000] > 16:56:40,404 TRACE [CENTRAL_LOCK] A <-- A: GRANT_LOCK[sample-lock, lock_id=1, owner=A::31, trylock, timeout=10000, sender=A] > 16:56:40,410 TRACE [CENTRAL_LOCK] A --> A: LOCK_GRANTED[sample-lock, lock_id=1, owner=A::31] > 16:56:40,411 TRACE [CENTRAL_LOCK] A <-- A: LOCK_GRANTED[sample-lock, lock_id=1, owner=A::31, sender=A] > 16:56:40,413 TRACE [CENTRAL_LOCK] A --> A: RELEASE_LOCK[sample-lock, lock_id=1, owner=A::31] > 16:56:40,414 TRACE [CENTRAL_LOCK] A <-- A: RELEASE_LOCK[sample-lock, lock_id=1, owner=A::31, sender=A] > 16:56:40,414 TRACE [CENTRAL_LOCK] A --> A: RELEASE_LOCK[sample-lock, lock_id=1, owner=A::31] > 16:56:40,415 TRACE [CENTRAL_LOCK] A --> A: RELEASE_LOCK_OK[sample-lock, lock_id=1, owner=A::31] > 16:56:40,415 TRACE [CENTRAL_LOCK] A --> A: RELEASE_LOCK[sample-lock, lock_id=1, owner=A::31] > {code} > * The expected log: > {code:java} > 2019-07-24 17:01:52,849 TRACE [org.jgroups.protocols.CENTRAL_LOCK] [A] --> [A] GRANT_LOCK [sample-lock, lock_id=1, owner=A::63, trylock (timeout=10000) > 2019-07-24 17:01:52,849 TRACE [org.jgroups.protocols.CENTRAL_LOCK] [A] <-- [A] GRANT_LOCK [sample-lock, lock_id=1, owner=A::63, trylock (timeout=10000) > 2019-07-24 17:01:52,852 TRACE [org.jgroups.protocols.CENTRAL_LOCK] [A] --> [A] LOCK_GRANTED [sample-lock, lock_id=1, owner=A::63 ] > 2019-07-24 17:01:52,852 TRACE [org.jgroups.protocols.CENTRAL_LOCK] [A] <-- [A] LOCK_GRANTED [sample-lock, lock_id=1, owner=A::63 ] > 2019-07-24 17:01:52,853 TRACE [org.jgroups.protocols.CENTRAL_LOCK] [A] --> [A] RELEASE_LOCK [sample-lock, lock_id=1, owner=A::63 ] > 2019-07-24 17:01:52,853 TRACE [org.jgroups.protocols.CENTRAL_LOCK] [A] <-- [A] RELEASE_LOCK [sample-lock, lock_id=1, owner=A::63 ] > 2019-07-24 17:01:52,853 TRACE [org.jgroups.protocols.CENTRAL_LOCK] [A] --> [A] RELEASE_LOCK_OK [sample-lock, lock_id=1, owner=A::63 ] > 2019-07-24 17:01:52,854 TRACE [org.jgroups.protocols.CENTRAL_LOCK] [A] <-- [A] RELEASE_LOCK_OK [sample-lock, lock_id=1, owner=A::63 ] > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4395) [DMN Designer] Validation fails for included models

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4395?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-4395: ---------------------------------------- [~jomarko] I cannot read the screenshot very well however I suspect this is the same as a JIRA I reported that is assigned to Edson or Matteo. I believe there is a problem with the DRL used by the core DMN engine to perform validation. Sorry I cannot be more specific and link the JIRA at the moment. > [DMN Designer] Validation fails for included models > --------------------------------------------------- > > Key: DROOLS-4395 > URL: https://issues.jboss.org/browse/DROOLS-4395 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.25.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > Attachments: Screenshot from 2019-08-02 14-01-32.png > > > The attached screenshot shows an error coming from a dmn file that has a imported another dmn model. All dmn models with imported other models (dmn or pmml) throws an error during validation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12346) Testing adding an Elytron jdbc-realm in admin mode

by Ashley Abdel-Sayed (Jira)

[ https://issues.jboss.org/browse/WFLY-12346?page=com.atlassian.jira.plugin... ] Ashley Abdel-Sayed updated WFLY-12346: -------------------------------------- Summary: Testing adding an Elytron jdbc-realm in admin mode (was: Test to add Elytron jdbc-realm in admin mode) > Testing adding an Elytron jdbc-realm in admin mode > -------------------------------------------------- > > Key: WFLY-12346 > URL: https://issues.jboss.org/browse/WFLY-12346 > Project: WildFly > Issue Type: Task > Components: Security > Reporter: Ashley Abdel-Sayed > Assignee: Ashley Abdel-Sayed > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3126) DMN Editor/Test Scenarios design requirements (dev/UX)

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3126?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-3126: ------------------------------------------- [~Rikkola][~danielezonca] Can this be closed? > DMN Editor/Test Scenarios design requirements (dev/UX) > ------------------------------------------------------ > > Key: DROOLS-3126 > URL: https://issues.jboss.org/browse/DROOLS-3126 > Project: Drools > Issue Type: Epic > Components: DMN Editor, Scenario Simulation and Testing, Stunner > Reporter: Daniele Zonca > Assignee: Elizabeth Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UX-CSS, UXTeam, drools-tools > > User story: As a user of this feature I want a consistent user experience so I can move seamlessly between editors and product features. > *Table/grid visual styling*: > * align with DMN and GDT. Refer to related epic: https://issues.jboss.org/browse/DROOLS-2942 > * resolve table width issue. > * provide Table edit dropdown control. > *Docks/panels*: track enhancements with known issues in workbench, see linked jiras. > - For scenario specific bugs see: See https://issues.jboss.org/browse/DROOLS-3154 > - use docks component, (remove "hide right panel" button from toolbar): https://issues.jboss.org/browse/DROOLS-2869 > *Contextual menus & pop-overs* - verify cross product-feature alignment where applicable. > Working documented at: https://docs.google.com/document/d/1lHQ1mvmzQcgWbxwkBobIXb9mV6uM3RLbEll8-... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3240) Cross-editor UX Consistency

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3240?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-3240: -------------------------------------- Labels: UX UXTeam (was: UX) > Cross-editor UX Consistency > --------------------------- > > Key: DROOLS-3240 > URL: https://issues.jboss.org/browse/DROOLS-3240 > Project: Drools > Issue Type: Epic > Components: DMN Editor, Guided Decision Table Editor, Test Scenarios Editor > Reporter: Ivo Bek > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam > > We have quite a few tasks to ensure UX consistency across multiple editors - DMN Modeler, Guided Decision Tables, Test Scenario tool, etc. > This epic links to and oversee such UX work efforts so that the scrum teams are aware of the changes that will make all the editors consistent. > https://docs.google.com/document/d/1ZXlOjR-bI-Bkkusn-CA3f-0ILyyh8tSZY1hg5... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3954) DM UX solutions for communicating errors in graphs & grids.

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3954?page=com.atlassian.jira.plugi... ] Elizabeth Clayton reassigned DROOLS-3954: ----------------------------------------- Assignee: Margot Menestrot (was: Tao Zhu) > DM UX solutions for communicating errors in graphs & grids. > ------------------------------------------------------------ > > Key: DROOLS-3954 > URL: https://issues.jboss.org/browse/DROOLS-3954 > Project: Drools > Issue Type: Epic > Components: DMN Editor, Scenario Simulation and Testing > Reporter: Elizabeth Clayton > Assignee: Margot Menestrot > Priority: Major > Labels: ScenarioSimulation, Stunner, UX, UXTeam, drools-tools > > Scenario and DMN editors share design solutions for displaying errors in graphs (models) and grids (scenario test, dmn boxed expressions.) Support design consistency where applicable, while also documenting unique solutions per context. > Current DM context specific "design pattern" document: https://docs.google.com/document/d/1fX9K_fDjEO4_wDLK9EDDb0OtEFir7S6nFH9cn... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-916) E2E - External Service TC Bug

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-916?page=com.atlassian.jira.plugin.... ] Matthew Mahoney deleted SWSQE-916: ---------------------------------- > E2E - External Service TC Bug > ----------------------------- > > Key: SWSQE-916 > URL: https://issues.jboss.org/browse/SWSQE-916 > Project: Kiali QE > Issue Type: Bug > Reporter: Matthew Mahoney > Assignee: Matthew Mahoney > Priority: Minor > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 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 August 2019