[JBoss JIRA] (WFLY-11362) Update root README with instructions to build the README html files
by Sande Gilda (Jira)
[ https://issues.jboss.org/browse/WFLY-11362?page=com.atlassian.jira.plugin... ]
Sande Gilda updated WFLY-11362:
-------------------------------
Description: Now that the `README.adoc` files use includes and are not easily readable, we should provide instructions to generate the `README.html` files. We also need to remove some obsolete content, for example '.md' files that have been replaced with '.adoc' files. (was: Now that the `README.adoc` files use includes and are not easily readable, we should provide instructions to generate the `README.html` files. We also need to remove some obsolete content, for example '*.md' files that have been replaced with '*.adoc' files.)
> Update root README with instructions to build the README html files
> -------------------------------------------------------------------
>
> Key: WFLY-11362
> URL: https://issues.jboss.org/browse/WFLY-11362
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Reporter: Sande Gilda
> Assignee: Sande Gilda
> Priority: Major
>
> Now that the `README.adoc` files use includes and are not easily readable, we should provide instructions to generate the `README.html` files. We also need to remove some obsolete content, for example '.md' files that have been replaced with '.adoc' files.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11362) Update root README with instructions to build the README html files
by Sande Gilda (Jira)
[ https://issues.jboss.org/browse/WFLY-11362?page=com.atlassian.jira.plugin... ]
Sande Gilda updated WFLY-11362:
-------------------------------
Description: Now that the `README.adoc` files use includes and are not easily readable, we should provide instructions to generate the `README.html` files. We also need to remove some obsolete content, for example '*.md' files that have been replaced with '*.adoc' files. (was: Now that the `README.adoc` files use includes and are not easily readable, we should provide instructions to generate the `README.html` files.)
> Update root README with instructions to build the README html files
> -------------------------------------------------------------------
>
> Key: WFLY-11362
> URL: https://issues.jboss.org/browse/WFLY-11362
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Reporter: Sande Gilda
> Assignee: Sande Gilda
> Priority: Major
>
> Now that the `README.adoc` files use includes and are not easily readable, we should provide instructions to generate the `README.html` files. We also need to remove some obsolete content, for example '*.md' files that have been replaced with '*.adoc' files.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11117) Executing legacy operations in mod_cluster subsystem is not possible with configuration with just one proxy
by Jan Kašík (Jira)
[ https://issues.jboss.org/browse/WFLY-11117?page=com.atlassian.jira.plugin... ]
Jan Kašík commented on WFLY-11117:
----------------------------------
It seems to me, that this is still not fixed...
{noformat}
[standalone@localhost:9990 /] /subsystem=modcluster/:disable
06:02:59,984 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("disable") failed - address: ([("subsystem" => "modcluster")]): java.lang.IllegalStateException: WFLYCTL0181: Get service registry only supported in runtime operations
at org.jboss.as.controller.OperationContextImpl.getServiceRegistry(OperationContextImpl.java:613)
at org.jboss.as.controller.OperationContextImpl.getServiceRegistry(OperationContextImpl.java:590)
at org.wildfly.extension.mod_cluster.LegacyProxyOperation.getService(LegacyProxyOperation.java:524)
at org.wildfly.extension.mod_cluster.LegacyProxyOperation.access$100(LegacyProxyOperation.java:61)
at org.wildfly.extension.mod_cluster.LegacyProxyOperation$2.execute(LegacyProxyOperation.java:116)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999)
at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743)
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467)
at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1411)
at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423)
at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:289)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:255)
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:138)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:162)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:313)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270)
at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254)
at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:158)
at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:485)
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalStateException: WFLYCTL0181: Get service registry only supported in runtime operations",
"rolled-back" => true
{noformat}
> Executing legacy operations in mod_cluster subsystem is not possible with configuration with just one proxy
> -----------------------------------------------------------------------------------------------------------
>
> Key: WFLY-11117
> URL: https://issues.jboss.org/browse/WFLY-11117
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 14.0.0.Final
> Reporter: Jan Kašík
> Assignee: Radoslav Husar
> Priority: Major
> Fix For: 15.0.0.Beta1
>
>
> Running legacy operation ends up with an error:
> {code}
> [standalone@localhost:9990 /] /subsystem=modcluster/:disable
> {
> "outcome" => "failed",
> "failure-description" => "WFLYMODCLS0022: Legacy operations cannot be used with multiple proxy configurations. Use non-deprecated operations at the correct proxy address.",
> "rolled-back" => true
> }
> {code}
> mod_cluster configuration:
> {code}
> [standalone@localhost:9990 /] /subsystem=modcluster/:read-resource
> {
> "outcome" => "success",
> "result" => {
> "mod-cluster-config" => {"configuration" => undefined},
> "proxy" => {"default" => undefined}
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months