[JBoss JIRA] (WFCORE-1499) logging custom-handler does not load module with slot
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1499?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1499:
-------------------------------------
Fix Version/s: 2.2.0.CR1
> logging custom-handler does not load module with slot
> -----------------------------------------------------
>
> Key: WFCORE-1499
> URL: https://issues.jboss.org/browse/WFCORE-1499
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Reporter: Erwan Lacoste
> Assignee: James Perkins
> Fix For: 2.2.0.CR1, 3.0.0.Alpha1
>
>
> Tested on EAP 6.4
> when creating a module for a custom *loghandler*, everything works fine if the module is package in default main slot, e.g.
> my/loghandler/main
> - module.xml
> - my.jar
> {code:xml}
> <custom-handler name="4H" class="my.handler.Periodic4HFileHandler" module="my.loghandler">
> {code}
> Nevertheless I want to version the module, therefore package my module with a given slot:
> my/loghandler/1.0
> - module.xml
> - my.jar
> {code:xml}
> <custom-handler name="4H" class="my.handler.Periodic4HFileHandler" module="my.loghandler:1.0">
> {code}
> But this fails with following stacktrace:
> {code}
> 11:53:50,458 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("add") failed - address: ([
> ("subsystem" => "logging"),
> ("custom-handler" => "4H")
> ]): java.lang.IllegalArgumentException: JBAS011532: Failed to load module 'my.loghandler:1.0' for handler '4H'
> at org.jboss.as.logging.HandlerOperations$HandlerAddOperationStepHandler.createHandlerConfiguration(HandlerOperations.java:320) [jboss-as-logging-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
> at org.jboss.as.logging.HandlerOperations$HandlerAddOperationStepHandler.performRuntime(HandlerOperations.java:255) [jboss-as-logging-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
> at org.jboss.as.logging.LoggingOperations$LoggingAddOperationStepHandler$1.execute(LoggingOperations.java:206) [jboss-as-logging-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:702) [jboss-as-controller-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:537) [jboss-as-controller-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:338) [jboss-as-controller-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:314) [jboss-as-controller-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1144) [jboss-as-controller-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
> at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:416) [jboss-as-controller-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
> at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:301) [jboss-as-controller-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
> at org.jboss.as.server.ServerService.boot(ServerService.java:355) [jboss-as-server-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
> at org.jboss.as.server.ServerService.boot(ServerService.java:330) [jboss-as-server-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:263) [jboss-as-controller-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_65]
> Caused by: org.jboss.modules.ModuleNotFoundException: my.loghandler:1.0:main
> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:240) [jboss-modules.jar:1.3.6.Final-redhat-1]
> at org.jboss.as.logging.HandlerOperations$HandlerAddOperationStepHandler.createHandlerConfiguration(HandlerOperations.java:295) [jboss-as-logging-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
> ... 13 more
> {code}
> why is the module not found being *my.loghandler:1.0:main* ?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFCORE-1505) Missing services for outbound socket bindings on the HC
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1505?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1505:
-------------------------------------
Fix Version/s: 2.2.0.CR1
> 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: 2.2.0.CR1, 3.0.0.Alpha1
>
>
> Calling
> {code}
> /host=master/socket-binding-group=sockets/socket-binding=one:add(port=1121)
> {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)
9 years, 11 months
[JBoss JIRA] (WFCORE-1485) ":read-resource(recursive=true)" generates output with random order, could be ordered alphabetically by keys
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1485?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1485:
-------------------------------------
Fix Version/s: 2.2.0.CR1
> ":read-resource(recursive=true)" generates output with random order, could be ordered alphabetically by keys
> ------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-1485
> URL: https://issues.jboss.org/browse/WFCORE-1485
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Ladislav Thon
> Assignee: Ladislav Thon
> Fix For: 2.2.0.CR1, 3.0.0.Alpha1
>
>
> ":read-resource(recursive=true)" generates output with random order, could it be ordered alphabetically by keys
> Now I can't do simple diff of changes, it's necessary to parse output to get valid list of changes.
> I expect output is stored in some structure data format before processed/printed out, could you use some sorted structure (Tree* stuff) ?
> Command to generate output and diff
> {code}
> jboss-eap-7.0/bin/jboss-cli.sh -c ":read-resource(recursive=true)" > 01 && jboss-eap-7.0/bin/jboss-cli.sh -c ":read-resource(recursive=true)" > 02
> diff 01 02 ## meld kdiff3 or your diff favorite tool
> {code}
> Diff in my case:
> {code:diff}
> > 02 && diff 01 02
> 50c50,67
> < "security" => {"classification" => {"security-domain" => {
> ---
> > "logging" => {"classification" => {
> > "logger" => {
> > "configured-application" => undefined,
> > "default-application" => false,
> > "applies-to" => undefined
> > },
> > "logging-profile" => {
> > "configured-application" => undefined,
> > "default-application" => false,
> > "applies-to" => undefined
> > }
> > }},
> > "naming" => {"classification" => {"binding" => {
> > "configured-application" => undefined,
> > "default-application" => false,
> > "applies-to" => undefined
> > }}},
> > "mail" => {"classification" => {"mail-session" => {
> 64a82,86
> > "security" => {"classification" => {"security-domain" => {
> > "configured-application" => undefined,
> > "default-application" => false,
> > "applies-to" => undefined
> > }}},
> 66,70d87
> < "data-source" => {
> < "configured-application" => undefined,
> < "default-application" => false,
> < "applies-to" => undefined
> < },
> 80,86d96
> < }
> < }},
> < "logging" => {"classification" => {
> < "logging-profile" => {
> < "configured-application" => undefined,
> < "default-application" => false,
> < "applies-to" => undefined
> 88c98
> < "logger" => {
> ---
> > "data-source" => {
> 93,103c103
> < }},
> < "mail" => {"classification" => {"mail-session" => {
> < "configured-application" => undefined,
> < "default-application" => false,
> < "applies-to" => undefined
> < }}},
> < "naming" => {"classification" => {"binding" => {
> < "configured-application" => undefined,
> < "default-application" => false,
> < "applies-to" => undefined
> < }}}
> ---
> > }}
> 106,114d105
> < "mail" => {"classification" => {"mail-server-security" => {
> < "configured-requires-addressable" => undefined,
> < "configured-requires-read" => undefined,
> < "configured-requires-write" => undefined,
> < "default-requires-addressable" => false,
> < "default-requires-read" => false,
> < "default-requires-write" => true,
> < "applies-to" => undefined
> < }}},
> 116c107
> < "naming-binding" => {
> ---
> > "jndi-view" => {
> 121,122c112,113
> < "default-requires-read" => false,
> < "default-requires-write" => false,
> ---
> > "default-requires-read" => true,
> > "default-requires-write" => true,
> 125c116
> < "jndi-view" => {
> ---
> > "naming-binding" => {
> 130,131c121,122
> < "default-requires-read" => true,
> < "default-requires-write" => true,
> ---
> > "default-requires-read" => false,
> > "default-requires-write" => false,
> 153,162c144
> < "remoting" => {"classification" => {"remoting-security" => {
> < "configured-requires-addressable" => undefined,
> < "configured-requires-read" => undefined,
> < "configured-requires-write" => undefined,
> < "default-requires-addressable" => false,
> < "default-requires-read" => true,
> < "default-requires-write" => true,
> < "applies-to" => undefined
> < }}},
> < "security" => {"classification" => {"misc-security" => {
> ---
> > "logging" => {"classification" => {"view-server-logs" => {
> 167,168c149,150
> < "default-requires-read" => true,
> < "default-requires-write" => true,
> ---
> > "default-requires-read" => false,
> > "default-requires-write" => false,
> 171,172c153,154
> < "undertow" => {"classification" => {
> < "undertow-handler" => {
> ---
> > "core" => {"classification" => {
> > "security-realm-ref" => {
> 176,178c158,160
> < "default-requires-addressable" => false,
> < "default-requires-read" => false,
> < "default-requires-write" => false,
> ---
> > "default-requires-addressable" => true,
> > "default-requires-read" => true,
> > "default-requires-write" => true,
> 181c163
> < "undertow-filter" => {
> ---
> > "server-ssl" => {
> 185,187c167,169
> < "default-requires-addressable" => false,
> < "default-requires-read" => false,
> < "default-requires-write" => false,
> ---
> > "default-requires-addressable" => true,
> > "default-requires-read" => true,
> > "default-requires-write" => true,
> 190c172
> < "web-connector" => {
> ---
> > "service-container" => {
> 196c178
> < "default-requires-write" => false,
> ---
> > "default-requires-write" => true,
> 199c181
> < "web-access-log" => {
> ---
> > "extensions" => {
> 205c187
> < "default-requires-write" => false,
> ---
> > "default-requires-write" => true,
> 207,237c189,190
> < }
> < }},
> < "logging" => {"classification" => {"view-server-logs" => {
> < "configured-requires-addressable" => undefined,
> < "configured-requires-read" => undefined,
> < "configured-requires-write" => undefined,
> < "default-requires-addressable" => false,
> < "default-requires-read" => false,
> < "default-requires-write" => false,
> < "applies-to" => undefined
> < }}},
> < "datasources" => {"classification" => {"data-source-security" => {
> < "configured-requires-addressable" => undefined,
> < "configured-requires-read" => undefined,
> < "configured-requires-write" => undefined,
> < "default-requires-addressable" => false,
> < "default-requires-read" => true,
> < "default-requires-write" => true,
> < "applies-to" => undefined
> < }}},
> < "resource-adapters" => {"classification" => {"resource-adapter-security" => {
> < "configured-requires-addressable" => undefined,
> < "configured-requires-read" => undefined,
> < "configured-requires-write" => undefined,
> < "default-requires-addressable" => false,
> < "default-requires-read" => true,
> < "default-requires-write" => true,
> < "applies-to" => undefined
> < }}},
> < "core" => {"classification" => {
> < "extensions" => {
> ---
> > },
> > "system-property" => {
> 246c199
> < "service-container" => {
> ---
> > "module-loading" => {
> 255c208
> < "domain-controller" => {
> ---
> > "jvm" => {
> 264c217
> < "domain-names" => {
> ---
> > "snapshots" => {
> 270c223
> < "default-requires-write" => true,
> ---
> > "default-requires-write" => false,
> 273c226
> < "security-domain-ref" => {
> ---
> > "access-control" => {
> 291c244
> < "management-interfaces" => {
> ---
> > "credential" => {
> 296c249
> < "default-requires-read" => false,
> ---
> > "default-requires-read" => true,
> 300c253
> < "socket-binding-ref" => {
> ---
> > "management-interfaces" => {
> 306c259
> < "default-requires-write" => false,
> ---
> > "default-requires-write" => true,
> 309c262
> < "socket-config" => {
> ---
> > "security-domain" => {
> 313,314c266,267
> < "default-requires-addressable" => false,
> < "default-requires-read" => false,
> ---
> > "default-requires-addressable" => true,
> > "default-requires-read" => true,
> 318c271
> < "security-vault" => {
> ---
> > "patching" => {
> 323c276
> < "default-requires-read" => true,
> ---
> > "default-requires-read" => false,
> 327c280
> < "server-ssl" => {
> ---
> > "read-whole-config" => {
> 331c284
> < "default-requires-addressable" => true,
> ---
> > "default-requires-addressable" => false,
> 336c289
> < "jvm" => {
> ---
> > "domain-controller" => {
> 345c298
> < "module-loading" => {
> ---
> > "security-vault" => {
> 350c303
> < "default-requires-read" => false,
> ---
> > "default-requires-read" => true,
> 354c307
> < "security-domain" => {
> ---
> > "security-domain-ref" => {
> 363c316
> < "snapshots" => {
> ---
> > "socket-binding-ref" => {
> 372c325
> < "credential" => {
> ---
> > "domain-names" => {
> 377c330
> < "default-requires-read" => true,
> ---
> > "default-requires-read" => false,
> 381c334
> < "read-whole-config" => {
> ---
> > "socket-config" => {
> 386c339
> < "default-requires-read" => true,
> ---
> > "default-requires-read" => false,
> 389,390c342,363
> < },
> < "patching" => {
> ---
> > }
> > }},
> > "mail" => {"classification" => {"mail-server-security" => {
> > "configured-requires-addressable" => undefined,
> > "configured-requires-read" => undefined,
> > "configured-requires-write" => undefined,
> > "default-requires-addressable" => false,
> > "default-requires-read" => false,
> > "default-requires-write" => true,
> > "applies-to" => undefined
> > }}},
> > "resource-adapters" => {"classification" => {"resource-adapter-security" => {
> > "configured-requires-addressable" => undefined,
> > "configured-requires-read" => undefined,
> > "configured-requires-write" => undefined,
> > "default-requires-addressable" => false,
> > "default-requires-read" => true,
> > "default-requires-write" => true,
> > "applies-to" => undefined
> > }}},
> > "undertow" => {"classification" => {
> > "undertow-filter" => {
> 396c369
> < "default-requires-write" => true,
> ---
> > "default-requires-write" => false,
> 399c372
> < "access-control" => {
> ---
> > "web-connector" => {
> 403,405c376,378
> < "default-requires-addressable" => true,
> < "default-requires-read" => true,
> < "default-requires-write" => true,
> ---
> > "default-requires-addressable" => false,
> > "default-requires-read" => false,
> > "default-requires-write" => false,
> 408c381
> < "system-property" => {
> ---
> > "undertow-handler" => {
> 414c387
> < "default-requires-write" => true,
> ---
> > "default-requires-write" => false,
> 417c390
> < "security-realm-ref" => {
> ---
> > "web-access-log" => {
> 421,423c394,396
> < "default-requires-addressable" => true,
> < "default-requires-read" => true,
> < "default-requires-write" => true,
> ---
> > "default-requires-addressable" => false,
> > "default-requires-read" => false,
> > "default-requires-write" => false,
> 426c399,426
> < }}
> ---
> > }},
> > "datasources" => {"classification" => {"data-source-security" => {
> > "configured-requires-addressable" => undefined,
> > "configured-requires-read" => undefined,
> > "configured-requires-write" => undefined,
> > "default-requires-addressable" => false,
> > "default-requires-read" => true,
> > "default-requires-write" => true,
> > "applies-to" => undefined
> > }}},
> > "remoting" => {"classification" => {"remoting-security" => {
> > "configured-requires-addressable" => undefined,
> > "configured-requires-read" => undefined,
> > "configured-requires-write" => undefined,
> > "default-requires-addressable" => false,
> > "default-requires-read" => true,
> > "default-requires-write" => true,
> > "applies-to" => undefined
> > }}},
> > "security" => {"classification" => {"misc-security" => {
> > "configured-requires-addressable" => undefined,
> > "configured-requires-read" => undefined,
> > "configured-requires-write" => undefined,
> > "default-requires-addressable" => false,
> > "default-requires-read" => true,
> > "default-requires-write" => true,
> > "applies-to" => undefined
> > }}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFCORE-1501) Failure to create timestamped config file history fails boot
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1501?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1501:
-------------------------------------
Fix Version/s: 2.2.0.CR1
> Failure to create timestamped config file history fails boot
> ------------------------------------------------------------
>
> Key: WFCORE-1501
> URL: https://issues.jboss.org/browse/WFCORE-1501
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 2.1.0.Final
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Labels: 2.2
> Fix For: 2.2.0.CR1, 3.0.0.Alpha1
>
>
> Something like the following shouldn't be allowed to fail a boot; if it happens an ERROR should be logged but no exception thrown:
> {code}
> 2016-04-22 22:10:21,247 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: java.lang.IllegalStateException: WFLYCTL0056: Could not rename C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone_xml_history\current to C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone_xml_history\20160422-221021244
> at org.jboss.as.controller.persistence.ConfigurationFile.createHistoryDirectory(ConfigurationFile.java:668)
> at org.jboss.as.controller.persistence.ConfigurationFile.successfulBoot(ConfigurationFile.java:500)
> at org.jboss.as.controller.persistence.BackupXmlConfigurationPersister.successfulBoot(BackupXmlConfigurationPersister.java:94)
> at org.jboss.as.controller.AbstractControllerService.finishBoot(AbstractControllerService.java:452)
> at org.jboss.as.server.ServerService.boot(ServerService.java:367)
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> That stack trace indicates file standalone\configuration\standalone_xml_history\20160422-221021144 must already exist but the 2nd attempt renameTo standalone\configuration\standalone_xml_history\20160422-221021244 has failed. It would be good to sort out what happened, but regardless it should not fail boot.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFCORE-1456) org.jboss.as.cli.scriptsupport.CLI prevents use of embed-server and embed-host-controller
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1456?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1456:
-------------------------------------
Fix Version/s: 2.2.0.CR1
> org.jboss.as.cli.scriptsupport.CLI prevents use of embed-server and embed-host-controller
> -----------------------------------------------------------------------------------------
>
> Key: WFCORE-1456
> URL: https://issues.jboss.org/browse/WFCORE-1456
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 2.1.0.Final
> Reporter: Brian Stansberry
> Assignee: Jean-Francois Denise
> Fix For: 2.2.0.CR1, 3.0.0.Alpha1
>
>
> The org.jboss.as.cli.scriptsupport.CLI will throw an exception if the user invokes the cmd method before invoking one of the connect methods. But the connect/disconnect methods are oriented toward remote connections. The result is you can't really use this class with the offline CLI.
> I'm not sure what the best fix is here. Perhaps new method(s) analogous to connect/disconnect that establish a CommandContext but don't call connectController(). Or perhaps the checkNotConnected() call in the cmd method should just be dropped, and an unconnected command context created. But then the existing connect/disconnect methods would need to be reworked to deal with the fact that an unconnected command context may be present.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFCORE-1471) CLI class is mixing commands and operations
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1471?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1471:
-------------------------------------
Fix Version/s: 2.2.0.CR1
> CLI class is mixing commands and operations
> -------------------------------------------
>
> Key: WFCORE-1471
> URL: https://issues.jboss.org/browse/WFCORE-1471
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 3.0.0.Alpha1
> Reporter: Jean-Francois Denise
> Assignee: Jean-Francois Denise
> Fix For: 2.2.0.CR1, 3.0.0.Alpha1
>
>
> CLI.cmd method logic is not in sync with the CLI syntax.
> A fallback is implemented in order to route requests to cx.handle only if ctx.buildRequest(cliCommand) is failing.
> For example this doesn't cope with reload vs :reload. In this case, buildRequest will succeed both for reload and :reload. CLI.cmd("reload") will end to be treated as CLI.cmd(":reload");
> Furthermore batch and workflow are not supported by CLI.
> I am suggesting to implement the following logic:
> 1) If batch is enabled or a workflow is enabled, route the command to handle
> 2) Parse the request.
> 3) If this is an operation, route to execute
> 4) Otherwise route to handle
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFCORE-1373) Unable to specify custom configuration directory via -Djboss.server.config.dir
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1373?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1373:
-------------------------------------
Fix Version/s: 2.2.0.CR1
> Unable to specify custom configuration directory via -Djboss.server.config.dir
> ------------------------------------------------------------------------------
>
> Key: WFCORE-1373
> URL: https://issues.jboss.org/browse/WFCORE-1373
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 2.1.0.CR1
> Reporter: Sergey Lisovoy
> Assignee: ehsavoie Hugonnet
> Fix For: 2.2.0.CR1, 3.0.0.Alpha1
>
>
> Broken support for server config files location customization via: {{jboss.server.config.dir}}.
> Previous Wildfly 10 versions till CR4 it works as expected. Broken since WF10.0.0.CR5
> See Steps to reproduce.
> Error:
> Cannot start embedded server: WFLYEMB0022: Cannot invoke 'start' on embedded process: WFLYCTL0214: Could not get main file: config.xml. Specified files must be relative to the configuration dir: /opt/wildfly-10.0.0.Final/standalone/configuration
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFCORE-1467) Servers are suspended two times using timeout parameter in domain mode
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1467?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1467:
-------------------------------------
Fix Version/s: 3.0.0.Alpha1
2.2.0.CR1
> Servers are suspended two times using timeout parameter in domain mode
> ----------------------------------------------------------------------
>
> Key: WFCORE-1467
> URL: https://issues.jboss.org/browse/WFCORE-1467
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Yeray Santana Borges
> Assignee: Yeray Santana Borges
> Fix For: 2.2.0.CR1, 3.0.0.Alpha1
>
>
> In a domain mode :suspend-servers command with a timeout parameter different than 0 executes two suspend operations for each server in the domain. It first executes a suspend with 0ms and later a suspend with the timeout specified.
> How to reproduce it:
> {code}
> [domain@localhost:9990 /] :suspend-servers(timeout=10)
> {code}
> Server log traces show:
> {code}
> [Server:server-one] 20:14:40,126 INFO [org.jboss.as.server] (ServerService Thread Pool -- 8) WFLYSRV0211: Suspending server with 0ms timeout.
> [Server:server-one] 20:14:40,135 INFO [org.jboss.as.server] (ServerService Thread Pool -- 8) WFLYSRV0211: Suspending server with 10000000ms timeout.
> {code}
> Expected traces are:
> {code}
> [Server:server-one] 20:14:40,135 INFO [org.jboss.as.server] (ServerService Thread Pool -- 8) WFLYSRV0211: Suspending server with 10000000ms timeout.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months