April 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-60) Capabilities and requirements in a managed process

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-60?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFCORE-60: ----------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > Capabilities and requirements in a managed process > -------------------------------------------------- > > Key: WFCORE-60 > URL: https://issues.jboss.org/browse/WFCORE-60 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 1.0.0.CR1 > > > Implement the aspects discussed under the "Runtime" section of https://community.jboss.org/docs/DOC-52712 > Add an API to the OperationContext for handlers to publish capabilities and for other handlers to register a requirement for those capabilities and to access the API object associated with the capability. > The registry of capabilities and requirements should be maintained with a semantic equivalent to the resource tree. The registry is copied-on-write, making the copy invisible to concurrently executing operations, and then the copy is published on commit of the operation that modified it. If the operation does not commit, the copy is discarded, so handlers have no need to revert changes they make to the registry. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

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

by Kabir Khan (JIRA)

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

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-129) Overlay does not work for subunits in exploded deployments.

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-129?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFCORE-129: ------------------------------ Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > Overlay does not work for subunits in exploded deployments. > ----------------------------------------------------------- > > Key: WFCORE-129 > URL: https://issues.jboss.org/browse/WFCORE-129 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 1.0.0.Alpha8 > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 1.0.0.CR1 > > > If deployment is exploded and has subdeployments overlay wont work on files contained in said subdeployments. > Reproducers: https://github.com/baranowb/wildfly/tree/WFCORE-83-TESTS -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-114) Get RuntimeVaultReader into WildFly Core

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-114?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFCORE-114: ------------------------------ Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > Get RuntimeVaultReader into WildFly Core > ---------------------------------------- > > Key: WFCORE-114 > URL: https://issues.jboss.org/browse/WFCORE-114 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha8 > Reporter: Brian Stansberry > Assignee: ehsavoie Hugonnet > Priority: Blocker > Fix For: 1.0.0.CR1 > > > The only real implementation of AbstractVaultReader isn't in wildfly-core; it's in the wildfly-full security subsystem module. > This means WildFly Core currently doesn't really support vault expressions. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[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)

9 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)

9 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)

9 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)

9 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)

9 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)

9 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2015