April 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1504) Add /core-service=service-container resource to host model

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1504?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1504: ------------------------------------- Labels: (was: 2.2) > Add /core-service=service-container resource to host model > ---------------------------------------------------------- > > Key: WFCORE-1504 > URL: https://issues.jboss.org/browse/WFCORE-1504 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 3.0.0.Alpha1 > > > {quote} > Kabir Khan·17:30 > @BrianStansberry I'm replying to mazz > Just trying to dump services though, is there any reason why we have /core-service=service-container on a server, but no /host=master/core-service=service-container on a HC? > Brian Stansberry·17:37 > @KabirKhan I don't think so > for some reason I was poking at that a few days ago and I couldn't find any reason why not > Kabir Khan·17:37 > I'll add a Jira > Brian Stansberry·17:37 > I think it's something historical that no longer applies > Kabir Khan·17:37 > Probably just an oversight > we had jconsole all the time > and probably enhanced this for servers at some stage > Brian Stansberry·17:38 > I'm quite certain I put that TODO in there and there was a real reason at the time > Kabir Khan·17:38 > where is the TODO? > Brian Stansberry·17:40 > @KabirKhan https://github.com/wildfly/wildfly-core/blob/master/host-controller/src/m... > {quote} > So we should > a) investigate if this is possible or not > b) Make it happen if it is -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1504) Add /core-service=service-container resource to host model

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1504?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1504: ------------------------------------- Labels: 2.2 (was: ) > Add /core-service=service-container resource to host model > ---------------------------------------------------------- > > Key: WFCORE-1504 > URL: https://issues.jboss.org/browse/WFCORE-1504 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Labels: 2.2 > Fix For: 3.0.0.Alpha1 > > > {quote} > Kabir Khan·17:30 > @BrianStansberry I'm replying to mazz > Just trying to dump services though, is there any reason why we have /core-service=service-container on a server, but no /host=master/core-service=service-container on a HC? > Brian Stansberry·17:37 > @KabirKhan I don't think so > for some reason I was poking at that a few days ago and I couldn't find any reason why not > Kabir Khan·17:37 > I'll add a Jira > Brian Stansberry·17:37 > I think it's something historical that no longer applies > Kabir Khan·17:37 > Probably just an oversight > we had jconsole all the time > and probably enhanced this for servers at some stage > Brian Stansberry·17:38 > I'm quite certain I put that TODO in there and there was a real reason at the time > Kabir Khan·17:38 > where is the TODO? > Brian Stansberry·17:40 > @KabirKhan https://github.com/wildfly/wildfly-core/blob/master/host-controller/src/m... > {quote} > So we should > a) investigate if this is possible or not > b) Make it happen if it is -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-316) Slave host does not register to DC when starting with --cached-dc and DC is available

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-316?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFCORE-316: ----------------------------------------- Another note: the reason persistence of changes to domain.cached-remote.xml can't happen even if the slave connects to a DC is because in the --cached-dc case we use this ConfigurationPersister: https://github.com/wildfly/wildfly-core/blob/master/host-controller/src/m... The store() method logs a warn and then returns a no-op PersistenceResource. I think it probably can just not override the superclass, which is what BackupRemoteDomainXmlPersister just above it does. > Slave host does not register to DC when starting with --cached-dc and DC is available > ------------------------------------------------------------------------------------- > > Key: WFCORE-316 > URL: https://issues.jboss.org/browse/WFCORE-316 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Manel Martinez Gonzalez > Assignee: Ken Wills > Fix For: 3.0.0.Beta1 > > > NOTE: this is related to AS7-4281 (see https://issues.jboss.org/browse/AS7-4281?focusedCommentId=12682058&page=c... ) > When a slave host is started with --cached-dc option it won't register to Domain Controller although it's available. domain.sh help says "If this host is not the Domain Controller and cannot contact the Domain Controller at boot, boot using a locally cached copy of the domain configuration (see --backup)" and this is not really happening because slave host never contact to DC with --cached-dc -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-316) Slave host does not register to DC when starting with --cached-dc and DC is available

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-316?page=com.atlassian.jira.plugin... ] Ken Wills commented on WFCORE-316: ---------------------------------- Adding not that the associated routing & exception is here: https://github.com/wildfly/wildfly-core/blob/master/host-controller/src/m... > Slave host does not register to DC when starting with --cached-dc and DC is available > ------------------------------------------------------------------------------------- > > Key: WFCORE-316 > URL: https://issues.jboss.org/browse/WFCORE-316 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Manel Martinez Gonzalez > Assignee: Ken Wills > Fix For: 3.0.0.Beta1 > > > NOTE: this is related to AS7-4281 (see https://issues.jboss.org/browse/AS7-4281?focusedCommentId=12682058&page=c... ) > When a slave host is started with --cached-dc option it won't register to Domain Controller although it's available. domain.sh help says "If this host is not the Domain Controller and cannot contact the Domain Controller at boot, boot using a locally cached copy of the domain configuration (see --backup)" and this is not really happening because slave host never contact to DC with --cached-dc -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1506) Add a HostControllerEnvironmentService

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1506?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-1506: ------------------------------- Fix Version/s: 3.0.0.Alpha1 (was: 3.0.0.Beta1) > Add a HostControllerEnvironmentService > -------------------------------------- > > Key: WFCORE-1506 > URL: https://issues.jboss.org/browse/WFCORE-1506 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Kabir Khan > Assignee: Brian Stansberry > Fix For: 3.0.0.Alpha1 > > > On servers we add a ServerEnvironmentService giving subsystems access to the ServerEnvironment. > For the host controller subsystems it would be useful to have something similar to allow access to the HostControllerEnvironment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1506) Add a HostControllerEnvironmentService

by Kabir Khan (JIRA)

Kabir Khan created WFCORE-1506: ---------------------------------- Summary: Add a HostControllerEnvironmentService Key: WFCORE-1506 URL: https://issues.jboss.org/browse/WFCORE-1506 Project: WildFly Core Issue Type: Enhancement Components: Domain Management Reporter: Kabir Khan Assignee: Brian Stansberry Fix For: 3.0.0.Beta1 On servers we add a ServerEnvironmentService giving subsystems access to the ServerEnvironment. For the host controller subsystems it would be useful to have something similar to allow access to the HostControllerEnvironment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1505) Missing services for outbound socket bindings on the HC

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1505?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-1505: ------------------------------- Description: Calling {code} {code} I see a corresponding service in the service container' {code} Service "org.wildfly.network.socket-binding.one" (aliases: jboss.binding.one) (class org.jboss.as.server.services.net.SocketBindingService) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.host.controller.model.controller) (dependencies: jboss.socket-binding-manager) {code} However, when e.g. doing: {code} /host=master/socket-binding-group=sockets/remote-destination-outbound-socket-binding=test:add(host=localhost,port=12345) {code} I see no corresponding service in the dump. > Missing services for outbound socket bindings on the HC > ------------------------------------------------------- > > Key: WFCORE-1505 > URL: https://issues.jboss.org/browse/WFCORE-1505 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Kabir Khan > Assignee: Brian Stansberry > Fix For: 3.0.0.Alpha1 > > > Calling > {code} > {code} > I see a corresponding service in the service container' > {code} > Service "org.wildfly.network.socket-binding.one" (aliases: jboss.binding.one) (class org.jboss.as.server.services.net.SocketBindingService) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.host.controller.model.controller) (dependencies: jboss.socket-binding-manager) > {code} > However, when e.g. doing: > {code} > /host=master/socket-binding-group=sockets/remote-destination-outbound-socket-binding=test:add(host=localhost,port=12345) > {code} > I see no corresponding service in the dump. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1505) Missing services for outbound socket bindings on the HC

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1505?page=com.atlassian.jira.plugi... ] Kabir Khan reassigned WFCORE-1505: ---------------------------------- Assignee: Kabir Khan (was: Brian Stansberry) > Missing services for outbound socket bindings on the HC > ------------------------------------------------------- > > Key: WFCORE-1505 > URL: https://issues.jboss.org/browse/WFCORE-1505 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 3.0.0.Alpha1 > > > Calling > {code} > {code} > I see a corresponding service in the service container' > {code} > Service "org.wildfly.network.socket-binding.one" (aliases: jboss.binding.one) (class org.jboss.as.server.services.net.SocketBindingService) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.host.controller.model.controller) (dependencies: jboss.socket-binding-manager) > {code} > However, when e.g. doing: > {code} > /host=master/socket-binding-group=sockets/remote-destination-outbound-socket-binding=test:add(host=localhost,port=12345) > {code} > I see no corresponding service in the dump. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1504) Add /core-service=service-container resource to host model

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1504?page=com.atlassian.jira.plugi... ] Kabir Khan reassigned WFCORE-1504: ---------------------------------- Assignee: Kabir Khan (was: Brian Stansberry) > Add /core-service=service-container resource to host model > ---------------------------------------------------------- > > Key: WFCORE-1504 > URL: https://issues.jboss.org/browse/WFCORE-1504 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 3.0.0.Alpha1 > > > {quote} > Kabir Khan·17:30 > @BrianStansberry I'm replying to mazz > Just trying to dump services though, is there any reason why we have /core-service=service-container on a server, but no /host=master/core-service=service-container on a HC? > Brian Stansberry·17:37 > @KabirKhan I don't think so > for some reason I was poking at that a few days ago and I couldn't find any reason why not > Kabir Khan·17:37 > I'll add a Jira > Brian Stansberry·17:37 > I think it's something historical that no longer applies > Kabir Khan·17:37 > Probably just an oversight > we had jconsole all the time > and probably enhanced this for servers at some stage > Brian Stansberry·17:38 > I'm quite certain I put that TODO in there and there was a real reason at the time > Kabir Khan·17:38 > where is the TODO? > Brian Stansberry·17:40 > @KabirKhan https://github.com/wildfly/wildfly-core/blob/master/host-controller/src/m... > {quote} > So we should > a) investigate if this is possible or not > b) Make it happen if it is -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-915) Allow concurrent registration of slave host controllers

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-915?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-915: ------------------------------------ Labels: 2.2 (was: ) > Allow concurrent registration of slave host controllers > ------------------------------------------------------- > > Key: WFCORE-915 > URL: https://issues.jboss.org/browse/WFCORE-915 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Ken Wills > Labels: 2.2 > Fix For: 3.0.0.Alpha1 > > > Registration of slave host controllers must be done with the exclusive ModelController lock held, in order to ensure that the registering HC sees a consistent config throughout the entire process. The drawback to this is registrations must therefore be done in series, which is inefficient in a large domain. > We need to evaluate how this can be done in parallel, without losing the correctness semantics. For example, have the first registration request acquire the lock, but then don't release the lock as long as any other registrations are in progress. > The current lock acquisition mechanism based on an OperationStepHandler acquiring the lock[1] can't do this, or at least not without having the request that acquires the lock have to wait for final completion until all other concurrent requests complete. (Doing that will likely cause problems due to that "unlucky" first slave not getting the expected final response. Plus it just smells bad.) > A possibility is to remove the currrent lock acquisition in the OSH[1] and instead change the internal HostControllerRegistrationHandler.OperationExecutor API to expose a use-case specific method for the initial registration call.[2] The actual HostControllerRegistrationHandler.OperationExecutor impl is DomainModelControllerService, which is the service that installs the ModelControllerImpl and potentially has closer access to its non-public API (i.e. the locking methods.) So DomainModelControllerService can perhaps therefore coordinate the locking, holding the lock until all active registrations complete. > [1] https://github.com/wildfly/wildfly-core/blob/master/host-controller/src/m... > [2] I want to change that API anyway. See TODO at https://github.com/wildfly/wildfly-core/blob/master/host-controller/src/m... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 2016