March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-330) No Spaces Allowed in Host -> Name, but ' do work, odd

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-330?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-330: ------------------------------------ Affects Version/s: domain-mode > No Spaces Allowed in Host -> Name, but ' do work, odd > ----------------------------------------------------- > > Key: WFCORE-330 > URL: https://issues.jboss.org/browse/WFCORE-330 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Affects Versions: domain-mode > Reporter: Jim Tyrrell > Labels: eap6-ux > > For some reason spaces do not seem to be allowed, but an Apostrophe seems to be okay. > [Host Controller] 20:56:20,250 ERROR [org.jboss.as.controller] (Controller Boot Thread) JBAS014601: Error booting the container: java.lang.IllegalArgumentException: JBAS014719: Invalid value specification Jim's Most_Excellent_Domain_Ever_so_here > Would be nice if the error message would kick out what values are acceptable? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-397) Provide Unit for JVM configuration elements

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-397?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-397: ------------------------------------ Labels: domain-mode (was: ) > Provide Unit for JVM configuration elements > ------------------------------------------- > > Key: WFCORE-397 > URL: https://issues.jboss.org/browse/WFCORE-397 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Labels: domain-mode > > Like with any other config element, units for the JVM parameters would be nice. > I.e. instead of encoding it into the string value ("64m") it would be better to split the actual value from unit (value=64, unit=<kb|mb|gb>). See the thread subsystem for a reference how this is done in other places -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-218) wildfly web management console hangs during deploy from cli

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-218?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-218: ------------------------------------ Labels: domain-mode (was: ) > wildfly web management console hangs during deploy from cli > ----------------------------------------------------------- > > Key: WFCORE-218 > URL: https://issues.jboss.org/browse/WFCORE-218 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha1 > Reporter: Ian Kent > Labels: domain-mode > Attachments: threaddump-1415735255304.tdump > > > We are running wildfly in domain mode with the following configuration. > host A running domain controlller > host B running host controller with one app sever > host C running host controller with one app server > host D running host controller with one app server > When we deloy war using jboss-cli the web console is blocked for usage until deploy completes. I have run jvisualvm and it does not appear that domain controller process is starved for resources (cpu, memory, threads). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-252) Guard domain topology changes with separate locks from the controller lock

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-252?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-252: ------------------------------------ Labels: domain-mode (was: ) > Guard domain topology changes with separate locks from the controller lock > -------------------------------------------------------------------------- > > Key: WFCORE-252 > URL: https://issues.jboss.org/browse/WFCORE-252 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management > Affects Versions: 1.0.0.Alpha12 > Reporter: Brian Stansberry > Labels: domain-mode > > Look into having a separate lock for the domain topology, and not using the exclusive controller lock to guard it. This requires great care though, as now there will be two separate locks involved in operation execution. We need to be certain that all code paths always acquire them in the same order or we'll be vulnerable to deadlocks. I believe the correct order should be 1) topology lock 2) controller lock. There are relatively few points where a topology lock would be needed, and I believe they are all at the outer edge of operation execution. So it's much simpler to control those points and ensure they always get topology before doing anything that could need the controller lock. > Note it's possible 3 locks will be involved, one for host topology, one for server, and then the controller lock. > Locking order needs to be thought about on a domain-wide basis, not just within a single process! > This task will be more important once the feature discussed at http://lists.jboss.org/pipermail/wildfly-dev/2014-October/003241.html comes in, as that will result in numerous read operations that truly need the domain topology lock. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-251) Avoiding unnecessary 2-phase execution of composite operations in a managed domain

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-251?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-251: ------------------------------------ Labels: domain-mode (was: ) > Avoiding unnecessary 2-phase execution of composite operations in a managed domain > ---------------------------------------------------------------------------------- > > Key: WFCORE-251 > URL: https://issues.jboss.org/browse/WFCORE-251 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management > Affects Versions: 1.0.0.Alpha12 > Reporter: Brian Stansberry > Labels: domain-mode > > When the console sends a composite operation, it is getting routed into the 2-phase domain wide operation path more often than is necessary, resulting in requests for the exclusive controller lock for read-only ops that could be executed on the local process without needing the lock. > Improving this needs to be done carefully, but should be a relatively straightforward change and probably will have the biggest impact on the parent issue, as most of the CRUD screens in the console don't need to invoke ops that involve more than the domain controller. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-338) Auto-promotion of slave HC to master

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-338?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-338: ------------------------------------ Labels: domain-mode (was: ) > Auto-promotion of slave HC to master > ------------------------------------ > > Key: WFCORE-338 > URL: https://issues.jboss.org/browse/WFCORE-338 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Labels: domain-mode > > Implement an option for a properly configured slave HC to promote itself to master after acquiring in some controlled manner an exclusive right to act as such. > Analysis (and eventually design) document is at: https://developer.jboss.org/docs/DOC-55491 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1882) Deal with WFCORE-1052 functionality in the HA DC case

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1882?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1882: ------------------------------------- Labels: domain-mode (was: ) > Deal with WFCORE-1052 functionality in the HA DC case > ----------------------------------------------------- > > Key: WFCORE-1882 > URL: https://issues.jboss.org/browse/WFCORE-1882 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Ken Wills > Labels: domain-mode > > WFCORE-1052 adds the ability to reload a process to a different config file from what it is currently running. That includes the domain-wide config file if the reloading process is a master HC. > I don't think we want to support this in a WFCORE-338 scenario, as it amounts to a mechanism to force a different domain-wide config into the domain. I think we should have a more specific, controlled mechanism for that. > Once WFCORE-1881 is implemented HostProcessReloadHandler can check LocalHostControllerInfo to see if its running in a CDC. Note that this issue may have implications on the design of WFCORE-1881. That is, it may not be the case that if LHCI.isMaster() is true then LHCI.isCandidateDomainController() is true. Perhaps an HC configured in the EAP 7.0 and earlier style could be a master but not a CDC. For such an HC the WFCORE-1052 functionality could be available. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-273?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-273: ------------------------------------ Labels: domain-mode (was: ) > 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 > Assignee: Ken Wills > Labels: domain-mode > > 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 (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1147) Eliminate ProcessController

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1147?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1147: ------------------------------------- Labels: domain-mode (was: ) > Eliminate ProcessController > --------------------------- > > Key: WFCORE-1147 > URL: https://issues.jboss.org/browse/WFCORE-1147 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: David Lloyd > Labels: domain-mode > > We should eliminate ProcessController and directly have the HC control the servers. This should greatly simplify the code and add more power and flexibility to the management and lifecycle of server JVMs. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1806) Split DomainModelControllerService into separate services for initializing as a master versus as a slave

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1806?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1806: ------------------------------------- Labels: domain-mode (was: ) > Split DomainModelControllerService into separate services for initializing as a master versus as a slave > -------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1806 > URL: https://issues.jboss.org/browse/WFCORE-1806 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Labels: domain-mode > Fix For: 4.0.0.Beta1 > > > This is an aspect of WFCORE-338, although it's valid in its own right as a conceptually cleaner approach to host controller boot. > Using different services is a prerequisite to WFCORE-338 as it allows those elements of HC behavior to be started/stopped as a DC candidate is elected or unelected. It also makes it feasible to wire in the service that performs the election. > The method that installs the service with MSC will return a Future<Boolean>, with the service setting the future's value at the completion of start(). DMCS during boot can block reading the future, from that confirm that the service completed successfully, and then proceed with the rest of boot. The boolean is basically an ok/not ok signal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 March 2017