April 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-185) Api returns internal server error instead of not found for non-existing path

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-185?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFCORE-185: ------------------------------ Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > Api returns internal server error instead of not found for non-existing path > ---------------------------------------------------------------------------- > > Key: WFCORE-185 > URL: https://issues.jboss.org/browse/WFCORE-185 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Heiko Rupp > Assignee: Brian Stansberry > Labels: rhq > Fix For: 1.0.0.CR1 > > > When I try to e.g. /subsystem=foo:read-resource the api returns a 500 internal server error. > In http-land, the return code for "not found" is normally 404. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

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

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-170?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFCORE-170: ------------------------------ Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > 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: 1.0.0.CR1 > > > 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)

11 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-230) Failure by ProcessController to launch a server vm is not logged

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-230?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFCORE-230: ------------------------------ Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > Failure by ProcessController to launch a server vm is not logged > ---------------------------------------------------------------- > > Key: WFCORE-230 > URL: https://issues.jboss.org/browse/WFCORE-230 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha11 > Reporter: Brian Stansberry > Assignee: ehsavoie Hugonnet > Fix For: 1.0.0.CR1 > > > In a domain configuration, if a server is associated with an incorrectly configurated jvm java-home (e.g. domain.xml -> server-groups -> jvm), it will fail silently (no error shown in logs). For example: > ``` > <server-group name="mySrvrGrp" profile="full"> > <jvm name="my-default" java-home="/usr/java/wrongPath"> > <heap size="1024m" max-size="4096m"/> > <permgen size="256m" max-size="256m"/> > <stack size="256k"/> > ``` -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-198) Remove deprecated operations and attributes from the logging subsystem

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-198?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFCORE-198: ------------------------------ Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > Remove deprecated operations and attributes from the logging subsystem > ---------------------------------------------------------------------- > > Key: WFCORE-198 > URL: https://issues.jboss.org/browse/WFCORE-198 > Project: WildFly Core > Issue Type: Task > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Blocker > Fix For: 1.0.0.CR1 > > > Deprecated operations and attributes need to be removed before final. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-234) Inconsistent synchronization in ConfigurationFile

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-234?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFCORE-234: ------------------------------ Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > Inconsistent synchronization in ConfigurationFile > ------------------------------------------------- > > Key: WFCORE-234 > URL: https://issues.jboss.org/browse/WFCORE-234 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha11 > Reporter: Brian Stansberry > Fix For: 1.0.0.CR1 > > > ConfigurationFile synchronizes on itself in some places and not in others. This may cause problems, particularly with the history dir. > The one that comes to mind is successfulBoot is synchronized, but all the methods called by ConfigurationFilePersistenceResource are not. The latter is called with the controller lock held, but the former is not. So there's a possibility of two threads interacting with the files concurrently if an operation executes immediately after boot. > The deployment scanner schedules such an op, so it's possible. Currently the schedule is for 200 ms after deployment-scanner add runs during boot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-273) ServerInventory#reconnectServer should take auto-start into account

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-273?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFCORE-273: ------------------------------ Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > ServerInventory#reconnectServer should take auto-start into account > ------------------------------------------------------------------- > > Key: WFCORE-273 > URL: https://issues.jboss.org/browse/WFCORE-273 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Emanuel Muckenhuber > Fix For: 1.0.0.CR1 > > > When reconnecting to stopped (but not removed) servers, the ServerInventory should take the auto-start property into account. Otherwise the process will just get removed, however started with the next :reload of the HC. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

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

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-266?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFCORE-266: ------------------------------ Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > 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: 1.0.0.CR1 > > > 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)

11 years

1
0
0 / 0

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

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-278?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFCORE-278: ------------------------------ Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > 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: 1.0.0.CR1 > > > 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)

11 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-287) Provide an operation to execute domain wide queries on the server side

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-287?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFCORE-287: ------------------------------ Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > Provide an operation to execute domain wide queries on the server side > ---------------------------------------------------------------------- > > Key: WFCORE-287 > URL: https://issues.jboss.org/browse/WFCORE-287 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 1.0.0.CR1 > > > i.e. retrieve all 'enabled' datasources that use the 'h2' driver: > {code:java} > ModelNode address = new ModelNode(); > address.add("profile", "*") > .add("subsystem", "datasources") > .add("data-source", "*"); > ModelNode filter = new ModelNode(); > filter.add("driver-name", "h2") > .add("enabled", true); > ModelNode op = new ModelNode(); > op.get(OP).set(QUERY); > op.get(ADDRESS).set(address); > op.get(WHERE).set(filter); > {code} > Another example using the CLI: > {code} > [standalone@localhost:9990 /] /path=*:query(select=[path], where={name="jboss.home.dir"}) > { > "outcome" => "success", > "result" => [{ > "address" => [("path" => "jboss.home.dir")], > "outcome" => "success", > "result" => {"path" => "/Users/hbraun/dev/prj/wildfly-core/core-build/target/wildfly-core-1.0.0.Alpha14-SNAPSHOT"} > }] > } > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-293) Add EAP 6.2 and 6.3 to versions tested in core-model-test

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-293?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFCORE-293: ------------------------------ Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > Add EAP 6.2 and 6.3 to versions tested in core-model-test > --------------------------------------------------------- > > Key: WFCORE-293 > URL: https://issues.jboss.org/browse/WFCORE-293 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: ehsavoie Hugonnet > Priority: Blocker > Fix For: 1.0.0.CR1 > > > The latest EAP versions are not being tested in core-model-test. > Seems there are problems with 6.2: > https://github.com/wildfly/wildfly/pull/6409 > I haven't tried 6.3 because it is not complete. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

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 April 2015