September 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2175) Add transformers for RBAC resources

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-2175: -------------------------------------- Summary: Add transformers for RBAC resources Key: WFLY-2175 URL: https://issues.jboss.org/browse/WFLY-2175 Project: WildFly Issue Type: Sub-task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 8.0.0.CR1 Transformation needs to be supported so WF 8 hosts can manage earlier version slaves without the RBAC facilities breaking things. The basic idea here is everything needs to be discarded unless the provider != undefined or simple. Trying to use or change to 'rbac' should trigger failure. The complicated part is the parent resource /core-service=management needs to be discarded if all the children are. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2174) Intermittent failures in DomainControllerMigrationTestCase

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-2174: -------------------------------------- Summary: Intermittent failures in DomainControllerMigrationTestCase Key: WFLY-2174 URL: https://issues.jboss.org/browse/WFLY-2174 Project: WildFly Issue Type: Bug Components: Domain Management, Test Suite Affects Versions: 8.0.0.Alpha4 Reporter: Brian Stansberry Assignee: Emanuel Muckenhuber Fix For: 8.0.0.CR1 For example: java.lang.RuntimeException: "JBAS010839: Operation failed or was rolled back on all servers." at org.jboss.as.test.integration.domain.management.util.DomainLifecycleUtil.executeForResult(DomainLifecycleUtil.java:582) at org.jboss.as.test.integration.domain.DomainControllerMigrationTestCase.testDCFailover(DomainControllerMigrationTestCase.java:206) With this in the logs: [Host Controller] 14:51:08,996 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.2.0.Alpha1 (AS 7.3.0.Final-redhat-SNAPSHOT) (Host Controller) started in 829ms - Started 12 of 12 services (0 services are passive or on-demand) [Server:failover-two] 14:51:10,113 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "SimpleServlet.war" (runtime-name: "SimpleServlet.war") [Host Controller] 14:51:10,377 INFO [org.jboss.as.domain.controller.mgmt] (Remoting "failover-h3:MANAGEMENT" task-2) JBAS010920: Server [Server:failover-three] registered using connection [Channel ID 7e979de4 (inbound) of Remoting connection 00429bb7 to /127.0.0.1:53634] [Host Controller] 14:51:11,185 ERROR [org.jboss.as.controller.management-operation] (domain-connection-threads - 2) JBAS014612: Operation ("composite") failed - address: ([ [Host Controller] ("host" => "failover-h3"), [Host Controller] ("server" => "failover-three") [Host Controller] ]): java.lang.RuntimeException: java.io.IOException: JBAS012175: Channel closed [Host Controller] at org.jboss.as.controller.remote.RemoteProxyController.execute(RemoteProxyController.java:203) [jboss-as-controller-7.3.0.Final-redhat-SNAPSHOT.jar:7.3.0.Final-redhat-SNAPSHOT] [Host Controller] at org.jboss.as.controller.TransformingProxyController$TransformingProxyControllerImpl.execute(TransformingProxyController.java:149) [jboss-as-controller-7.3.0.Final-redhat-SNAPSHOT.jar:7.3.0.Final-redhat-SNAPSHOT] [Host Controller] at org.jboss.as.controller.ProxyStepHandler.execute(ProxyStepHandler.java:130) [jboss-as-controller-7.3.0.Final-redhat-SNAPSHOT.jar:7.3.0.Final-redhat-SNAPSHOT] [Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:624) [jboss-as-controller-7.3.0.Final-redhat-SNAPSHOT.jar:7.3.0.Final-redhat-SNAPSHOT] ..... [Host Controller] Caused by: java.io.IOException: JBAS012175: Channel closed [Host Controller] at org.jboss.as.host.controller.ManagedServerProxy$DisconnectedProtocolClient.execute(ManagedServerProxy.java:114) [Host Controller] at org.jboss.as.host.controller.ManagedServerProxy.execute(ManagedServerProxy.java:92) [Host Controller] at org.jboss.as.host.controller.ManagedServerProxy.execute(ManagedServerProxy.java:80) [Host Controller] at org.jboss.as.controller.remote.RemoteProxyController.execute(RemoteProxyController.java:159) [jboss-as-controller-7.3.0.Final-redhat-SNAPSHOT.jar:7.3.0.Final-redhat-SNAPSHOT] [Host Controller] ... 23 more I believe what is going on here is the test is hitting expected behavior. It restarts an HC without restarting the servers. When the HC is reloaded, it is aware that it has disconnected servers. While it awaits reconnect, any attempt to send an op through to the disconnected server will get the exception above. If my analysis is correct, then the test just needs adjusting to check server status before continuing on. If it's incorrect and this shouldn't fail, then we have a bug. A 3rd option is it's correct, but the behavior is bad. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2139) ProxyStepHandler/Controller need to check access before attempting to read information

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2139?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2139: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1011994|https://bugzilla.redhat.com/show_bug.cgi?id=1011994] from NEW to POST > ProxyStepHandler/Controller need to check access before attempting to read information > -------------------------------------------------------------------------------------- > > Key: WFLY-2139 > URL: https://issues.jboss.org/browse/WFLY-2139 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management, Security > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 8.0.0.Beta1 > > > This affects things like recursive :read-resource(-description) :read-children-resources and so on. The problem as it stands is that if you have, say, a host scoped role scoped to host=master, and there is also a slave host controller, and you try to :read-resource(recursive=true,proxies=true), the master will list the slave host controller in its list of child addresses. It will then execute /host=slave:read-resource(recursive=true,proxies=true), which will fail and roll back the tx since the master host scoped role does not have access to that resource. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-277) Trait Handles are not (de)serialized correctly

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-277: ------------------------------------- Summary: Trait Handles are not (de)serialized correctly Key: DROOLS-277 URL: https://issues.jboss.org/browse/DROOLS-277 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.CR3, 5.5.0.Final Reporter: Davide Sottara Assignee: Mark Proctor TraitFactHandles are not covered by the Protobuf Input/Output Marshallers, which return normal fact handles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2173) Get subsystem test framework working with AS 7.2.0 legacy controller

by Kabir Khan (JIRA)

Kabir Khan created WFLY-2173: -------------------------------- Summary: Get subsystem test framework working with AS 7.2.0 legacy controller Key: WFLY-2173 URL: https://issues.jboss.org/browse/WFLY-2173 Project: WildFly Issue Type: Feature Request Components: Domain Management Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 8.0.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1759) Existing management WS section improvements / consolidation

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-1759?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on WFLY-1759: --------------------------------------- Also see https://github.com/wildfly/wildfly/pull/5162 > Existing management WS section improvements / consolidation > ----------------------------------------------------------- > > Key: WFLY-1759 > URL: https://issues.jboss.org/browse/WFLY-1759 > Project: WildFly > Issue Type: Enhancement > Components: Web Services > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: 8.0.0.Beta1 > > > We need to clarify the ws integration behavior when user provides not valid or undefined values in the webservices section of the domain. It's also not clear what the stack does after values are set in fields requiring re-load. > We should also consider creating services for EndpointConfigAdd/Remove, HandlerAdd/Remove, HandlerChainAdd/Remove, PropertyAdd/Remove (at least for the first couple), similarly to what has been done for ClientConfigAdd/Remove in WFLY-227. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-276) Stream mode with CR4-Pre1 generates rules looping

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-276?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated DROOLS-276: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1012933 > Stream mode with CR4-Pre1 generates rules looping > -------------------------------------------------- > > Key: DROOLS-276 > URL: https://issues.jboss.org/browse/DROOLS-276 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.CR4 > Environment: Drools 6.0.0.CR4-Pre1 > Reporter: Richard Bourner > Assignee: Mark Proctor > Attachments: Drools6Stream.zip > > > When in STREAM mode, our rules are looping because of an update. > The attached example doesn't demonstrate the looping but one rule is fired twice where it should only fire once. We are supposing that the issue is the same. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-276) Stream mode with CR4-Pre1 generates rules looping

by Richard Bourner (JIRA)

[ https://issues.jboss.org/browse/DROOLS-276?page=com.atlassian.jira.plugin... ] Richard Bourner updated DROOLS-276: ----------------------------------- Attachment: Drools6Stream.zip > Stream mode with CR4-Pre1 generates rules looping > -------------------------------------------------- > > Key: DROOLS-276 > URL: https://issues.jboss.org/browse/DROOLS-276 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.CR4 > Environment: Drools 6.0.0.CR4-Pre1 > Reporter: Richard Bourner > Assignee: Mark Proctor > Attachments: Drools6Stream.zip > > > When in STREAM mode, our rules are looping because of an update. > The attached example doesn't demonstrate the looping but one rule is fired twice where it should only fire once. We are supposing that the issue is the same. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-276) Stream mode with CR4-Pre1 generates rules looping

by Richard Bourner (JIRA)

Richard Bourner created DROOLS-276: -------------------------------------- Summary: Stream mode with CR4-Pre1 generates rules looping Key: DROOLS-276 URL: https://issues.jboss.org/browse/DROOLS-276 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.CR4 Environment: Drools 6.0.0.CR4-Pre1 Reporter: Richard Bourner Assignee: Mark Proctor When in STREAM mode, our rules are looping because of an update. The attached example doesn't demonstrate the looping but one rule is fired twice where it should only fire once. We are supposing that the issue is the same. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2155) Defining <outbound-connections> in <management> prevents the server to start

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2155?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2155: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1011911|https://bugzilla.redhat.com/show_bug.cgi?id=1011911] from POST to MODIFIED > Defining <outbound-connections> in <management> prevents the server to start > ---------------------------------------------------------------------------- > > Key: WFLY-2155 > URL: https://issues.jboss.org/browse/WFLY-2155 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management > Reporter: Ladislav Thon > Assignee: Darran Lofthouse > Priority: Blocker > Labels: rbac-filed-by-qa > Fix For: 8.0.0.Beta1 > > > If I want to authenticate against LDAP for management purposes, I have to define an LDAP outbound connection in the {{<management>}} section. But once I do this, the server fails to start with this error message: > {code} > 13:18:10,594 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.server.ServerService.boot(ServerService.java:331) [wildfly-server-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:252) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40] > Caused by: java.lang.UnsupportedOperationException > at org.jboss.as.server.parsing.StandaloneXml$ManagementXmlDelegate.parseOutboundConnections(StandaloneXml.java:1314) [wildfly-server-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.domain.management.parsing.ManagementXml.parseManagement_2_0(ManagementXml.java:354) [wildfly-domain-management-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.domain.management.parsing.ManagementXml.parseManagement(ManagementXml.java:282) [wildfly-domain-management-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_4(StandaloneXml.java:453) [wildfly-server-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:145) [wildfly-server-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:107) [wildfly-server-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:104) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > ... 3 more > 13:18:10,598 FATAL [org.jboss.as.server] (Controller Boot Thread) JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. > {code} > To be precise: I take a freshly built WildFly server and add this into {{standalone.xml}} (into the {{<management>}} section): > {code:xml} > <outbound-connections> > <ldap name="ldap" url="ldap://localhost:10389"/> > </outbound-connections> > {code} > Then I try to start the server (using plain old {{./bin/standalone.sh}}). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2013