[JBoss JIRA] (WFLY-3703) arq.container.domain.ManagementClient.readRootNode does not see servers on remote hosts
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-3703?page=com.atlassian.jira.plugin.... ]
Brian Stansberry reopened WFLY-3703:
------------------------------------
Assignee: Arcadiy Ivanov (was: Alexey Loubyansky)
Reopening to adjust fix versions and give Arcadiy credit as the assignee.
> arq.container.domain.ManagementClient.readRootNode does not see servers on remote hosts
> ---------------------------------------------------------------------------------------
>
> Key: WFLY-3703
> URL: https://issues.jboss.org/browse/WFLY-3703
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 8.1.0.Final
> Environment: Linux aimobile-sm.servicemesh.com 3.15.6-200.fc20.x86_64 #1 SMP Fri Jul 18 02:36:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Arcadiy Ivanov
> Assignee: Arcadiy Ivanov
> Priority: Blocker
> Attachments: non-recursive.txt, recursive-runtime.txt, recursive.txt
>
>
> Trying to use Arquillian with remote multi-host domain.
> Now see the code snippet below:
> * readRootNode calls readResource with includeRuntime set to true.
> * readResource also sets recursive to true.
> However due to this behavior of read-resource *no hosts other than domain controller's are visible to Arquillian*:
> [proxies – (boolean, default is false) – whether to include remote resources in a recursive query (i.e. host level resources from slave Host Controllers in a query of the Domain Controller; running server resources in a query of a host).|https://docs.jboss.org/author/display/WFLY8/Global+operations]
> +As a result if I have a DC on localhost with no servers and Host1 with Node1 on 127.0.0.2 and Host2 with Node2 on 127.0.0.3, Arquillian will not find ANY servers to deploy to - no proxies (remote hosts) will be enumerated.+
> {noformat}
> private void readRootNode() throws Exception {
> rootNode = readResource(new ModelNode());
> }
> private ModelNode readResource(ModelNode address) throws Exception {
> return readResource(address, true);
> }
> private ModelNode readResource(ModelNode address, boolean includeRuntime) throws Exception {
> final ModelNode operation = new ModelNode();
> operation.get(OP).set(READ_RESOURCE_OPERATION);
> operation.get(RECURSIVE).set("true");
> operation.get(INCLUDE_RUNTIME).set(includeRuntime);
> operation.get(OP_ADDR).set(address);
> return executeForResult(operation);
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (WFCORE-42) Add a ServerXml Parser which extends CommonXml
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFCORE-42?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFCORE-42:
-------------------------------
Fix Version/s: 1.0.0.Alpha8
(was: 1.0.0.Alpha7)
> Add a ServerXml Parser which extends CommonXml
> ----------------------------------------------
>
> Key: WFCORE-42
> URL: https://issues.jboss.org/browse/WFCORE-42
> Project: WildFly Core
> Issue Type: Task
> Components: Domain Management
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 1.0.0.Alpha8
>
>
> Both StandaloneXml and AppclientXml parse XML starting from the server element.
> This duplication has always been problematic as AppclientXml is completely separate from the remaining domain config parsing, however with the core split this is even worse.
> This change is to introduce a ServerXml that can be the common base for both StandaloneXml and AppclientXml - except in extreme cases it will then be safe to ignore AppclientXml for further schema updates.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (WFCORE-77) We need even better reporting for failed authentications
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFCORE-77?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFCORE-77:
-------------------------------
Fix Version/s: 1.0.0.Alpha8
(was: 1.0.0.Alpha7)
> We need even better reporting for failed authentications
> --------------------------------------------------------
>
> Key: WFCORE-77
> URL: https://issues.jboss.org/browse/WFCORE-77
> Project: WildFly Core
> Issue Type: Bug
> Components: Remoting
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 1.0.0.Alpha8
>
>
> The following message is often the one reported to users: -
> {noformat}
> >> Caused by: javax.security.sasl.SaslException: Authentication failed:
> >> the server presented no authentication mechanisms
> {noformat}
> Whilst technically it is true at that point in time this is most likely caused because other mechanisms have already been tried and failed and the list of mechanisms to try is now exhausted.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years