November 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3423) Eliminate MSC service listeners usage in test suite

by Richard Opalka (JIRA)

Richard Opalka created WFCORE-3423: -------------------------------------- Summary: Eliminate MSC service listeners usage in test suite Key: WFCORE-3423 URL: https://issues.jboss.org/browse/WFCORE-3423 Project: WildFly Core Issue Type: Enhancement Components: Test Suite Affects Versions: 4.0.0.Alpha2 Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 4.0.0.Alpha3 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1447) Ensure the subject key identifier extension gets added if it isn't specified when generating a self-signed certificate

by Farah Juma (JIRA)

Farah Juma created ELY-1447: ------------------------------- Summary: Ensure the subject key identifier extension gets added if it isn't specified when generating a self-signed certificate Key: ELY-1447 URL: https://issues.jboss.org/browse/ELY-1447 Project: WildFly Elytron Issue Type: Bug Components: X.500 Reporter: Farah Juma Assignee: Farah Juma -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3422) OperationContextImpl.originalModel should be final

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-3422: ---------------------------------------- Summary: OperationContextImpl.originalModel should be final Key: WFCORE-3422 URL: https://issues.jboss.org/browse/WFCORE-3422 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor The original model is assigned in the constructor and should not be (and isn't) reassigned thereafter. "Bug" only in the sense of non-ideal code. There is no incorrect behavior resulting from this. -- 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 ehsavoie Hugonnet (JIRA)

ehsavoie Hugonnet created WFCORE-3421: ----------------------------------------- Summary: 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 Assignee: Darran Lofthouse 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] (WFLY-9073) Thread Leak in jboss-client on JMX remoting authentication failure

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9073?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-9073: -------------------------------------- Assignee: (was: Stuart Douglas) REMJMX-156 is the cloned issue. Since I believe Stuart was assigned to this just as the default assignee for "Application Client" component, that component isn't strongly involved, and I see no activity from him on this, I'm unassigning it. The real work would be on REMJMX-156. > 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: Application Client, 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] (REMJMX-156) Thread Leak in jboss-client on JMX remoting authentication failure

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/REMJMX-156?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-9555 to REMJMX-156: ----------------------------------------------- Project: Remoting JMX (was: WildFly) Key: REMJMX-156 (was: WFLY-9555) Workflow: classic default workflow (was: GIT Pull Request workflow ) Component/s: (was: Application Client) (was: JMX) Affects Version/s: (was: 10.1.0.Final) > Thread Leak in jboss-client on JMX remoting authentication failure > ------------------------------------------------------------------ > > Key: REMJMX-156 > URL: https://issues.jboss.org/browse/REMJMX-156 > Project: Remoting JMX > Issue Type: Bug > Reporter: Piotr Krokowski > Assignee: Stuart Douglas > 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] (REMJMX-156) Thread Leak in jboss-client on JMX remoting authentication failure

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/REMJMX-156?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned REMJMX-156: --------------------------------------- Assignee: Darran Lofthouse (was: Stuart Douglas) > Thread Leak in jboss-client on JMX remoting authentication failure > ------------------------------------------------------------------ > > Key: REMJMX-156 > URL: https://issues.jboss.org/browse/REMJMX-156 > Project: Remoting JMX > Issue Type: Bug > Reporter: Piotr Krokowski > Assignee: Darran Lofthouse > 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] (WFLY-9073) Thread Leak in jboss-client on JMX remoting authentication failure

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9073?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-9073: ---------------------------------------- I'm going to clone this and move the clone to the REMJMX project, as that's where the issue seems to be. > 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: Application Client, JMX > Affects Versions: 10.1.0.Final > Reporter: Piotr Krokowski > Assignee: Stuart Douglas > 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] (WFLY-9555) Thread Leak in jboss-client on JMX remoting authentication failure

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-9555: -------------------------------------- Summary: Thread Leak in jboss-client on JMX remoting authentication failure Key: WFLY-9555 URL: https://issues.jboss.org/browse/WFLY-9555 Project: WildFly Issue Type: Bug Components: Application Client, JMX Affects Versions: 10.1.0.Final Reporter: Piotr Krokowski Assignee: Stuart Douglas 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] (WFLY-9516) JPA deployer adding cross sub deployment dependencies when multiple persistence units deployed

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-9516?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-9516: ------------------------------------ >From jpa 2.1 spec, I think that it is correct to make subdeployment level persistence units available to other sub/top level deployments: {code} 8.2.2 Persistence Unit Scope An EJB-JAR, WAR, application client jar, or EAR can define a persistence unit. When referencing a persistence unit using the unitName annotation element or persistence-unit-name deployment descriptor element, the visibility scope of the persistence unit is determined by its point of definition: * A persistence unit that is defined at the level of an EJB-JAR, WAR, or application client jar is scoped to that EJB-JAR, WAR, or application jar respectively and is visible to the components defined in that jar or war. * A persistence unit that is defined at the level of the EAR is generally visible to all components in the application. However, if a persistence unit of the same name is defined by an EJB-JAR, WAR, or application jar file within the EAR, the persistence unit of that name defined at EAR level will not be visible to the components defined by that EJB-JAR, WAR, or application jar file unless the persistence unit reference uses the persistence unit name # syntax to specify a path name to disambiguate the reference. When the # syntax is used, the path name is relative to the referencing application component jar file. For example, the syntax ../lib/persistenceUnitRoot.jar#myPersistenceUnit refers to a persistence unit whose name, as specified in the name element of the persistence.xml file, is myPersistenceUnit and for which the relative path name of the root of the persistence unit is ../lib/persistenceUnitRoot.jar. The # syntax may be used with both the unitName annotation element or persistence-unit-name deployment descriptor element to reference a persistence unit defined at EAR level. {code} > JPA deployer adding cross sub deployment dependencies when multiple persistence units deployed > ---------------------------------------------------------------------------------------------- > > Key: WFLY-9516 > URL: https://issues.jboss.org/browse/WFLY-9516 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 11.0.0.Final > Reporter: Brad Maxwell > Assignee: Scott Marlow > > If an ear contains two EJB sub deployments which each contain a Persistence Unit and a Stateless EJB which injects the PU that is in its jar using @PersistenceContext. There is a dependency being added where in the Stateless EJB from one deployment depends on the PU from the other jar. It appears this is happening after this bug fix WFLY-1531 > {code} > app.ear > - ejb-with-pu1.jar > - ejb-with-pu2.jar > {code} -- 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