[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)
11 years, 5 months
[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)
11 years, 5 months
[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)
11 years, 5 months
[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)
11 years, 5 months
[JBoss JIRA] (WFCORE-348) review server debug-options configuration
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-348?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-1229 to WFCORE-348:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-348 (was: WFLY-1229)
Component/s: Domain Management
(was: Domain Management)
> review server debug-options configuration
> -----------------------------------------
>
> Key: WFCORE-348
> URL: https://issues.jboss.org/browse/WFCORE-348
> Project: WildFly Core
> Issue Type: Task
> Components: Domain Management
> Reporter: Emanuel Muckenhuber
> Assignee: Emanuel Muckenhuber
>
> We need to review the server debug-options configuration, since it's not entirely clear what value is expected. Currently the JVM specific builder is doing additional checks, so that the value passed to the JVM startsWith -X. Which might not be true for all JVMs.
> <jvm name="default" debug-enabled="true" debug-options="runjdwp:transport=dt_socket,address=8787,server=y,suspend=n" />
> https://issues.jboss.org/browse/AS7-1606
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (WFCORE-349) Document new system properties for the configuration history length and the number of days
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-349?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-1231 to WFCORE-349:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-349 (was: WFLY-1231)
Component/s: Domain Management
(was: Documentation)
(was: Domain Management)
> Document new system properties for the configuration history length and the number of days
> ------------------------------------------------------------------------------------------
>
> Key: WFCORE-349
> URL: https://issues.jboss.org/browse/WFCORE-349
> Project: WildFly Core
> Issue Type: Task
> Components: Domain Management
> Reporter: Ivo Studensky
>
> New system properties have been introduced to AS7 which allow setting of the configuration history length and the number of days they are kept. These properties need to be documented properly. See AS7-4931.
> The default value of jboss.config.current-history-length is 100 and the default value of jboss.config.history-days is 30.
> Here is an example configuration:
> {code:title=standalone.xml|xml}
> ..
> </extensions>
> <system-properties>
> <property name="jboss.config.current-history-length" value="50"/>
> <property name="jboss.config.history-days" value="15"/>
> </system-properties>
> <management>
> ..
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[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 moved WFLY-1047 to WFCORE-343:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-343 (was: WFLY-1047)
Component/s: Domain Management
(was: Domain Management)
> 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: eap6-ux
>
> This snippet from the host.xml file, note the --> that was forgotten to be removed in the remote line...
> <domain-controller>
> <!--<local/>-->
> <!-- Alternative remote domain controller configuration with a host and$
> <remote host="127.0.0.1" port="9999"/>-->
> </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
(v6.3.8#6338)
11 years, 5 months