November 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9073) Thread Leak in jboss-client on JMX remoting authentication failure

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-9073?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-9073: ----------------------------------- Component/s: (was: Application Client) > Thread Leak in jboss-client on JMX remoting authentication failure > ------------------------------------------------------------------ > > Key: WFLY-9073 > URL: https://issues.jboss.org/browse/WFLY-9073 > Project: WildFly > Issue Type: Bug > Components: JMX > Affects Versions: 10.1.0.Final > Reporter: Piotr Krokowski > Attachments: JbossClientThreadLeakDemo.java, close.png > > > I've observed, that authentication failure, while connecting with jboss-client implementation of JMX remoting (remote+http) causes a thread leak. > Please find the attached code snippet to reproduce the faulty behavior. > The attached code produces following output in my case : > Thread count before starting: 2 > Active threads AFTER start: 2 > Connection failed. > Active threads AFTER after success: 7 > Connection failed. > Active threads AFTER after failure: 12 > Possible cause. > After an initial analisys I've observed that RemotingConnector.internalConnect throws an Exception, while having state set to UNUSED, while I'd actually expect it being set to OPEN, as connection and endpoint fields are already initialized. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3421) Incorrect usage of requires for defining the relationship between outflow-anonymous and outflow-security-domains

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3421?page=com.atlassian.jira.plugi... ] Darran Lofthouse commented on WFCORE-3421: ------------------------------------------ If setting it to the default value causes an error maybe we should just handle this within the domain management validation, this sounds like something easy to trigger elsewhere in the management model without adding custom validators all over the place. Alternatively maybe just accept setting this without an outflow domain means the attribute is ignored - no harm done so is the maintenance of an additional validator providing any real value? > Incorrect usage of requires for defining the relationship between outflow-anonymous and outflow-security-domains > ---------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-3421 > URL: https://issues.jboss.org/browse/WFCORE-3421 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 4.0.0.Alpha2 > Reporter: ehsavoie Hugonnet > > If outflow-anonymous is set to false then there is no need for outflow-security-domains as the default configuration shows clearly. > So /subsystem=elytron/security-domain=ApplicationDomain:add(default-realm=ApplicationRealm,outflow-anonymous=false,realms=[{realm=ApplicationRealm,role-decoder=groups-to-roles}]) should work like /subsystem=elytron/security-domain=ApplicationDomain:add(default-realm=ApplicationRealm,realms=[{realm=ApplicationRealm,role-decoder=groups-to-roles}]) > A custom validation code is required instead of relying on the setRequires of SimpleAttributeDefinition -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3421) Incorrect usage of requires for defining the relationship between outflow-anonymous and outflow-security-domains

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3421?page=com.atlassian.jira.plugi... ] Darran Lofthouse reassigned WFCORE-3421: ---------------------------------------- Assignee: (was: Darran Lofthouse) > Incorrect usage of requires for defining the relationship between outflow-anonymous and outflow-security-domains > ---------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-3421 > URL: https://issues.jboss.org/browse/WFCORE-3421 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 4.0.0.Alpha2 > Reporter: ehsavoie Hugonnet > > If outflow-anonymous is set to false then there is no need for outflow-security-domains as the default configuration shows clearly. > So /subsystem=elytron/security-domain=ApplicationDomain:add(default-realm=ApplicationRealm,outflow-anonymous=false,realms=[{realm=ApplicationRealm,role-decoder=groups-to-roles}]) should work like /subsystem=elytron/security-domain=ApplicationDomain:add(default-realm=ApplicationRealm,realms=[{realm=ApplicationRealm,role-decoder=groups-to-roles}]) > A custom validation code is required instead of relying on the setRequires of SimpleAttributeDefinition -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2141) [Guided Decision Table] Pinned mode indicator position wrong

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2141?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2141: -------------------------------- Tester: Jozef Marko > [Guided Decision Table] Pinned mode indicator position wrong > ------------------------------------------------------------ > > Key: DROOLS-2141 > URL: https://issues.jboss.org/browse/DROOLS-2141 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Reporter: Michael Anstis > Assignee: Guilherme Carreiro > Priority: Minor > Attachments: DROOLS-2141.png > > > The "pinned mode" indicator (following https://issues.jboss.org/browse/DROOLS-1828) is incorrect if the "description" column has been resized. See the attached. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2140) [Guided Decision Table] Dragging table should be disabled when pinned

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2140?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2140: -------------------------------- Tester: Jozef Marko > [Guided Decision Table] Dragging table should be disabled when pinned > --------------------------------------------------------------------- > > Key: DROOLS-2140 > URL: https://issues.jboss.org/browse/DROOLS-2140 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.4.1.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > > If you enter "pinned mode" it is still possible to drag the table using the "drag handle" (i.e. table name cell). This appears to be caused by {{GridWidgetDnDMouseMoveHandler.findGridColumn(...)}} that sets the DnD state to {{GRID_MOVE_PENDING}} when over the "drag handle" even if the table is "pinned". > Panning is OK. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2141) [Guided Decision Table] Pinned mode indicator position wrong

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2141?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2141: ----------------------------------- Attachment: DROOLS-2141.png > [Guided Decision Table] Pinned mode indicator position wrong > ------------------------------------------------------------ > > Key: DROOLS-2141 > URL: https://issues.jboss.org/browse/DROOLS-2141 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Reporter: Michael Anstis > Assignee: Guilherme Carreiro > Priority: Minor > Attachments: DROOLS-2141.png > > > The "pinned mode" indicator (following https://issues.jboss.org/browse/DROOLS-1828) is incorrect if the "description" column has been resized. See the attached. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2141) [Guided Decision Table] Pinned mode indicator position wrong

by Michael Anstis (JIRA)

Michael Anstis created DROOLS-2141: -------------------------------------- Summary: [Guided Decision Table] Pinned mode indicator position wrong Key: DROOLS-2141 URL: https://issues.jboss.org/browse/DROOLS-2141 Project: Drools Issue Type: Bug Components: Guided Decision Table Editor Reporter: Michael Anstis Assignee: Guilherme Carreiro Priority: Minor The "pinned mode" indicator (following https://issues.jboss.org/browse/DROOLS-1828) is incorrect if the "description" column has been resized. See the attached. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2140) [Guided Decision Table] Dragging table should be disabled when pinned

by Michael Anstis (JIRA)

Michael Anstis created DROOLS-2140: -------------------------------------- Summary: [Guided Decision Table] Dragging table should be disabled when pinned Key: DROOLS-2140 URL: https://issues.jboss.org/browse/DROOLS-2140 Project: Drools Issue Type: Bug Components: Guided Decision Table Editor Affects Versions: 7.4.1.Final Reporter: Michael Anstis Assignee: Michael Anstis If you enter "pinned mode" it is still possible to drag the table using the "drag handle" (i.e. table name cell). This appears to be caused by {{GridWidgetDnDMouseMoveHandler.findGridColumn(...)}} that sets the DnD state to {{GRID_MOVE_PENDING}} when over the "drag handle" even if the table is "pinned". Panning is OK. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1828) [Guided Decision Table] New Toolbar

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1828?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-1828: ---------------------------------------- [~jomarko] The general new asset toolbar is out of the scope of the specific Guided Decision Table changes. > [Guided Decision Table] New Toolbar > ----------------------------------- > > Key: DROOLS-1828 > URL: https://issues.jboss.org/browse/DROOLS-1828 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Reporter: Ivo Bek > Assignee: Guilherme Carreiro > Labels: UX > Fix For: 7.5.0.Final > > Attachments: Decision Table 1.png, Decision Table 2.png, DecisionTableColTab.png > > Original Estimate: 1 week > Remaining Estimate: 1 week > > We need a new toolbar of the buttons and tabs which contains the most commonly used actions and options, hide the advanced actions, remove unneeded buttons, and add new buttons such as "Add Row". > As part of the JIRA: > -Rename "otherwise" action in Edit menu to "All other" ([~stetson.robinson] did you come up with anything else?)- > [Moved to https://issues.jboss.org/browse/GUVNOR-3462] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2139) Test class CommonTestMethodBase extends Assert class

by Tibor Zimányi (JIRA)

Tibor Zimányi created DROOLS-2139: ------------------------------------- Summary: Test class CommonTestMethodBase extends Assert class Key: DROOLS-2139 URL: https://issues.jboss.org/browse/DROOLS-2139 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.4.1.Final Reporter: Tibor Zimányi Assignee: Tibor Zimányi Priority: Minor Fix For: 7.5.0.Final The parent test class for many Drools tests - CommonTestMethodBase extends Junit's Assert class. Assert class is a static util class which shouldn't be extended and static import should be used instead where needed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 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 November 2017