December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2318) Access control exceptions missing for scoped roles

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2318?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-2318: ----------------------------- Fix Version/s: 10.0.0.Final I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 10.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed. > Access control exceptions missing for scoped roles > -------------------------------------------------- > > Key: WFLY-2318 > URL: https://issues.jboss.org/browse/WFLY-2318 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Heiko Braun > Assignee: Harald Pehl > Fix For: 10.0.0.Final > > > The following setup: user with two scoped roles assigned. maintainer for "main-servers", monitor for "other-servers". Requesting the access control meta data for the server group wildcard ]does not include "exceptions". > Expected result: the access control meta data response contains an "exception" for each server group (main-server-group & other-server-group) > {code} > [domain@localhost:9999 /] ./server-group=*:read-resource-description(access-control=trim-descriptions, operations=true){roles=main-servers, other-servers} > { > "outcome" => "success", > "result" => [{ > "address" => [("server-group" => "*")], > "outcome" => "success", > "result" => { > "description" => undefined, > "attributes" => undefined, > "operations" => undefined, > "children" => { > "deployment" => {"model-description" => undefined}, > "system-property" => {"model-description" => undefined}, > "jvm" => {"model-description" => undefined}, > "deployment-overlay" => {"model-description" => undefined} > }, > "access-control" => { > "default" => { > "read" => true, > "write" => true, > "attributes" => { > "socket-binding-port-offset" => { > "read" => true, > "write" => true > }, > "management-subsystem-endpoint" => { > "read" => true, > "write" => false > }, > "socket-binding-group" => { > "read" => true, > "write" => true > }, > "profile" => { > "read" => true, > "write" => true > } > }, > "operations" => { > "read-children-names" => {"execute" => true}, > "read-operation-description" => {"execute" => true}, > "remove" => {"execute" => true}, > "read-resource-description" => {"execute" => true}, > "stop-servers" => {"execute" => true}, > "read-resource" => {"execute" => true}, > "add" => {"execute" => true}, > "read-attribute" => {"execute" => true}, > "whoami" => {"execute" => true}, > "read-children-types" => {"execute" => true}, > "read-operation-names" => {"execute" => true}, > "undefine-attribute" => {"execute" => true}, > "start-servers" => {"execute" => true}, > "read-children-resources" => {"execute" => true}, > "restart-servers" => {"execute" => true}, > "replace-deployment" => {"execute" => true}, > "write-attribute" => {"execute" => true} > } > }, > "exceptions" => {} > } > } > }] > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4905) CacheRemoveHandler can't run in same op as remove of parent cache-container

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4905?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4905: ----------------------------- Fix Version/s: 10.0.0.Final I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 10.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed. > CacheRemoveHandler can't run in same op as remove of parent cache-container > --------------------------------------------------------------------------- > > Key: WFLY-4905 > URL: https://issues.jboss.org/browse/WFLY-4905 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.Alpha4 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 10.0.0.Final > > > CacheRemoveHandler tries to read its parent resource in Stage.RUNTIME, which means it can't run in the same op (say a composite) with a remove of the parent, as the parent resource will be gone by RUNTIME. > This will also interfere with the WFCORE-808 improvement. > Easy fix, as the read of the parent resource looks to be cruft; the data is never used. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1460) WildFly server fails to start with transactions configured to be run with JDBCObject store

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1460?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1460: ----------------------------- Fix Version/s: 10.0.0.Final I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 10.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed. > WildFly server fails to start with transactions configured to be run with JDBCObject store > ------------------------------------------------------------------------------------------ > > Key: WFLY-1460 > URL: https://issues.jboss.org/browse/WFLY-1460 > Project: WildFly > Issue Type: Bug > Components: Transactions > Affects Versions: 8.0.0.Alpha1 > Reporter: Ondra Chaloupka > Assignee: Stefano Maestri > Fix For: 10.0.0.Final > > > In case that you configure transactions subsystem for running with JDBCObject store the app server fails to start because of (it seems so) a circular dependency. > You can expect the exception like: > {code} > ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 52) JBAS014612: Operation ("add") failed - address: ([("subsystem" => "transactions")]): org.jboss.msc.service.CircularDependencyException: Container jboss-as has a circular dependency: [service jboss.txn.ArjunaObjectStoreEnvironment, service jboss.txn.ArjunaRecoveryManager, service jboss.connector.transactionintegration, service jboss.cached-connection-manager, service jboss.data-source.java:jboss/datasources/JDBCObjectDS] > {code} > My assumption came from the configuration similar to this: > {code} > <datasource jta="false" jndi-name="java:jboss/datasources/JDBCObjectDS" pool-name="JDBCObjectDS" enabled="true" use-ccm="false"> > <connection-url>jdbc:postgresql://postgresserver.com:5432/user1</connection-url> > <driver-class>org.postgresql.Driver</driver-class> > <driver>postgresql-9.2-1002.jdbc4.jar</driver> > <security> > <user-name>user1</user-name> > <password>user1</password> > </security> > </datasource> > {code} > and the transaction config looks like this > {code} > <jdbc-store datasource-jndi-name="java:jboss/datasources/JDBCObjectDS" /> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4441) web.xml parser process cannot handle exception for xml file which does not have the encoding attribute

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4441?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4441: ----------------------------- Fix Version/s: 9.0.0.Final > web.xml parser process cannot handle exception for xml file which does not have the encoding attribute > ------------------------------------------------------------------------------------------------------ > > Key: WFLY-4441 > URL: https://issues.jboss.org/browse/WFLY-4441 > Project: WildFly > Issue Type: Bug > Affects Versions: 9.0.0.Alpha1 > Reporter: Tomas Hofman > Assignee: Tomas Hofman > Fix For: 9.0.0.Final > > > Description copied from https://bugzilla.redhat.com/show_bug.cgi?id=1184292 > Description of problem: > When XMLStreamException occurs by web.xml parser process for xml file which does not have the encoding attribute, e.getLocation()[1] is null. We cannot find cause of exception by NullPointerException. > [1] > - org.jboss.as.web.deployment.WebParsingDeploymentProcessor.java > #115 } catch (XMLStreamException e) { > -> #116 throw new DeploymentUnitProcessingException(MESSAGES.failToParseXMLDescriptor(webXml, e.getLocation().getLineNumber(), e.getLocation().getColumnNumber()), e); > #117 } catch (IOException e) { > #118 throw new DeploymentUnitProcessingException(MESSAGES.failToParseXMLDescriptor(webXml), e); > #119 } > Version-Release number of selected component (if applicable): > EAP 6.3.2 > How reproducible: > Attached web.xml for reproducing. > Steps to Reproduce: > 1. Create war application using attached web.xml. > 2. Deploy war to EAP. > 3. Start EAP. > Actual results: > You can confirm NullPointerException. > 15:56:23,190 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."test.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."test.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "test.war" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server-7.4.2.Final-redhat-2.jar:7.4.2.Final-redhat-2] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_71] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_71] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_71] > Caused by: java.lang.NullPointerException > at org.jboss.as.web.deployment.WebParsingDeploymentProcessor.deploy(WebParsingDeploymentProcessor.java:116) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server-7.4.2.Final-redhat-2.jar:7.4.2.Final-redhat-2] > ... 5 more -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1808) Update transaction API 1.2 to 1.0.0.Beta1

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1808?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1808: ----------------------------- Fix Version/s: 9.0.0.Final > Update transaction API 1.2 to 1.0.0.Beta1 > ----------------------------------------- > > Key: WFLY-1808 > URL: https://issues.jboss.org/browse/WFLY-1808 > Project: WildFly > Issue Type: Enhancement > Components: EE > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1739) Certain methods unconditionally invokes itself and may cause infinit loop

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1739?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1739: ----------------------------- Fix Version/s: 9.0.0.Final > Certain methods unconditionally invokes itself and may cause infinit loop > ------------------------------------------------------------------------- > > Key: WFLY-1739 > URL: https://issues.jboss.org/browse/WFLY-1739 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.0.0.Alpha4 > Reporter: Cheng Fang > Assignee: Paul Ferraro > Fix For: 9.0.0.Final > > > FindBugs found 2 instances of such recursive calls: > {code:title=org.jboss.as.clustering.msc.DelegatingServiceTarget} > @Override > public Set<ServiceListener<Object>> getListeners() { > return this.getListeners(); > } > {code} > {code:title=org.wildfly.clustering.web.catalina.session.SessionFacade} > @Override > public boolean isValidInternal() { > return this.isValidInternal(); > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4224) Update all text references from JBoss to Wildfly on kitchensink quickstarts

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4224?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4224: ----------------------------- Fix Version/s: 9.0.0.Final > Update all text references from JBoss to Wildfly on kitchensink quickstarts > --------------------------------------------------------------------------- > > Key: WFLY-4224 > URL: https://issues.jboss.org/browse/WFLY-4224 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Rafael Benevides > Assignee: Rafael Benevides > Fix For: 9.0.0.Final > > > Kitchensink Quickstarts contains a lot of references to JBossAS7 that needs to be updated to WildFly -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4153) Incorrect interface definition in ejb-jar.xml for entity beans shows just NullPointer exception

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4153?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4153: ----------------------------- Fix Version/s: 9.0.0.Final > Incorrect interface definition in ejb-jar.xml for entity beans shows just NullPointer exception > ----------------------------------------------------------------------------------------------- > > Key: WFLY-4153 > URL: https://issues.jboss.org/browse/WFLY-4153 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Minor > Fix For: 9.0.0.Final > > > {noformat} > In case that you specify interface type for entity bean in ejb-jar.xml that does not correspond with definition in the class of the bean then just Null Pointer exception is shown without any other info what's happening. > I mean when you define bean through interface as remote and the ejb-jar.xml describes bean interfaces as local > {code} > public interface SomeBean extends EJBObject { > ... > } > public interface SomeBeanHome extends EJBHome { > ... > } > {code} > and the ejb-jar.xml looks like > {code} > <ejb-jar xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd" version="3.1"> > <enterprise-beans> > <entity> > <ejb-name>SomeBean</ejb-name> > <local-home>package.SomeBeanHome</local-home> > <local>package.SomeBean</local> > <ejb-class>package.SomeBeanBean</ejb-class> > <persistence-type>Bean</persistence-type> > <prim-key-class>java.lang.Integer</prim-key-class> > <reentrant>true</reentrant> > </entity> > </enterprise-beans> > </ejb-jar> > {code} > then NullPointerException is thrown > {code} > ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.deployment.unit."entitybeanbmp.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."entitybeanbmp.jar".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "entitybeanbmp.jar" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_23] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_23] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_23] > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011058: Failed to install component SimpleBMPBean > at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deploy(ComponentInstallProcessor.java:102) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > ... 5 more > Caused by: java.lang.NullPointerException > at org.jboss.as.ejb3.component.entity.EntityBeanObjectViewConfigurator$2.configureDependency(EntityBeanObjectViewConfigurator.java:108) > at org.jboss.as.ejb3.component.entity.EntityBeanObjectViewConfigurator$2.configureDependency(EntityBeanObjectViewConfigurator.java:105) > at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deployComponent(ComponentInstallProcessor.java:139) > at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deploy(ComponentInstallProcessor.java:95) > ... 6 more > {code} > instead of some informative one. > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1695) Web Console: Principal/Role indication in footer

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1695?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1695: ----------------------------- Fix Version/s: 9.0.0.Final > Web Console: Principal/Role indication in footer > ------------------------------------------------ > > Key: WFLY-1695 > URL: https://issues.jboss.org/browse/WFLY-1695 > Project: WildFly > Issue Type: Feature Request > Components: Web Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 9.0.0.Final > > > it should be possible to see the current principal and the active role in the console footer -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4313) Clean-up tests which use Kerberos in the WildFly testsuite

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4313?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4313: ----------------------------- Fix Version/s: 9.0.0.Final > Clean-up tests which use Kerberos in the WildFly testsuite > ---------------------------------------------------------- > > Key: WFLY-4313 > URL: https://issues.jboss.org/browse/WFLY-4313 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Reporter: Josef Cacek > Assignee: Josef Cacek > Fix For: 9.0.0.Final > > > Clean up Kerberos tests and add an unified logic for skipping Kerberos test configurations which proved to be unstable/buggy. By a configuration here is meant combination of Java vendor, version and IP stack. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 December 2017