September 2013 - jboss-jira - Jboss List Archives

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

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2173?page=com.atlassian.jira.plugin.... ] Kabir Khan resolved WFLY-2173. ------------------------------ Resolution: Done > 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2087) Administrator should be prevented from modifying super user and auditor roles.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2087?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2087: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1012579|https://bugzilla.redhat.com/show_bug.cgi?id=1012579] from POST to MODIFIED > Administrator should be prevented from modifying super user and auditor roles. > ------------------------------------------------------------------------------ > > Key: WFLY-2087 > URL: https://issues.jboss.org/browse/WFLY-2087 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 8.0.0.Beta1 > > > These roles have maximum privileges in their area, i.e. super user can do everything and auditor can stop changes to the server being logged. > The administrator role should be prevented from modifying these two roles. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2177) org.jboss.logmanager module needs dependency on javax.api for the SocketFactory

by James Perkins (JIRA)

James Perkins created WFLY-2177: ----------------------------------- Summary: org.jboss.logmanager module needs dependency on javax.api for the SocketFactory Key: WFLY-2177 URL: https://issues.jboss.org/browse/WFLY-2177 Project: WildFly Issue Type: Bug Components: Logging Reporter: James Perkins Assignee: James Perkins Fix For: 8.0.0.CR1 The {{javax.net.SocketFactory}} is part of the {{javax.api}} module. Since the {{org.jboss.logmanager}} uses this for the syslog handler on TCP and SSL connections, a dependency on the module is needed. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1765) JDBC object store does not change LOG_STORE_TYPE attribute

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1765?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1765: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1002976|https://bugzilla.redhat.com/show_bug.cgi?id=1002976] from POST to MODIFIED > JDBC object store does not change LOG_STORE_TYPE attribute > ---------------------------------------------------------- > > Key: WFLY-1765 > URL: https://issues.jboss.org/browse/WFLY-1765 > Project: WildFly > Issue Type: Bug > Components: Transactions > Affects Versions: 8.0.0.Alpha3 > Reporter: Ivo Studensky > Assignee: Ivo Studensky > > The transaction subsystem when set up to JDBC object store should keep a note about it in log-store-type attribute as HornetQ object store does. It seems not to be consistent when one object store does this, but others do not. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2028) An exploded war inside an archived ear returns 404

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2028?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2028: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 991244|https://bugzilla.redhat.com/show_bug.cgi?id=991244] from POST to MODIFIED > An exploded war inside an archived ear returns 404 > -------------------------------------------------- > > Key: WFLY-2028 > URL: https://issues.jboss.org/browse/WFLY-2028 > Project: WildFly > Issue Type: Feature Request > Components: EE > Affects Versions: 8.0.0.Alpha4 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > > When an archived ear which includes an exploded war is deployed in EAP 6, the application seems to be deployed successfully but it returns status code 404. > 1. Start EAP 6 standalone mode > 2. Put the attached test.ear to $JBOSS_HOME/standalone/deployments > 3. Access the web application > curl -v http://localhost:8080/test/index.jsp > JBoss returns status code 404. > JBoss returns actual response of web application's content. > Additional info: > Same application works in EAP 5. When an application is an exploded ear which includes an exploded war, it works in EAP 6. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2176) JSF should be able to access the CDI-enabled ValidatorFactory

by Farah Juma (JIRA)

Farah Juma created WFLY-2176: -------------------------------- Summary: JSF should be able to access the CDI-enabled ValidatorFactory Key: WFLY-2176 URL: https://issues.jboss.org/browse/WFLY-2176 Project: WildFly Issue Type: Feature Request Components: JSF Affects Versions: 8.0.0.Alpha4 Reporter: Farah Juma Assignee: Farah Juma Currently, for every deployment that uses JSF, the JSF subsystem adds the org.hibernate.validator module to the deployment. A ValidatorFactory is then obtained via the standard Bean Validation bootstrap strategy. However, a ValidatorFactory obtained this way isn't CDI-enabled. JSF needs to use the EE LazyValidatorFactory instead. -- 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

12 years, 9 months

1
0
0 / 0

[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

12 years, 9 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

12 years, 9 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

12 years, 9 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

12 years, 9 months

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 September 2013