February 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2241) Mem Leak in CLI class

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2241?page=com.atlassian.jira.plugi... ] Jean-Francois Denise edited comment on WFCORE-2241 at 2/7/17 12:02 PM: ----------------------------------------------------------------------- A branch has been created to implement this change: https://github.com/jfdenise/wildfly-core/tree/cli_new_threading Testing jobs: https://ci.wildfly.org/viewLog.html?buildId=44476&tab=buildResultsDiv&bui... https://ci.wildfly.org/viewLog.html?buildId=44485&tab=buildResultsDiv&bui... https://ci.wildfly.org/viewLog.html?buildId=44523&tab=buildResultsDiv&bui... was (Author: jdenise): A branch has been created to implement this change: https://github.com/jfdenise/wildfly-core/tree/cli_new_threading Testing jobs: https://ci.wildfly.org/viewLog.html?buildId=44476&tab=buildResultsDiv&bui... https://ci.wildfly.org/viewLog.html?buildId=44485&tab=buildResultsDiv&bui... > Mem Leak in CLI class > --------------------- > > Key: WFCORE-2241 > URL: https://issues.jboss.org/browse/WFCORE-2241 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > Fix For: 3.0.0.Alpha23 > > > The CLI class offline CommandContext is never terminated. This makes the CommandContext to be referenced from Shutdown Hook and never cleaned. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2241) Mem Leak in CLI class

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2241?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-2241: ---------------------------------------------- A branch has been created to implement this change: https://github.com/jfdenise/wildfly-core/tree/cli_new_threading Testing jobs: https://ci.wildfly.org/viewLog.html?buildId=44476&tab=buildResultsDiv&bui... https://ci.wildfly.org/viewLog.html?buildId=44485&tab=buildResultsDiv&bui... > Mem Leak in CLI class > --------------------- > > Key: WFCORE-2241 > URL: https://issues.jboss.org/browse/WFCORE-2241 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > Fix For: 3.0.0.Alpha23 > > > The CLI class offline CommandContext is never terminated. This makes the CommandContext to be referenced from Shutdown Hook and never cleaned. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2271) CLI should use Endpoint executor

by Jean-Francois Denise (JIRA)

Jean-Francois Denise created WFCORE-2271: -------------------------------------------- Summary: CLI should use Endpoint executor Key: WFCORE-2271 URL: https://issues.jboss.org/browse/WFCORE-2271 Project: WildFly Core Issue Type: Enhancement Components: CLI Reporter: Jean-Francois Denise Assignee: Jean-Francois Denise Today the 16 threads (default value) of the ThreadPool attached to the Endpoint are started and never used (except during connection of Controller client). CLI, instead of instantiating and managing its own Executor, it should re-use the XNIO one and configure its size the way the CLI custom one does. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-919) Coverity: default platform encoding used in DefaultSingleSignOnSessionFactory

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-919?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-919: --------------------------------- Fix Version/s: 1.1.0.Beta23 > Coverity: default platform encoding used in DefaultSingleSignOnSessionFactory > ----------------------------------------------------------------------------- > > Key: ELY-919 > URL: https://issues.jboss.org/browse/ELY-919 > Project: WildFly Elytron > Issue Type: Bug > Components: HTTP > Affects Versions: 1.1.0.Beta21 > Reporter: Martin Choma > Assignee: Ilia Vassilev > Priority: Critical > Fix For: 1.1.0.Beta23 > > > Coverity static-analysis scan found a String to byte conversion (4xoccurences of {{getBytes()}}) with default platform encoding in the DefaultSingleSignOnSessionFactory method. > Following code > {code:java|title=DefaultSingleSignOnSessionFactory.java} > @Override > public String createLogoutParameter(String sessionId) { > try { > Signature signature = Signature.getInstance(DEFAULT_SIGNATURE_ALGORITHM); > signature.initSign(this.privateKey); > Base64.Encoder urlEncoder = Base64.getUrlEncoder(); > return sessionId + "." + ByteIterator.ofBytes(urlEncoder.encode(ByteIterator.ofBytes(sessionId.getBytes()).sign(signature).drain())).asUtf8String().drainToString(); > } catch (NoSuchAlgorithmException | InvalidKeyException e) { > throw new IllegalStateException(e); > } > } > > @Override > public String verifyLogoutParameter(String parameter) { > String[] parts = parameter.split("\\."); > if (parts.length != 2) { > throw new IllegalArgumentException(parameter); > } > try { > String localSessionId = ByteIterator.ofBytes(parts[0].getBytes()).asUtf8String().drainToString(); > Signature signature = Signature.getInstance(DEFAULT_SIGNATURE_ALGORITHM); > signature.initVerify(this.certificate); > signature.update(localSessionId.getBytes()); > Base64.Decoder urlDecoder = Base64.getUrlDecoder(); > if (!ByteIterator.ofBytes(urlDecoder.decode(parts[1].getBytes())).verify(signature)) { > throw log.httpMechSsoInvalidLogoutMessage(localSessionId); > } > return localSessionId; > } catch (NoSuchAlgorithmException | InvalidKeyException e) { > throw new IllegalStateException(e); > } catch (SignatureException e) { > throw new IllegalArgumentException(parameter, e); > } > } > {code} > The encoding should be specified as argument. > Setting with high priority, because once default platform encoding UTF-16 will be set, funcionality do not need to work as intended. Especially when combined with {{asUtf8String()}}, which implies specifying default encoding UTF-8. > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=86758... > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=86758... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-923) Elytron LDAP caching realm should cache attributes and credentials

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-923?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse reassigned ELY-923: ------------------------------------ Assignee: Jan Kalina > Elytron LDAP caching realm should cache attributes and credentials > ------------------------------------------------------------------ > > Key: ELY-923 > URL: https://issues.jboss.org/browse/ELY-923 > Project: WildFly Elytron > Issue Type: Bug > Components: Realms > Affects Versions: 1.1.0.Beta21 > Reporter: Ondrej Kotek > Assignee: Jan Kalina > Priority: Blocker > > Elytron {{caching-realm}} backed by {{ldap-realm}} provides caching for identity objects but not for related credentials and attributes. This is currently due to design of {{ldap-realm}} (like in case of {{filesystem-realm}}, see ELY-915). > Credentials and attributes should not be loaded from LDAP for a cache hit. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2151) Client is unable to connect to remote+http://localhost:9990 intermittently (the connection timed out)

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2151?page=com.atlassian.jira.plugi... ] Jean-Francois Denise resolved WFCORE-2151. ------------------------------------------ Release Notes Text: This was caused by WFCORE-2241 Resolution: Duplicate Issue > Client is unable to connect to remote+http://localhost:9990 intermittently (the connection timed out) > ----------------------------------------------------------------------------------------------------- > > Key: WFCORE-2151 > URL: https://issues.jboss.org/browse/WFCORE-2151 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Remoting > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > Making it a CLI issue for now although I suspect a remoting one. I am running reproducer with traces enabled. Hope to get something. Only managed to reproduce once with 2 millions connect./disconnect but without traces enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-903) Missing some role assignment for Elytron ldap-realm when role and user are members of the same role

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-903?page=com.atlassian.jira.plugin.sy... ] Jan Kalina edited comment on ELY-903 at 2/7/17 10:26 AM: --------------------------------------------------------- Probably problem: realm find R1, find it role R2 and its role R3 - add all of them to the set of already added groups. When later found R2, it does not find its roles, as it was already added... Max depth is by random of ways to the node, not by shortest way to the node - need to change algorithm of duplicities prevention. was (Author: honza889): Probably problem: realm find R1, find it role R2 and its role R3 - add all of them to the set of already added groups. When later found R2, it does not find its roles, as it was already added... > Missing some role assignment for Elytron ldap-realm when role and user are members of the same role > --------------------------------------------------------------------------------------------------- > > Key: ELY-903 > URL: https://issues.jboss.org/browse/ELY-903 > Project: WildFly Elytron > Issue Type: Bug > Components: Realms > Affects Versions: 1.1.0.Beta21 > Reporter: Ondrej Lukas > Assignee: Jan Kalina > Priority: Critical > Attachments: print-roles.war > > > In case when role recursion is configured for ldap-realm and given LDAP includes some role which has member some user and also another role, then some roles are intermittently not assigned. See Steps to Reproduce for more details about configuration. > Most important part of ldif for reproduction is following: > {code} > dn: cn=R1,ou=Roles,dc=jboss,dc=org > objectclass: top > objectclass: groupOfNames > cn: R1 > member: uid=jduke,ou=People,dc=jboss,dc=org > description: the R1 group > dn: cn=R2,ou=Roles,dc=jboss,dc=org > objectclass: top > objectclass: groupOfNames > cn: R2 > member: uid=jduke,ou=People,dc=jboss,dc=org > member: cn=R1,ou=Roles,dc=jboss,dc=org > description: the R2 group > dn: cn=R3,ou=Roles,dc=jboss,dc=org > objectclass: top > objectclass: groupOfNames > cn: R3 > member: cn=R2,ou=Roles,dc=jboss,dc=org > description: the R3 group > {code} > User jduke is direct member of roles R1 and R2. However role R2 is also member of role R1. In case when {{ldap-realm.identity-mapping.attribute-mapping.role-recursion}} is configured to {{2}}, then sometimes only roles R1, R2 and R3 are assigned (and role R4 is missing). > The same behavior occurs when role mapping is configured in application server in opposite way (principal to group mapping which uses memberOf attribute). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-903) Missing some role assignment for Elytron ldap-realm when role and user are members of the same role

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-903?page=com.atlassian.jira.plugin.sy... ] Jan Kalina commented on ELY-903: -------------------------------- Probably problem: realm find R1, find it role R2 and its role R3 - add all of them to the set of already added groups. When later found R2, it does not find its roles, as it was already added... > Missing some role assignment for Elytron ldap-realm when role and user are members of the same role > --------------------------------------------------------------------------------------------------- > > Key: ELY-903 > URL: https://issues.jboss.org/browse/ELY-903 > Project: WildFly Elytron > Issue Type: Bug > Components: Realms > Affects Versions: 1.1.0.Beta21 > Reporter: Ondrej Lukas > Assignee: Jan Kalina > Priority: Critical > Attachments: print-roles.war > > > In case when role recursion is configured for ldap-realm and given LDAP includes some role which has member some user and also another role, then some roles are intermittently not assigned. See Steps to Reproduce for more details about configuration. > Most important part of ldif for reproduction is following: > {code} > dn: cn=R1,ou=Roles,dc=jboss,dc=org > objectclass: top > objectclass: groupOfNames > cn: R1 > member: uid=jduke,ou=People,dc=jboss,dc=org > description: the R1 group > dn: cn=R2,ou=Roles,dc=jboss,dc=org > objectclass: top > objectclass: groupOfNames > cn: R2 > member: uid=jduke,ou=People,dc=jboss,dc=org > member: cn=R1,ou=Roles,dc=jboss,dc=org > description: the R2 group > dn: cn=R3,ou=Roles,dc=jboss,dc=org > objectclass: top > objectclass: groupOfNames > cn: R3 > member: cn=R2,ou=Roles,dc=jboss,dc=org > description: the R3 group > {code} > User jduke is direct member of roles R1 and R2. However role R2 is also member of role R1. In case when {{ldap-realm.identity-mapping.attribute-mapping.role-recursion}} is configured to {{2}}, then sometimes only roles R1, R2 and R3 are assigned (and role R4 is missing). > The same behavior occurs when role mapping is configured in application server in opposite way (principal to group mapping which uses memberOf attribute). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8050) Upgrade Artemis to 1.5.1.jbossorg-002

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-8050?page=com.atlassian.jira.plugin.... ] Jeff Mesnil moved JBEAP-8711 to WFLY-8050: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8050 (was: JBEAP-8711) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: ActiveMQ) (was: JMS) > Upgrade Artemis to 1.5.1.jbossorg-002 > ------------------------------------- > > Key: WFLY-8050 > URL: https://issues.jboss.org/browse/WFLY-8050 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > > (note that it might be possible that we upgrade to Artemis upstream 1.5.3 instead of 1.5.1.jbossorg-002). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8049) Update Artemis SQL statements

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-8049: --------------------------------- Summary: Update Artemis SQL statements Key: WFLY-8049 URL: https://issues.jboss.org/browse/WFLY-8049 Project: WildFly Issue Type: Bug Components: JMS Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 11.0.0.Alpha1 After ARTEMIS-938, SQL statements for Artemis JDBC store uses BIGINT for ids instead of INT. The SQL statement used by WildFly (in modules/system/layers/base/org/wildfly/extension/messaging-activemq/main/database/journal-sql.properties) must be updated to also use BIGINT -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 February 2017