March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8336) Upgrade Narayana to 5.5.5.Final

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-8336?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-8336: -------------------------------- Summary: Upgrade Narayana to 5.5.5.Final (was: Upgrade Narayana to 5.5.4.Final) > Upgrade Narayana to 5.5.5.Final > ------------------------------- > > Key: WFLY-8336 > URL: https://issues.jboss.org/browse/WFLY-8336 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > https://issues.jboss.org/projects/JBTM/versions/12333853 > https://github.com/jbosstm/narayana/compare/5.5.3.Final...5.5.4.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6409) Update default domain configuration to use remote+http

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6409?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-6409: ----------------------------------- Labels: domain-mode (was: ) > Update default domain configuration to use remote+http > ------------------------------------------------------ > > Key: WFLY-6409 > URL: https://issues.jboss.org/browse/WFLY-6409 > Project: WildFly > Issue Type: Enhancement > Components: Domain Management > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Labels: domain-mode > Fix For: 12.0.0.Alpha1 > > > Our default domain configuration still use the native remote protocol on port 9999 for DC-HC communication. Update those files so that we use http-remoting on port 9990. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6616) Problems in DomainHostExcludes700TestCase

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6616?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-6616: ----------------------------------- Labels: domain-mode (was: ) > Problems in DomainHostExcludes700TestCase > ----------------------------------------- > > Key: WFLY-6616 > URL: https://issues.jboss.org/browse/WFLY-6616 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Assignee: Brian Stansberry > Labels: domain-mode > Fix For: 11.0.0.Alpha1 > > > The profile clone operation in the new DomainHostExcludes700TestCase.test003PostBootUpdates() in testsuite/mixed-domain fails with the following message: > {code} > { > "outcome" => "failed", > "failure-description" => {"domain-failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalStateException: WFLYCTL0363: Capability 'org.wildfly.messaging.activemq.server.default' is already registered in context 'profile=clone'."}, > "rolled-back" => true > } > {code} > And we also see an error in > {code} > DomainHostExcludes700TestCase.test001SlaveBoot:45->DomainHostExcludesTest.test001SlaveBoot:217->DomainHostExcludesTest.checkSocketBindingGroups:300 ["full-ha-sockets"] expected:<2> but was:<1> > {code} > Some WIP to create this test is in my https://github.com/kabir/wildfly/tree/WFLY-6616 branch -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1502) RBAC: The two kinds of non-addressability

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1502?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1502: ------------------------------------- Labels: domain-mode (was: ) > RBAC: The two kinds of non-addressability > ----------------------------------------- > > Key: WFCORE-1502 > URL: https://issues.jboss.org/browse/WFCORE-1502 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.1.0.Final > Reporter: Ladislav Thon > Assignee: Brian Stansberry > Labels: domain-mode > > Ever since we introduced RBAC in WildFly / EAP, we had this shortcut in place that we were documenting in EAP Release Notes: > bq. Some resources are non-addressable to server-group and host scoped roles in order to provide a simplified view of the management model to improve usability. This is distinct from resources that are non-addressable to protect sensitive data. > I think that this shortcut is in place mainly because HAL can't cope with addressable but non-readable resources, but there might be other reasons. In any case, I figured I should finally file an upstream JIRA so that I don't have to bug Brian all the time if this has changed :-) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2329) ServerAutoStartTestCase and ServerStartFailureTestCase are never run

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2329?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2329: ------------------------------------- Labels: domain-mode (was: ) > ServerAutoStartTestCase and ServerStartFailureTestCase are never run > -------------------------------------------------------------------- > > Key: WFCORE-2329 > URL: https://issues.jboss.org/browse/WFCORE-2329 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Test Suite > Reporter: Brian Stansberry > Labels: domain-mode > > Tests in testsuite/domain do not all automatically run just by being called XXXTestCase. They need to be located in one of the packages listed in the surefire config in testsuite/domain/pom.xml or by listed in the @Suite.SuiteClasses annotation of one of the suites that is in one of those packages. ServerAutoStartTestCase and ServerStartFailureTestCase are tests where neither of these are true so they are not running. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2298) RespawnHttpTestCase and RespawnTestCase don't account for recycling of PIDs

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2298?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2298: ------------------------------------- Labels: domain-mode (was: ) > RespawnHttpTestCase and RespawnTestCase don't account for recycling of PIDs > --------------------------------------------------------------------------- > > Key: WFCORE-2298 > URL: https://issues.jboss.org/browse/WFCORE-2298 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Test Suite > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Labels: domain-mode > > On Windows, apparently PIDs can be recycled in such a way that they can reappear shortly after the first process with a PID is terminated. (See http://stackoverflow.com/questions/26301382/does-windows-7-recycle-proces... and links therein.) > RespawnHttpTestCase is assuming that this won't happen, since when checking for reload completion it ignores any PID that belonged to one of the servers that's expected to be restarted. I'm seeing intermittent failures that seem to be due to this expectation being incorrect, as the logging for the failed tests clearly shows that the servers are restarted. > For example: > https://ci.wildfly.org/viewLog.html?buildId=45601&tab=buildResultsDiv&bui... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2298) RespawnHttpTestCase and RespawnTestCase don't account for recycling of PIDs

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2298?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-2298: ---------------------------------------- Assignee: (was: Brian Stansberry) > RespawnHttpTestCase and RespawnTestCase don't account for recycling of PIDs > --------------------------------------------------------------------------- > > Key: WFCORE-2298 > URL: https://issues.jboss.org/browse/WFCORE-2298 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Test Suite > Reporter: Brian Stansberry > Priority: Minor > Labels: domain-mode > > On Windows, apparently PIDs can be recycled in such a way that they can reappear shortly after the first process with a PID is terminated. (See http://stackoverflow.com/questions/26301382/does-windows-7-recycle-proces... and links therein.) > RespawnHttpTestCase is assuming that this won't happen, since when checking for reload completion it ignores any PID that belonged to one of the servers that's expected to be restarted. I'm seeing intermittent failures that seem to be due to this expectation being incorrect, as the logging for the failed tests clearly shows that the servers are restarted. > For example: > https://ci.wildfly.org/viewLog.html?buildId=45601&tab=buildResultsDiv&bui... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2093) A 'start' operation only is available for a domain server resource when it is started

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2093?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2093: ------------------------------------- Labels: domain-mode (was: ) > A 'start' operation only is available for a domain server resource when it is started > ------------------------------------------------------------------------------------- > > Key: WFCORE-2093 > URL: https://issues.jboss.org/browse/WFCORE-2093 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: ehsavoie Hugonnet > Labels: domain-mode > Fix For: 4.0.0.Beta1 > > > The server lifecycle ops are registered with the domain server resource by a call to ServerConfigResourceDefintion.registerServerLifecycleOperations. DomainModelControllerService registers that when the server registers with the HC. > This is odd in the case of 'start' as it means that op is only registered when the server is started. > Perhaps it should be registered with StoppedServerResource, although I haven't dug into what happens with that resource when the server is registered. If it is simply ignored that would be great. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2022) Can not invoke read-resource-description on multi target address with a resource named server.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2022?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2022: ------------------------------------- Labels: domain-mode (was: ) > Can not invoke read-resource-description on multi target address with a resource named server. > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-2022 > URL: https://issues.jboss.org/browse/WFCORE-2022 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 3.0.0.Alpha12 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Labels: domain-mode > > To reproduce, invoke: > {noformat} > /subsystem=undertow/server=*/http-listener=*:read-resource-description > { > "outcome" => "failed", > "result" => [], > "failure-description" => "WFLYCTL0030: No resource definition is registered for address [ > (\"subsystem\" => \"undertow\"), > (\"server\" => \"*\") > ]", > "rolled-back" => true > } > {noformat} > The address is valid but the operation fails at org.jboss.as.controller.operations.global.GlobalOperationHandlers.RegistrationAddressResolver#executeMultiTargetChildren when checking the condition: > {noformat} > if (path.getKey().equals(RUNNING_SERVER) && path.isWildcard() && newRemaining.size() > 0) > {noformat} > The check was added for WFCORE-948 but makes any multi target operation with a server resource fails (such as Undertow server or messaging-activemq server resources). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2092) ProxyControllerRegistration does not properly implement getOperationDescriptions

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2092?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2092: ------------------------------------- Labels: domain-mode (was: ) > ProxyControllerRegistration does not properly implement getOperationDescriptions > -------------------------------------------------------------------------------- > > Key: WFCORE-2092 > URL: https://issues.jboss.org/browse/WFCORE-2092 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Labels: domain-mode > > A ProxyControllerRegistration is kind of a strange beast, as it represents a resource that has a dual nature, both as a leaf resource on the local process and as the root resource on the remote process. One place where this falls apart is with getOperationDescriptions, which does nothing locally, resulting in only ops on the remote side being described. > But a ProxyControllerRegistration can also have local ops; e.g. stop/kill/destroy ops on a /host=x/server=y resource. But because of this bug those ops can be invoked but they do not appear in things like read-operation-names output. > UPDATE: this is a poor description as the real goal is to get correct metadata via read-operation-names, read-operation-description, read-resource-description and doing that will require more than changing ProxyControllerRegistration. There would need to be OSHs for those ops at the proxy address that understand how to integrate the data from the two aspects of the resource. > UPDATE 2: Similar discussion may apply to attributes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2017