January 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7865) We cannot define CS file location outside of EAP directory

by Hynek Švábek (JIRA)

Hynek Švábek created WFLY-7865: ---------------------------------- Summary: We cannot define CS file location outside of EAP directory Key: WFLY-7865 URL: https://issues.jboss.org/browse/WFLY-7865 Project: WildFly Issue Type: Bug Components: Security Reporter: Hynek Švábek Assignee: Darran Lofthouse Priority: Critical We aren't able define location of CS file outside of EAP directory. When user has CS file on NFS he isn't able to reach this file. Define CS file location to JBOSS_HOME/Standalone/data directory: {code} /subsystem=elytron/credential-store=CredStore001:add(uri="cr-store://test/cs123.jceks?create.storage=true", credential-reference={clear-text=pass123}, relative-to=jboss.server.data.dir) {code} When I try set relative to TEMP directory: {code} /subsystem=elytron/credential-store=CredStore002:add(uri="cr-store://test/cs123.jceks?create.storage=true", credential-reference={clear-text=pass123}, relative-to=java.io.tmpdir) {code} I get this error {code} { "outcome" => "failed", "failure-description" => { "WFLYCTL0412: Required services that are not installed:" => ["jboss.server.path.\"java.io.tmpdir\""], "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.credential-store.CredStore002 is missing [jboss.server.path.\"java.io.tmpdir\"]"] }, "rolled-back" => true } {code} *NOTE:* *relative-to* is resolved here https://github.com/wildfly-security/elytron-subsystem/blob/c223be428b9a6f... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7538) WebSocketTestCase fails with security manager - Reenable the test

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-7538?page=com.atlassian.jira.plugin.... ] Ivo Studensky updated WFLY-7538: -------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/9506 (was: https://github.com/wildfly/wildfly/pull/9421) > WebSocketTestCase fails with security manager - Reenable the test > ----------------------------------------------------------------- > > Key: WFLY-7538 > URL: https://issues.jboss.org/browse/WFLY-7538 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Kabir Khan > Assignee: Darran Lofthouse > Priority: Blocker > Labels: downstream_dependency > Fix For: 11.0.0.Alpha1 > > > Reenable WebSocketsTestCase. See WFLY-7539 for more details -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7864) Missing dependency in wildfly-jms-client-bom

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-7864?page=com.atlassian.jira.plugin.... ] Jeff Mesnil moved JBEAP-8177 to WFLY-7864: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7864 (was: JBEAP-8177) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: JMS) (was: User Experience) Affects Version/s: (was: 7.1.0.DR10) Affects Testing: (was: Regression) > Missing dependency in wildfly-jms-client-bom > -------------------------------------------- > > Key: WFLY-7864 > URL: https://issues.jboss.org/browse/WFLY-7864 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Blocker > > I am unable to do JNDI lookup if I use only wildfly-jms-client-bom. I see the following exception > {code} > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NoClassDefFoundError: org/jboss/modules/ModuleLoadException > at org.jboss.remoting3.EndpointBuilder.build(EndpointBuilder.java:117) > at org.jboss.remoting3.ConfigurationEndpointSupplier.lambda$static$0(ConfigurationEndpointSupplier.java:68) > at java.security.AccessController.doPrivileged(Native Method) > at org.jboss.remoting3.ConfigurationEndpointSupplier.<clinit>(ConfigurationEndpointSupplier.java:48) > at org.wildfly.common.context.ContextManager.setGlobalDefaultSupplierIfNotSet(ContextManager.java:108) > at org.jboss.remoting3.Endpoint.lambda$static$0(Endpoint.java:58) > at java.security.AccessController.doPrivileged(Native Method) > at org.jboss.remoting3.Endpoint.<clinit>(Endpoint.java:56) > at org.wildfly.naming.client.remote.RemoteNamingProviderFactory.supportsUriScheme(RemoteNamingProviderFactory.java:70) > at org.wildfly.naming.client.WildFlyRootContext.getProviderContext(WildFlyRootContext.java:318) > at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:123) > at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at org.jboss.as.quickstarts.jms.HelloWorldJMSClient.main(HelloWorldJMSClient.java:62) > ... 6 more > Caused by: java.lang.ClassNotFoundException: org.jboss.modules.ModuleLoadException > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > ... 20 more > {code} > This issue was marked as Blocker because there shouldn't be needed any additional dependencies if wildfly-jms-client-bom is used. > *Customer impact:* Standalone clients doesn't work out of the box and programmer has to append additional dependency. This is serious user experience issue. Quickstarts do not work as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7863) Allow expressions in credential-reference attributes

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFLY-7863?page=com.atlassian.jira.plugin.... ] Martin Choma updated WFLY-7863: ------------------------------- Labels: user_experience (was: ) > Allow expressions in credential-reference attributes > ---------------------------------------------------- > > Key: WFLY-7863 > URL: https://issues.jboss.org/browse/WFLY-7863 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > Labels: user_experience > > Change these attributes to {{"expressions-allowed" => true}} > {code} > These applies to key-store and key-manager: > */credential-reference/alias > */credential-reference/type > */credential-reference/clear-text > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7863) Allow expressions in credential-reference attributes

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFLY-7863?page=com.atlassian.jira.plugin.... ] Martin Choma moved JBEAP-8176 to WFLY-7863: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7863 (was: JBEAP-8176) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) (was: User Experience) Affects Version/s: 11.0.0.Alpha1 (was: 7.1.0.DR10) > Allow expressions in credential-reference attributes > ---------------------------------------------------- > > Key: WFLY-7863 > URL: https://issues.jboss.org/browse/WFLY-7863 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > > Change these attributes to {{"expressions-allowed" => true}} > {code} > These applies to key-store and key-manager: > */credential-reference/alias > */credential-reference/type > */credential-reference/clear-text > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7862) Outdated deployment-scanner xml snippet in deployments readme.txt

by Petr Sakař (JIRA)

[ https://issues.jboss.org/browse/WFLY-7862?page=com.atlassian.jira.plugin.... ] Petr Sakař moved JBEAP-8174 to WFLY-7862: ----------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7862 (was: JBEAP-8174) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Documentation (was: Deployment Scanner) (was: User Experience) Affects Version/s: 10.1.0.Final (was: 7.1.0.DR7) Release Notes Docs Status: (was: Not Required) > Outdated deployment-scanner xml snippet in deployments readme.txt > ----------------------------------------------------------------- > > Key: WFLY-7862 > URL: https://issues.jboss.org/browse/WFLY-7862 > Project: WildFly > Issue Type: Bug > Components: Documentation > Affects Versions: 10.1.0.Final > Reporter: Petr Sakař > Assignee: Petr Sakař > Priority: Trivial > > $JBOSS_HOME/standalone/deployments/README.txt contains following configuration XML snippet: > {code:xml} > <deployment-scanner scan-interval="5000" relative-to="jboss.server.base.dir" path="deployments" auto-deploy-zipped="true" auto-deploy-exploded="false"/> > {code} > but actual snippet from standalone.xml config file is > {code:xml} > <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" runtime-failure-causes-rollback="${jboss.deployment.scanner.rollback.on.failure:false}"/> > {code} > This might be confusing. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4168) jdr.sh CommandLineMain does not run jdr on the application server

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4168?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-4168: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1410107, https://bugzilla.redhat.com/show_bug.cgi?id=1195507 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1195507) > jdr.sh CommandLineMain does not run jdr on the application server > ----------------------------------------------------------------- > > Key: WFLY-4168 > URL: https://issues.jboss.org/browse/WFLY-4168 > Project: WildFly > Issue Type: Bug > Components: JDR > Affects Versions: 9.0.0.Alpha1 > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Fix For: 9.0.0.Beta1 > > > jdr.sh CommandLineMain does not run jdr on the application server > JDR run via the CLI / Managemenet API - runs the JDR report in the Application Server's JVM > /subsystem=jdr:generate-jdr-report() > Running jdr.sh / jdr.bat runs the JDR report in the JDR JVM > jdr.sh / jdr.bat should run the JDR report in the Application Server's JVM if it is running. If it is not running, then it should just collect the files that are available. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2157) Full-replace rollback is failing with java.util.NoSuchElementException: No child 'name' exists: java.util.NoSuchElementException: No child > 'name' exists

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2157?page=com.atlassian.jira.plugi... ] Lin Gao updated WFCORE-2157: ---------------------------- Labels: downstream_dependency (was: ) > Full-replace rollback is failing with java.util.NoSuchElementException: No child 'name' exists: java.util.NoSuchElementException: No child > 'name' exists > ---------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-2157 > URL: https://issues.jboss.org/browse/WFCORE-2157 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 3.0.0.Alpha16 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Labels: downstream_dependency > > 21:24:18,013 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 56) WFLYCTL0190: Step > > handler org.jboss.as.server.deployment.DeploymentHandlerUtil$4@6f678cd for operation {"operation" => "full-replace-deployment","name" => > > "drmk22.ear","enabled" => true,"content" => [{"hash" => bytes { 0x40, 0xde, 0xe4, 0x1d, 0xdd, 0xd0, 0xa7, 0x9f, 0xa9, 0x7a, 0x92, 0x84, > > 0xee, 0x92, 0x81, 0xea, 0x5d, 0x7b, 0xa3, 0x2a }}],"operation-headers" => {"access-mechanism" => "NATIVE","domain-uuid" => > > "cf11aeb2-70b8-4f64-aa64-67fffd9c8080"},"address" => [],"runtime-name" => undefined,"persistent" => true,"owner" => undefined} at address [] > > failed handling operation rollback -- java.util.NoSuchElementException: No child 'name' exists: java.util.NoSuchElementException: No child > > 'name' exists > > at org.jboss.dmr.ModelValue.requireChild(ModelValue.java:387) > > at org.jboss.dmr.ObjectModelValue.requireChild(ObjectModelValue.java:302) > > at org.jboss.dmr.ModelNode.require(ModelNode.java:875) > > at org.jboss.as.server.deployment.DeploymentHandlerUtil$4$1.handleResult(DeploymentHandlerUtil.java:331) > > at org.jboss.as.controller.AbstractOperationContext$Step.invokeResultHandler(AbstractOperationContext.java:1435) > > at org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1417) > > at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1379) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2171) StackOverflowError after repeated management write ops

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-2171: ---------------------------------------- Summary: StackOverflowError after repeated management write ops Key: WFCORE-2171 URL: https://issues.jboss.org/browse/WFCORE-2171 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry I wrote an integration test that allows you to set a system prop and repeatedly call full-replace-deployment (see https://github.com/wildfly/wildfly-core/pull/2062). When I try and run it 30K times I get: 2017-01-09 22:28:40,431 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 3) WFLYCTL0013: Operation ("full-replace-deployment") failed - address: ([]): java.lang.StackOverflowError at java.util.Collections$UnmodifiableCollection.size(Collections.java:1030) at java.util.Collections$UnmodifiableCollection.size(Collections.java:1030) at java.util.Collections$UnmodifiableCollection.size(Collections.java:1030) I think this is due to BasicResource.clone()'s handling of orderedChildResources. It takes the internal set, wraps it in Collections.unmodifiableSet and passes it in to the clone, which in turn will do the same thing if cloned. So for each management write op, the same underlying set gets wrapped in another layer. Hence the overflow of size calls. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6394) Elytron integration with JCA subsystem

by Flavia Rainone (JIRA)

[ https://issues.jboss.org/browse/WFLY-6394?page=com.atlassian.jira.plugin.... ] Flavia Rainone updated WFLY-6394: --------------------------------- Involved: Stefan Guilhen > Elytron integration with JCA subsystem > -------------------------------------- > > Key: WFLY-6394 > URL: https://issues.jboss.org/browse/WFLY-6394 > Project: WildFly > Issue Type: Feature Request > Components: JCA, Security > Reporter: Darran Lofthouse > Assignee: Flavia Rainone > Fix For: 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 January 2017