May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3839) Cannot read-identity of filesystem-realm if change level attribute later

by Claudio Miranda (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3839?page=com.atlassian.jira.plugi... ] Claudio Miranda commented on WFCORE-3839: ----------------------------------------- > Does this prevent changing attribute manually in standalone.xml? No. > Do we have such creation only attributes in model now? There are other attributes that are set on create time only, for example: /profile=full-ha/subsystem=messaging-activemq/server=default/queue=* > Cannot read-identity of filesystem-realm if change level attribute later > ------------------------------------------------------------------------ > > Key: WFCORE-3839 > URL: https://issues.jboss.org/browse/WFCORE-3839 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Claudio Miranda > Assignee: Darran Lofthouse > > Add filesystem-realm, add a identity, then change the levels to 3, the previously added identity cannot be recovered anymore. This is due to the directory structure previously created. Perhaps, the levels attribute should be set at creation time only ? > {code} > [standalone@localhost:9990 /] /subsystem=elytron/filesystem-realm=file_realm1:add(path=file_realm) > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=elytron/filesystem-realm=file_realm1:add-identity(identity=user1) > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=elytron/filesystem-realm=file_realm1:read-identity(identity=user1) > { > "outcome" => "success", > "result" => { > "name" => "user1", > "attributes" => undefined > } > } > [standalone@localhost:9990 /] /subsystem=elytron/filesystem-realm=file_realm1:write-attribute(name=levels,value=3) > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > [standalone@localhost:9990 /] reload > [standalone@localhost:9990 /] /subsystem=elytron/filesystem-realm=file_realm1:read-identity(identity=user1) > { > "outcome" => "failed", > "failure-description" => "WFLYELY01002: Identity with name [user1] not found.", > "rolled-back" => true > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10366) The standalone-picketlink.xml example is missing some JMS config and has misordered attributes in the identity-management subsystem

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-10366?page=com.atlassian.jira.plugin... ] Kabir Khan resolved WFLY-10366. ------------------------------- Fix Version/s: 13.0.0.Beta1 Resolution: Done > The standalone-picketlink.xml example is missing some JMS config and has misordered attributes in the identity-management subsystem > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-10366 > URL: https://issues.jboss.org/browse/WFLY-10366 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 12.0.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 13.0.0.Beta1 > > > The standalone-picketlink.xml example includes the messaging subsystem but doesn't include the standard ee subsystem jms-connection-factory default-binding config. > It also misorders attributes on most of the partition-manager elements. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2548) java.lang.IllegalStateException: Unknown PartType: dialect

by chandra vudumula (JIRA)

chandra vudumula created DROOLS-2548: ---------------------------------------- Summary: java.lang.IllegalStateException: Unknown PartType: dialect Key: DROOLS-2548 URL: https://issues.jboss.org/browse/DROOLS-2548 Project: Drools Issue Type: Bug Reporter: chandra vudumula Assignee: Edson Tirelli org.kie.workbench.common.services.refactoring.backend.server.indexing.AbstractFileIndexer.toKObject Unable to index 'default://master@Repo/rules/src/main/resources/rules/*****.template'. java.lang.IllegalStateException: Unknown PartType: dialect at org.kie.workbench.common.services.refactoring.service.PartType.getPartTypeFromAttribueDescrName(PartType.java:164) at org.drools.workbench.screens.guided.template.server.indexing.GuidedRuleTemplateIndexVisitor.visitRuleAttribute(GuidedRuleTemplateIndexVisitor.java:104) at org.drools.workbench.screens.guided.template.server.indexing.GuidedRuleTemplateIndexVisitor.visit(GuidedRuleTemplateIndexVisitor.java:75) at org.drools.workbench.screens.guided.template.server.indexing.GuidedRuleTemplateIndexVisitor.visitRuleModel(GuidedRuleTemplateIndexVisitor.java:194) at org.drools.workbench.screens.guided.template.server.indexing.GuidedRuleTemplateIndexVisitor.visit(GuidedRuleTemplateIndexVisitor.java:73) at org.drools.workbench.screens.guided.template.server.indexing.GuidedRuleTemplateIndexVisitor.visit(GuidedRuleTemplateIndexVisitor.java:67) at org.drools.workbench.screens.guided.template.server.indexing.GuidedRuleTemplateFileIndexer.fillIndexBuilder(GuidedRuleTemplateFileIndexer.java:55) at org.kie.workbench.common.services.refactoring.backend.server.indexing.AbstractFileIndexer.toKObject(AbstractFileIndexer.java:78) at org.drools.workbench.screens.guided.template.server.indexing.GuidedRuleTemplateFileIndexer$Proxy$_$$_WeldClientProxy.toKObject(Unknown Source) at org.uberfire.ext.metadata.io.BatchIndex$3.visitFile(BatchIndex.java:178) at org.uberfire.ext.metadata.io.BatchIndex$3.visitFile(BatchIndex.java:144) at org.uberfire.java.nio.file.FileTreeWalker.walk(FileTreeWalker.java:71) at org.uberfire.java.nio.file.FileTreeWalker.walk(FileTreeWalker.java:96) at org.uberfire.java.nio.file.FileTreeWalker.walk(FileTreeWalker.java:96) at org.uberfire.java.nio.file.FileTreeWalker.walk(FileTreeWalker.java:96) at org.uberfire.java.nio.file.FileTreeWalker.walk(FileTreeWalker.java:96) at org.uberfire.java.nio.file.FileTreeWalker.walk(FileTreeWalker.java:96) at org.uberfire.java.nio.file.FileTreeWalker.walk(FileTreeWalker.java:96) at org.uberfire.java.nio.file.FileTreeWalker.walk(FileTreeWalker.java:96) at org.uberfire.java.nio.file.FileTreeWalker.walk(FileTreeWalker.java:48) at org.uberfire.java.nio.file.Files.walkFileTree(Files.java:1031) at org.uberfire.java.nio.file.Files.walkFileTree(Files.java:1052) at org.uberfire.ext.metadata.io.BatchIndex.run(BatchIndex.java:142) at org.uberfire.ext.metadata.io.BatchIndex.run(BatchIndex.java:127) at org.uberfire.ext.metadata.io.BatchIndex$1.run(BatchIndex.java:98) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10367) testsuite changes to refect wfly script changes for -secmgr

by R Searls (JIRA)

[ https://issues.jboss.org/browse/WFLY-10367?page=com.atlassian.jira.plugin... ] R Searls closed WFLY-10367. --------------------------- Resolution: Rejected Bug filed in wrong repository. > testsuite changes to refect wfly script changes for -secmgr > ----------------------------------------------------------- > > Key: WFLY-10367 > URL: https://issues.jboss.org/browse/WFLY-10367 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 13.0.0.Beta1 > Reporter: R Searls > Assignee: R Searls > > Changes to tests that test wildfly scripts appclient, wsconsume, wsprovide. > Scripts were changed to support -secmgr. Test changes were needed in order > to refect changes to scripts. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10367) testsuite changes to refect wfly script changes for -secmgr

by R Searls (JIRA)

R Searls created WFLY-10367: ------------------------------- Summary: testsuite changes to refect wfly script changes for -secmgr Key: WFLY-10367 URL: https://issues.jboss.org/browse/WFLY-10367 Project: WildFly Issue Type: Bug Components: Test Suite Affects Versions: 13.0.0.Beta1 Reporter: R Searls Assignee: R Searls Changes to tests that test wildfly scripts appclient, wsconsume, wsprovide. Scripts were changed to support -secmgr. Test changes were needed in order to refect changes to scripts. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3842) Generation of legacy feature pack licenses.xml output varies depending on whether -Pjboss-release is used

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3842?page=com.atlassian.jira.plugi... ] Brian Stansberry reopened WFCORE-3842: -------------------------------------- > Generation of legacy feature pack licenses.xml output varies depending on whether -Pjboss-release is used > --------------------------------------------------------------------------------------------------------- > > Key: WFCORE-3842 > URL: https://issues.jboss.org/browse/WFCORE-3842 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 5.0.0.Alpha7 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 5.0.0.Beta1 > > > The legacy feature pack licenses.xml generation uses the maven-resources-plugin copy-resources goal to copy the core-feature-pack-licenses.xml file from a custom src location to a custom target location, and then runs the licenses-plugin insert-versions goal, using that target file as both an input and an output of that goal. > The problem is using the -Pjboss-release profile causes those executions to occur in a different order. With -Pjboss-release, the copy-resources happens after the insert-versions, removing all effect of the insert-versions. > There are a couple fixes that come to mind. One is moving the copy-resources from prepare-package phase to prepare-resources. The other is dropping the copy-resources altogether and just directly specifying the src file as the input to the insert-versions. > I think I'll go for the latter as the result seems simpler to understand in the future. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9919) Deployment throwing exception on upgrade to JBOSS EAP 7.1

by Sreecharan Challagundla (JIRA)

[ https://issues.jboss.org/browse/WFLY-9919?page=com.atlassian.jira.plugin.... ] Sreecharan Challagundla commented on WFLY-9919: ----------------------------------------------- we do have similar issues.. is this a bug or change in deployment descriptor file structure, do confirm us we need to have hard stop on v7.1.1 patch install. > Deployment throwing exception on upgrade to JBOSS EAP 7.1 > --------------------------------------------------------- > > Key: WFLY-9919 > URL: https://issues.jboss.org/browse/WFLY-9919 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 11.0.0.Final > Reporter: Sainath Machupalli > Assignee: Jason Greene > > Our deployment worked on EAP 7 and we started seeing the below exception when we upgraded to EAP 7.1. > > 2018-02-07 09:19:46,234 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment inner.war > 2018-02-07 09:19:46,239 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.subunit."myEAR.ear"."inner.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."myEAR.ear"."inner.war".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of subdeployment "inner.war" of deployment "myEAR.ear" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.IllegalArgumentException: VFS000025: Given parent ("/content/myEAR.ear/inner.war") is not an ancestor of this virtual file > at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:119) > at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125) > at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125) > at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125) > at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125) > at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125) > at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:112) > at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.createBeanArchiveId(BeanArchiveProcessor.java:348) > at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.processResourceRoot(BeanArchiveProcessor.java:296) > at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.handleResourceRoot(BeanArchiveProcessor.java:237) > at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.access$100(BeanArchiveProcessor.java:206) > at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor.deploy(BeanArchiveProcessor.java:113) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165) > ... 5 more > > Our jboss-deployment-structure.xml is as below. > > <?xml version="1.0" encoding="UTF-8"?> > <jboss-deployment-structure> > <ear-subdeployments-isolated>false</ear-subdeployments-isolated> > <sub-deployment name="inner.war"> > <dependencies> > <module name="org.jboss.remote-naming"/> > </dependencies> > <resources> > <resource-root path="APP-INF/lib/dep1.jar" /> > <resource-root path="APP-INF/lib/dep2.jar" /> > </resources> > </sub-deployment> > </jboss-deployment-structure> > > Our EAR structure is below, > >myEAR.ear > >inner.war > >APP-INF > >lib > >dep1.jar > >dep2.jar > >META-INF > >jboss-deployment-structure.xml > > The same structure and jboss-deployment-structure.xml worked for us on JBOSS EAP 7. > > Is there any change in deployment structure? or is it a BUG? > More details @ https://developer.jboss.org/message/980164#980164 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AG-82) remove deprecated API

by Luis Barreiro (JIRA)

Luis Barreiro created AG-82: ------------------------------- Summary: remove deprecated API Key: AG-82 URL: https://issues.jboss.org/browse/AG-82 Project: Agroal Issue Type: Bug Components: api Affects Versions: 0.5 Reporter: Luis Barreiro Assignee: Luis Barreiro Fix For: 0.6 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3847) Generate component-matrix as part of build

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3847?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-3847: ------------------------------- Fix Version/s: (was: 5.0.0.Beta1) > Generate component-matrix as part of build > ------------------------------------------ > > Key: WFCORE-3847 > URL: https://issues.jboss.org/browse/WFCORE-3847 > Project: WildFly Core > Issue Type: Task > Reporter: David Lloyd > Assignee: Kabir Khan > > Revert the change described in WFCORE-3635. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10366) The standalone-picketlink.xml example is missing some JMS config and has misordered attributes in the identity-management subsystem

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-10366: --------------------------------------- Summary: The standalone-picketlink.xml example is missing some JMS config and has misordered attributes in the identity-management subsystem Key: WFLY-10366 URL: https://issues.jboss.org/browse/WFLY-10366 Project: WildFly Issue Type: Bug Components: Security Affects Versions: 12.0.0.Final Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor The standalone-picketlink.xml example includes the messaging subsystem but doesn't include the standard ee subsystem jms-connection-factory default-binding config. It also misorders attributes on most of the partition-manager elements. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 May 2018