May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3855) Upgrade to Galleon 1.0.0.CR3 and plugins 1.0.0.CR5

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3855?page=com.atlassian.jira.plugi... ] Alexey Loubyansky updated WFCORE-3855: -------------------------------------- Summary: Upgrade to Galleon 1.0.0.CR3 and plugins 1.0.0.CR5 (was: Upgrade to Galleon 1.0.0.CR3 and plugins 1.0.0.CR4) > Upgrade to Galleon 1.0.0.CR3 and plugins 1.0.0.CR5 > -------------------------------------------------- > > Key: WFCORE-3855 > URL: https://issues.jboss.org/browse/WFCORE-3855 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Build System > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > > 1.0.0.CR3 fixes a file descriptor leak as a consequence of not properly closed file writer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3855) Upgrade to Galleon 1.0.0.CR3 and plugins 1.0.0.CR4

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3855?page=com.atlassian.jira.plugi... ] Alexey Loubyansky updated WFCORE-3855: -------------------------------------- Component/s: Build System (was: Server) > Upgrade to Galleon 1.0.0.CR3 and plugins 1.0.0.CR4 > -------------------------------------------------- > > Key: WFCORE-3855 > URL: https://issues.jboss.org/browse/WFCORE-3855 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Build System > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > > 1.0.0.CR3 fixes a file descriptor leak as a consequence of not properly closed file writer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3855) Upgrade to Galleon 1.0.0.CR3 and plugins 1.0.0.CR4

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created WFCORE-3855: ----------------------------------------- Summary: Upgrade to Galleon 1.0.0.CR3 and plugins 1.0.0.CR4 Key: WFCORE-3855 URL: https://issues.jboss.org/browse/WFCORE-3855 Project: WildFly Core Issue Type: Component Upgrade Components: Server Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky 1.0.0.CR3 fixes a file descriptor leak as a consequence of not properly closed file writer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3852) Incomplete attribute name in error message of ObjectFieldsRejectAttributeChecker

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3852?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3852: ------------------------------------- Issue Type: Enhancement (was: Bug) Priority: Minor (was: Major) This is an enhancement request, not a bug. It's not a bug because this message is quite correct: {code} WFLYCTL0302: The following attributes are not understood in the target model version and this resource will need to be ignored on the target host: [principal-query] {code} The message doesn't say the attribute can't be defined, it says it's not understood. Which is true; the value isn't understood. Being more precise about exactly what's not understood is an enhancement. TBH it's probably luck that the wording covers this case correctly, but sometimes we get lucky! :) > Incomplete attribute name in error message of ObjectFieldsRejectAttributeChecker > -------------------------------------------------------------------------------- > > Key: WFCORE-3852 > URL: https://issues.jboss.org/browse/WFCORE-3852 > Project: WildFly Core > Issue Type: Enhancement > Components: Management > Affects Versions: 5.0.0.Beta1 > Reporter: Jan Kalina > Priority: Minor > Labels: domain-mode, transformers > > When defined ObjectFieldsRejectAttributeChecker (or ListRejectAttributeChecker or their combination) in transformers, the error message is missleading - points to the complex attribute instead of individual subattributes: > {code} > WFLYCTL0297: Transforming operation { > \"address\" => [ > (\"profile\" => \"full\"), > (\"subsystem\" => \"elytron\"), > (\"jdbc-realm\" => \"xxxx\") > ], > \"operation\" => \"add\", > \"principal-query\" => [{ > \"data-source\" => \"ExampleDS\", > \"sql\" => \"SEL\", > \"scram-mapper\" => { > \"iteration-count-index\" => \"1\", > \"password-index\" => \"2\", > \"salt-index\" => \"5\", > \"hash-encoding\" => \"base64\" // this attribute is not backward compatible > } > }], > \"operation-headers\" => { > \"caller-type\" => \"user\", > \"access-mechanism\" => \"NATIVE\", > \"domain-uuid\" => \"658c12cc-9501-47d0-bf24-aa11079e444a\", > \"execute-for-coordinator\" => true, > \"domain-controller-lock-id\" => -1163262107 > } > } at resource [ > (\"profile\" => \"full\"), > (\"subsystem\" => \"elytron\"), > (\"jdbc-realm\" => \"xxxx\") > ] to subsystem 'elytron' model version '2.0.0' -- attributes [principal-query] WFLYCTL0302: The following attributes are not understood in the target model version and this resource will need to be ignored on the target host: [principal-query] > {code} > The error message should contain something like {{[principal-query[0].scram-mapper.hash-encoding]}} instead of {{[principal-query]}}. > The error message is misleading, as the attribute {{[principal-query]}} HAS TO be defined - only the {{hash-encoding}} must not. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3852) Incomplete attribute name in error message of ObjectFieldsRejectAttributeChecker

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3852?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3852: ------------------------------------- Labels: domain-mode transformers (was: transformers) > Incomplete attribute name in error message of ObjectFieldsRejectAttributeChecker > -------------------------------------------------------------------------------- > > Key: WFCORE-3852 > URL: https://issues.jboss.org/browse/WFCORE-3852 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 5.0.0.Beta1 > Reporter: Jan Kalina > Labels: domain-mode, transformers > > When defined ObjectFieldsRejectAttributeChecker (or ListRejectAttributeChecker or their combination) in transformers, the error message is missleading - points to the complex attribute instead of individual subattributes: > {code} > WFLYCTL0297: Transforming operation { > \"address\" => [ > (\"profile\" => \"full\"), > (\"subsystem\" => \"elytron\"), > (\"jdbc-realm\" => \"xxxx\") > ], > \"operation\" => \"add\", > \"principal-query\" => [{ > \"data-source\" => \"ExampleDS\", > \"sql\" => \"SEL\", > \"scram-mapper\" => { > \"iteration-count-index\" => \"1\", > \"password-index\" => \"2\", > \"salt-index\" => \"5\", > \"hash-encoding\" => \"base64\" // this attribute is not backward compatible > } > }], > \"operation-headers\" => { > \"caller-type\" => \"user\", > \"access-mechanism\" => \"NATIVE\", > \"domain-uuid\" => \"658c12cc-9501-47d0-bf24-aa11079e444a\", > \"execute-for-coordinator\" => true, > \"domain-controller-lock-id\" => -1163262107 > } > } at resource [ > (\"profile\" => \"full\"), > (\"subsystem\" => \"elytron\"), > (\"jdbc-realm\" => \"xxxx\") > ] to subsystem 'elytron' model version '2.0.0' -- attributes [principal-query] WFLYCTL0302: The following attributes are not understood in the target model version and this resource will need to be ignored on the target host: [principal-query] > {code} > The error message should contain something like {{[principal-query[0].scram-mapper.hash-encoding]}} instead of {{[principal-query]}}. > The error message is misleading, as the attribute {{[principal-query]}} HAS TO be defined - only the {{hash-encoding}} must not. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-182) Validate that Istio was succesfully deployed

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-182?page=com.atlassian.jira.plugin.... ] Matt Mahoney commented on SWSQE-182: ------------------------------------ Note: Feedback provided to Sunil. > Validate that Istio was succesfully deployed > -------------------------------------------- > > Key: SWSQE-182 > URL: https://issues.jboss.org/browse/SWSQE-182 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Matt Mahoney > Assignee: Sunil kondkar > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AG-84) Runtime changes to min-size

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-84?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro updated AG-84: ---------------------------- Summary: Runtime changes to min-size (was: runtime changes to min-size) > Runtime changes to min-size > --------------------------- > > Key: AG-84 > URL: https://issues.jboss.org/browse/AG-84 > Project: Agroal > Issue Type: Bug > Components: pool > Affects Versions: 0.5 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 0.6 > > > Don't strictly require to fill the pool when there is an increase on min-size -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AG-84) Runtime changes to min-size

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-84?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro resolved AG-84. ----------------------------- Resolution: Done > Runtime changes to min-size > --------------------------- > > Key: AG-84 > URL: https://issues.jboss.org/browse/AG-84 > Project: Agroal > Issue Type: Bug > Components: pool > Affects Versions: 0.5 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 0.6 > > > Don't strictly require to fill the pool when there is an increase on min-size -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AG-84) runtime changes to min-size

by Luis Barreiro (JIRA)

Luis Barreiro created AG-84: ------------------------------- Summary: runtime changes to min-size Key: AG-84 URL: https://issues.jboss.org/browse/AG-84 Project: Agroal Issue Type: Bug Components: pool Affects Versions: 0.5 Reporter: Luis Barreiro Assignee: Luis Barreiro Fix For: 0.6 Don't strictly require to fill the pool when there is an increase on min-size -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3786) ManagementAuthenticationUsersTestCase fails on latest JDKs

by Richard Opalka (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3786?page=com.atlassian.jira.plugi... ] Richard Opalka closed WFCORE-3786. ---------------------------------- Fix Version/s: 5.0.0.Beta2 (was: 5.0.0.Beta3) Resolution: Done > ManagementAuthenticationUsersTestCase fails on latest JDKs > ---------------------------------------------------------- > > Key: WFCORE-3786 > URL: https://issues.jboss.org/browse/WFCORE-3786 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Richard Opalka > Assignee: Darran Lofthouse > Fix For: 5.0.0.Beta2 > > > I downloaded both jdk1.8.0_b171 & jdk1.8.0_b172. > When running whole WFCORE test suite on them > I'm getting InvalidUserStore exception in > ManagementAuthenticationUsersTestCase -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 May 2018