December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-359) Failure to start the JVM should trigger a management update plan to rollback

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-359?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-744 to WFCORE-359: ---------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-359 (was: WFLY-744) Component/s: Domain Management (was: Domain Management) Fix Version/s: (was: Awaiting Volunteers) > Failure to start the JVM should trigger a management update plan to rollback > ---------------------------------------------------------------------------- > > Key: WFCORE-359 > URL: https://issues.jboss.org/browse/WFCORE-359 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Andrig Miller > > I have come across situations where certain JVM options, typically related to NUMA options, can cause the JVM to segfault. With our domain model, we expose the ability to set the JVM options, so I think this certainly would be a possibility. > So, as we discussed on the Andiamo call today, this type of situation should cause a rollback of the management update plan, if the JVM fails to start. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-354) Store config file comments in the model

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-354?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-731 to WFCORE-354: ---------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-354 (was: WFLY-731) Component/s: Domain Management (was: Domain Management) Fix Version/s: (was: Awaiting Volunteers) > Store config file comments in the model > --------------------------------------- > > Key: WFCORE-354 > URL: https://issues.jboss.org/browse/WFCORE-354 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 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 moved WFLY-736 to WFCORE-355: ---------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-355 (was: WFLY-736) Component/s: Domain Management (was: Domain Management) Fix Version/s: (was: Awaiting Volunteers) > 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: 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 (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-356) Make socket binding interface and port values available for use in property subsitution

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-356?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-702 to WFCORE-356: ---------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-356 (was: WFLY-702) Component/s: Domain Management (was: Domain Management) Fix Version/s: (was: Awaiting Volunteers) > Make socket binding interface and port values available for use in property subsitution > --------------------------------------------------------------------------------------- > > Key: WFCORE-356 > URL: https://issues.jboss.org/browse/WFCORE-356 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > > See linked dev list thread for an example use case (remote socket binding used in an driver-specific JDBC URL). > Some gotchas noted on the thread that need to be resolved: > A tricky thing to deal with is interfaces and socket bindings are > actually on-demand services. They aren't resolved until they are > demanded. Nothing in this connection-url scenario would demand the > socket binding, so it won't be resolved, and until it's resolved no > system property could be set. > That could be handled by adding an "auto-start" attribute on the > socket-binding config. Not particularly intuitive though. > Another thing to deal with is interface resolution. With the exception > of the "<loopback address="127.0.0.4"/> criteria Scott added, resolving > an interface means finding a NIC on the machine that matches the > criteria. If that can't be done, it's an error condition. To avoid that > there would need to be some new criteria added (e.g. > <remote-inet-address value="10.0.0.53"/>) or an attribute added to the > existing inet-address criteria (e.g. <inet-address value="10.0.0.53" > local="false"/>. (There is a separate JIRA for this issue: AS7-1614) > A minor issue relates to changing the configuration of a socket binding. > Basically, we try and track whether you've used a particular > SocketBinding service to open a socket; if not we let you change the > binding config without requiring a server restart or reload. This > connection-url stuff won't use the SocketBinding service to create a > socket, so the binding will be editable at runtime with no > reload/restart required. But there's no dependency relationship between > the binding and the datasource, so that change is not going to be > reflected in the datasource. This is just an example of the general > problem with using system properties as an injection mechanism. > I don't think this last point is a blocker, it just requires documentation. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-352) read-operation-name and read-operation-description should be combined

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-352?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-709 to WFCORE-352: ---------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-352 (was: WFLY-709) Component/s: Domain Management (was: Domain Management) Fix Version/s: (was: Awaiting Volunteers) > read-operation-name and read-operation-description should be combined > --------------------------------------------------------------------- > > Key: WFCORE-352 > URL: https://issues.jboss.org/browse/WFCORE-352 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Kevin Barfield > Priority: Minor > Labels: eap6-ux > > For usability, there should be a way to get a list of operation names with the descriptions attached > Example: > read-resource - This shows you the resources at the this node > etc > etc > etc -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-353) CLI command for executing the deployment scanner

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-353?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-710 to WFCORE-353: ---------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-353 (was: WFLY-710) Component/s: CLI Domain Management Server (was: CLI) (was: Domain Management) (was: Server) Fix Version/s: (was: Awaiting Volunteers) > CLI command for executing the deployment scanner > ------------------------------------------------ > > Key: WFCORE-353 > URL: https://issues.jboss.org/browse/WFCORE-353 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI, Domain Management, Server > Reporter: Ben Schofield > Priority: Minor > > provide a CLI command that will run the deployment scanner even if the deployment scanner is turned off. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-350) Domain reflects jboss.server.xy properties

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-350?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-686 to WFCORE-350: ---------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-350 (was: WFLY-686) Component/s: Domain Management Scripts (was: Domain Management) (was: Scripts) Fix Version/s: (was: Awaiting Volunteers) > Domain reflects jboss.server.xy properties > ------------------------------------------ > > Key: WFCORE-350 > URL: https://issues.jboss.org/browse/WFCORE-350 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Scripts > Reporter: Rostislav Svoboda > Priority: Minor > > Domain reflects jboss.server.xy properties, tested with jboss.server.log.dir property. > The same server.log file is used for both server-one and server-two. Only file boot.log is created in domain/servers/server-one/log and domain/servers/server-two/log directory. In my case file server.log contains log only for server-one, there is no log for server-two. > I think jboss.server.xy properties shouldn't be reflected in domain instances. > Even structure of https://docs.jboss.org/author/display/AS71/Command+line+parameters implies that jboss.server.xy properties are used for Standalone. > Reproducer of my steps: > {code} > rm -rf domain/servers > bin/domain.sh -Djboss.server.log.dir=/tmp/ > ls -aR domain/servers/server-one/log > ls -aR domain/servers/server-two/log > ls -l /tmp/server* > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-351) CLI "revert to snapshot" command

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-351?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-693 to WFCORE-351: ---------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-351 (was: WFLY-693) Component/s: Domain Management (was: Domain Management) Fix Version/s: (was: Awaiting Volunteers) > CLI "revert to snapshot" command > -------------------------------- > > Key: WFCORE-351 > URL: https://issues.jboss.org/browse/WFCORE-351 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Environment: all > Reporter: Rich Sharples > Labels: eap6-ux > > The CLI has commands for taking snapshots, listing snapshots, deleting snapshots but no way to rollback or revert to a previous snapshot. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-346) Serve gzip encoded console resources

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-346?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-1114 to WFCORE-346: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-346 (was: WFLY-1114) Component/s: Domain Management (was: Domain Management) > Serve gzip encoded console resources > ------------------------------------ > > Key: WFCORE-346 > URL: https://issues.jboss.org/browse/WFCORE-346 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Assignee: Darran Lofthouse > > To decrease network latency when loading the console from a remote host. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-347) Better reporting if a master and slave HC are both launched from the same directory

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-347?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-1087 to WFCORE-347: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-347 (was: WFLY-1087) Component/s: Domain Management (was: Domain Management) > Better reporting if a master and slave HC are both launched from the same directory > ----------------------------------------------------------------------------------- > > Key: WFCORE-347 > URL: https://issues.jboss.org/browse/WFCORE-347 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > > The only symptom at the moment is hangs on startup on the slave as mentioned in AS7-4593. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2014