March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1801) DomainSlaveHostRegistrations should survive a reload

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1801?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1801: ------------------------------------- Labels: domain-mode (was: ) > DomainSlaveHostRegistrations should survive a reload > ---------------------------------------------------- > > Key: WFCORE-1801 > URL: https://issues.jboss.org/browse/WFCORE-1801 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Priority: Minor > Labels: domain-mode > > DomainSlaveHostRegistrations is used by the master to record HC registration/unregistration events for display via the management API. The lifecycle of this data is tied to that of DomainModelControllerService, which gets gc'd and recreated on each reload. This data should have a longer lifespan than that. > It doesn't need to be persistent (survive HC restart) but surviving reload would be better. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-298) Provide configuration to define when config changes are pushed to servers in a domain

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-298?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-298: ------------------------------------ Affects Version/s: (was: domain-mode) > Provide configuration to define when config changes are pushed to servers in a domain > ------------------------------------------------------------------------------------- > > Key: WFCORE-298 > URL: https://issues.jboss.org/browse/WFCORE-298 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Labels: EAP, domain-mode > > An EAP customer request: > Right now, any changes done via the CLI to an active profile are pushed to all instances immediately. Some go life, some at reload only > While batch mode can be used to bundle a number of changes in one go, there is currently no way to tell individual servers or server-groups when to accept updates or not. > This proposal is to allow a config switch on servergroup level and on individual server level to accept a configuration change selectively: > 1. immediate, the current situation, being the default > 2. at restart only > 3. at explicit being told so, e.g. when a "reload" is ordered > Example: > <server name="server-three" group="other-server-group" updates="immediate"> > the default when the attribute is absent > <server name="server-three" group="other-server-group" updates="start"> > <server name="server-three" group="other-server-group" updates="explicit"> > The latter could then be triggered with: > /host=master/server-config=server1:reload > Similar option could be set on servergroup level, with a similar reload command on that level -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-312) Taking thread dumps via HC

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-312?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-312: ------------------------------------ Labels: domain-mode (was: ) > Taking thread dumps via HC > -------------------------- > > Key: WFCORE-312 > URL: https://issues.jboss.org/browse/WFCORE-312 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: James Livingston > Labels: domain-mode > > It would be useful to be able to gather low-level per-server information such as Java thread dumps. This would best be gathered from the Host Controllers, and be available via the management model. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-298) Provide configuration to define when config changes are pushed to servers in a domain

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-298?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-298: ------------------------------------ Labels: EAP domain-mode (was: EAP) > Provide configuration to define when config changes are pushed to servers in a domain > ------------------------------------------------------------------------------------- > > Key: WFCORE-298 > URL: https://issues.jboss.org/browse/WFCORE-298 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Labels: EAP, domain-mode > > An EAP customer request: > Right now, any changes done via the CLI to an active profile are pushed to all instances immediately. Some go life, some at reload only > While batch mode can be used to bundle a number of changes in one go, there is currently no way to tell individual servers or server-groups when to accept updates or not. > This proposal is to allow a config switch on servergroup level and on individual server level to accept a configuration change selectively: > 1. immediate, the current situation, being the default > 2. at restart only > 3. at explicit being told so, e.g. when a "reload" is ordered > Example: > <server name="server-three" group="other-server-group" updates="immediate"> > the default when the attribute is absent > <server name="server-three" group="other-server-group" updates="start"> > <server name="server-three" group="other-server-group" updates="explicit"> > The latter could then be triggered with: > /host=master/server-config=server1:reload > Similar option could be set on servergroup level, with a similar reload command on that level -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-312) Taking thread dumps via HC

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-312?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-312: ------------------------------------ Affects Version/s: (was: domain-mode) > Taking thread dumps via HC > -------------------------- > > Key: WFCORE-312 > URL: https://issues.jboss.org/browse/WFCORE-312 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: James Livingston > Labels: domain-mode > > It would be useful to be able to gather low-level per-server information such as Java thread dumps. This would best be gathered from the Host Controllers, and be available via the management model. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-355) List servers in a servergroup below /server-group/<groupname>

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-355?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-355: ------------------------------------ Affects Version/s: (was: domain-mode) > List servers in a servergroup below /server-group/<groupname> > ------------------------------------------------------------- > > Key: WFCORE-355 > URL: https://issues.jboss.org/browse/WFCORE-355 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Rupp > Labels: domain-mode, rhq > > It would be nice from a consistency standpoint to list the servers of a servergroup in its > api below /server-group/groupname/ - just the names would be enough. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-355) List servers in a servergroup below /server-group/<groupname>

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-355?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-355: ------------------------------------ Labels: domain-mode rhq (was: rhq) > List servers in a servergroup below /server-group/<groupname> > ------------------------------------------------------------- > > Key: WFCORE-355 > URL: https://issues.jboss.org/browse/WFCORE-355 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Rupp > Labels: domain-mode, rhq > > It would be nice from a consistency standpoint to list the servers of a servergroup in its > api below /server-group/groupname/ - just the names would be enough. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-343) Trailing forgotten --> does not generate a good error message on host.xml

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-343?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-343: ------------------------------------ Affects Version/s: (was: domain-mode) > Trailing forgotten --> does not generate a good error message on host.xml > ------------------------------------------------------------------------- > > Key: WFCORE-343 > URL: https://issues.jboss.org/browse/WFCORE-343 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Jim Tyrrell > Labels: domain-mode, eap6-ux > > This snippet from the host.xml file, note the --> that was forgotten to be removed in the remote line... > <domain-controller> >  >  > </domain-controller> > Generates this error message: > [Host Controller] 21:24:51,341 ERROR [org.jboss.as.controller] (Controller Boot Thread) JBAS014601: Error booting the container: java.lang.RuntimeException: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration > Several lines further down...you get this message... > [Host Controller] Caused by: com.ctc.wstx.exc.WstxParsingException: Received non-all-whitespace CHARACTERS or CDATA event in nextTag(). > [Host Controller] at [row,col {unknown-source}]: [44,4] > It would be nice if the first error message in an XML parsing error would just show me the place it failed, along with maybe the prior line. > Less nice would be the 44,4 to be in the first message and break it down as line 44, character 4. More verbosity would be nice. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-343) Trailing forgotten --> does not generate a good error message on host.xml

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-343?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-343: ------------------------------------ Labels: domain-mode eap6-ux (was: eap6-ux) > Trailing forgotten --> does not generate a good error message on host.xml > ------------------------------------------------------------------------- > > Key: WFCORE-343 > URL: https://issues.jboss.org/browse/WFCORE-343 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Jim Tyrrell > Labels: domain-mode, eap6-ux > > This snippet from the host.xml file, note the --> that was forgotten to be removed in the remote line... > <domain-controller> >  >  > </domain-controller> > Generates this error message: > [Host Controller] 21:24:51,341 ERROR [org.jboss.as.controller] (Controller Boot Thread) JBAS014601: Error booting the container: java.lang.RuntimeException: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration > Several lines further down...you get this message... > [Host Controller] Caused by: com.ctc.wstx.exc.WstxParsingException: Received non-all-whitespace CHARACTERS or CDATA event in nextTag(). > [Host Controller] at [row,col {unknown-source}]: [44,4] > It would be nice if the first error message in an XML parsing error would just show me the place it failed, along with maybe the prior line. > Less nice would be the 44,4 to be in the first message and break it down as line 44, character 4. More verbosity would be nice. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[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: (was: 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 > Reporter: Jim Tyrrell > Labels: domain-mode, 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

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