May 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-170) Create a shared ScheduledExecutorService

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-170?page=com.atlassian.jira.plugin... ] Jason Greene updated WFCORE-170: -------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Create a shared ScheduledExecutorService > ---------------------------------------- > > Key: WFCORE-170 > URL: https://issues.jboss.org/browse/WFCORE-170 > Project: WildFly Core > Issue Type: Feature Request > Components: Server > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 2.0.0.Alpha4 > > > There are number of ScheduledExecutorService instances being created around wf-core. Create a single service and inject it. > This will reduce resource usage by creating fewer threads, and will reduce the risk of code mistakes around shutting down the various executors, > I see these used in: > LdapCacheService > RemoteDomainConnectionService > DeploymentMountProvider > DeploymentScannerService > plus the operation response attachment stuff I'm doing will need one. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-137) Add Kerberos tests to domain-management module

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-137?page=com.atlassian.jira.plugin... ] Jason Greene updated WFCORE-137: -------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Add Kerberos tests to domain-management module > ---------------------------------------------- > > Key: WFCORE-137 > URL: https://issues.jboss.org/browse/WFCORE-137 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 2.0.0.Alpha4 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-109) Update syslog handler attributes

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-109?page=com.atlassian.jira.plugin... ] Jason Greene updated WFCORE-109: -------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Update syslog handler attributes > -------------------------------- > > Key: WFCORE-109 > URL: https://issues.jboss.org/browse/WFCORE-109 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > Fix For: 2.0.0.Alpha4 > > > The syslog handler does not currently expose the formatter for formatting messages. There will also be changes in a future logmanager release for TCP support and various other properties based on the new TCP support. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-299) HTTP Management Interface Configuration

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-299?page=com.atlassian.jira.plugin... ] Jason Greene updated WFCORE-299: -------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > HTTP Management Interface Configuration > --------------------------------------- > > Key: WFCORE-299 > URL: https://issues.jboss.org/browse/WFCORE-299 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: management_security,, management_sso > Fix For: 2.0.0.Alpha4 > > > Various configuration items are required for the HTTP Management interface, this is a parent task to combine them. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-296) Switch URI scheme from remoting:// http-remoting:// https-remoting:// to remote:// remote+http:// and remote+https://

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-296?page=com.atlassian.jira.plugin... ] Jason Greene updated WFCORE-296: -------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Switch URI scheme from remoting:// http-remoting:// https-remoting:// to remote:// remote+http:// and remote+https:// > --------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-296 > URL: https://issues.jboss.org/browse/WFCORE-296 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI, Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 2.0.0.Alpha4 > > > From [~dmlloyd] > {quote} > When we have multi-layer protocol going on, the URI scheme we should use > is like this: > outer+middle+inner:// > {quote} > Switch URI schemes from remoting:// http-remoting:// https-remoting:// to remote:// remote+http:// and remote+https:// > The existing schemes will be needed for backwards compatibility but somehow deprecated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-266) Deprecate the ParameterValidator constructor variants that accept allowNull and allowExpressions params

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-266?page=com.atlassian.jira.plugin... ] Jason Greene updated WFCORE-266: -------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Deprecate the ParameterValidator constructor variants that accept allowNull and allowExpressions params > ------------------------------------------------------------------------------------------------------- > > Key: WFCORE-266 > URL: https://issues.jboss.org/browse/WFCORE-266 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 2.0.0.Alpha4 > > > Most of the ParameterValidator implementations that get passed to AttributeDefinition accept params to control whether null and expressions are allowed. These are now redundant, as AttributeDefinition wraps the provided validator with NillableOrExpressionParameterValidator, and it handles that aspect of validation based on the settings of the AD. > So we should deprecate these constructor variants to let people know they aren't needed. Ideally shift the code as well. > CRITICAL: before doing this, make sure the AttributeDefinition variants that support complex types properly wrap any validators that are configured for *element* validation. A quick look shows that ListAttributeDefinition.Builder and MapAttributeDefinition.Builder do. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-278) Revisit error message for an authentication failure.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-278?page=com.atlassian.jira.plugin... ] Jason Greene updated WFCORE-278: -------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Revisit error message for an authentication failure. > ---------------------------------------------------- > > Key: WFCORE-278 > URL: https://issues.jboss.org/browse/WFCORE-278 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Domain Management, Remoting, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 2.0.0.Alpha4 > > > After authentication fails in the CLI the following error message is output: - > {code} > Unable to authenticate against controller at localhost:9990: Authentication failed: the server presented no authentication mechanisms > {code} > This text is a bit misleading, what it actually means is all mechanisms presented have either been excluded or attempted and now no further mechanisms are available to try. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-263) Cancelling management op on slave HC tree is broken

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-263?page=com.atlassian.jira.plugin... ] Jason Greene updated WFCORE-263: -------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Cancelling management op on slave HC tree is broken > --------------------------------------------------- > > Key: WFCORE-263 > URL: https://issues.jboss.org/browse/WFCORE-263 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha9 > Reporter: James Livingston > Assignee: Brian Stansberry > Fix For: 2.0.0.Alpha4 > > Attachments: unundeployable.zip > > > If you have a DC with a slave HC, and perform a management operation which gets stuck, non-progressing operations will be reported for both the DC and the slave HC via: > /host=master/core-service=management/service=management-operations:find-non-progressing-operation > /host=slave/core-service=management/service=management-operations:find-non-progressing-operation > Cancelling the operation under /host=master works as expected, pushing the cancellation down to the slave and the controllers become responsive again. > If however you attempt to cancel the operation under /host=slave, it goes bad. { "outcome" => "success", "result" => undefined } is reported in the CLI, but the controllers are still unresponsive. > Running :find-non-progressing-operation against the slave will report the {outcome=success,result=undefined} rather than that no non-progressing operations were found, and active-operation=*:read-resource() shows it as not cancelled. > Once you attempt to cancel it on a slave, attempting to cancel it under /host=master will report success, but leave the slave op in a weird state, and things requiring the controller lock (such as the web UI) will still not respond. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-383) Update the DC's IgnoredTransformationRegistry when changes are made to a slave's <ignored-resources>

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-383?page=com.atlassian.jira.plugin... ] Jason Greene updated WFCORE-383: -------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Update the DC's IgnoredTransformationRegistry when changes are made to a slave's <ignored-resources> > ---------------------------------------------------------------------------------------------------- > > Key: WFCORE-383 > URL: https://issues.jboss.org/browse/WFCORE-383 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 2.0.0.Alpha4 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-372) Cache role mapping results for the span of the overall operation

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-372?page=com.atlassian.jira.plugin... ] Jason Greene updated WFCORE-372: -------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Cache role mapping results for the span of the overall operation > ---------------------------------------------------------------- > > Key: WFCORE-372 > URL: https://issues.jboss.org/browse/WFCORE-372 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Darran Lofthouse > Labels: access_control, management_security, > Fix For: 2.0.0.Alpha4 > > > Look into caching role mapping results for the duration of an overall operation. This would be an impl detail of the RoleMapper. With our standard mappers, the mapping results should not be changing in the middle of an operation, so I believe they should be cacheable. > Likely place to cache them is as an attachment in a context object that will be passed in to the Authorizer. It would have to be passed in to the RoleMapper as well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 2015