April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7649) Ensure initial context lookup using the "java:" prefix works with the new naming client

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-7649?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated WFLY-7649: ---------------------------------- Fix Version/s: 11.0.0.Beta1 > Ensure initial context lookup using the "java:" prefix works with the new naming client > --------------------------------------------------------------------------------------- > > Key: WFLY-7649 > URL: https://issues.jboss.org/browse/WFLY-7649 > Project: WildFly > Issue Type: Task > Components: Naming > Reporter: Farah Juma > Assignee: Farah Juma > Fix For: 11.0.0.Beta1 > > > Currently, using the new naming client to perform initial context lookup using the "java:" prefix will result in the following exception: > {code} > WFNAM00026: No provider for found for URI: java > at org.wildfly.naming.client.WildFlyRootContext.getProviderContext(WildFlyRootContext.java:334) > 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) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8563) Boolean attributes CLI autocomplete does not offer true option

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFLY-8563?page=com.atlassian.jira.plugin.... ] Martin Choma closed WFLY-8563. ------------------------------ Resolution: Duplicate Issue > Boolean attributes CLI autocomplete does not offer true option > -------------------------------------------------------------- > > Key: WFLY-8563 > URL: https://issues.jboss.org/browse/WFLY-8563 > Project: WildFly > Issue Type: Bug > Components: CLI > Reporter: Martin Choma > Assignee: Jean-Francois Denise > Priority: Minor > > Having {{debug}} attribute defined as > {code} > "debug" => { > "type" => BOOLEAN, > "description" => "Should the JAAS step of obtaining the credential have debug logging enabled.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "default" => false, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > } > {code} > CLI autocomplete offers just false option > {code} > [standalone@localhost:9990 /] /subsystem=elytron/kerberos-security-factory=a:add(debug<TAB> > ) , =false > {code} > I would expect also true option provided > {code} > [standalone@localhost:9990 /] /subsystem=elytron/kerberos-security-factory=a:add(debug<TAB> > ) , =false =true > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8563) Boolean attributes CLI autocomplete does not offer true option

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFLY-8563?page=com.atlassian.jira.plugin.... ] Jean-Francois Denise reassigned WFLY-8563: ------------------------------------------ Assignee: Jean-Francois Denise (was: Jason Greene) > Boolean attributes CLI autocomplete does not offer true option > -------------------------------------------------------------- > > Key: WFLY-8563 > URL: https://issues.jboss.org/browse/WFLY-8563 > Project: WildFly > Issue Type: Bug > Components: CLI > Reporter: Martin Choma > Assignee: Jean-Francois Denise > Priority: Minor > > Having {{debug}} attribute defined as > {code} > "debug" => { > "type" => BOOLEAN, > "description" => "Should the JAAS step of obtaining the credential have debug logging enabled.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "default" => false, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > } > {code} > CLI autocomplete offers just false option > {code} > [standalone@localhost:9990 /] /subsystem=elytron/kerberos-security-factory=a:add(debug<TAB> > ) , =false > {code} > I would expect also true option provided > {code} > [standalone@localhost:9990 /] /subsystem=elytron/kerberos-security-factory=a:add(debug<TAB> > ) , =false =true > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1079) SecurityProviderServerMechanismFactory incorrect log message

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/ELY-1079?page=com.atlassian.jira.plugin.s... ] Martin Choma updated ELY-1079: ------------------------------ Description: {code:java|title=SecurityProviderServerMechanismFactory.java} log.tracef("No %s provided by service loader in %s: %s", SERVICE_TYPE, getClass().getSimpleName(), Arrays.toString(providerSupplier.get())); {code} should be {code:java} log.tracef("No %s provided by provider loader in %s: %s", SERVICE_TYPE, getClass().getSimpleName(), Arrays.toString(providerSupplier.get())); {code} It means "service loader" -> "provider loader" was: {code:java|title=SecurityProviderServerMechanismFactory.java} log.tracef("No %s provided by service loader in %s: %s", SERVICE_TYPE, getClass().getSimpleName(), Arrays.toString(providerSupplier.get())); {code} should be {code} log.tracef("No %s provided by provider loader in %s: %s", SERVICE_TYPE, getClass().getSimpleName(), Arrays.toString(providerSupplier.get())); {code} It means "service loader" -> "provider loader" > SecurityProviderServerMechanismFactory incorrect log message > ------------------------------------------------------------ > > Key: ELY-1079 > URL: https://issues.jboss.org/browse/ELY-1079 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Martin Choma > Assignee: Darran Lofthouse > Priority: Minor > > {code:java|title=SecurityProviderServerMechanismFactory.java} > log.tracef("No %s provided by service loader in %s: %s", SERVICE_TYPE, getClass().getSimpleName(), Arrays.toString(providerSupplier.get())); > {code} > should be > {code:java} > log.tracef("No %s provided by provider loader in %s: %s", SERVICE_TYPE, getClass().getSimpleName(), Arrays.toString(providerSupplier.get())); > {code} > It means "service loader" -> "provider loader" -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1079) SecurityProviderServerMechanismFactory incorrect log message

by Martin Choma (JIRA)

Martin Choma created ELY-1079: --------------------------------- Summary: SecurityProviderServerMechanismFactory incorrect log message Key: ELY-1079 URL: https://issues.jboss.org/browse/ELY-1079 Project: WildFly Elytron Issue Type: Bug Reporter: Martin Choma Assignee: Darran Lofthouse Priority: Minor {code:java|title=SecurityProviderServerMechanismFactory.java} log.tracef("No %s provided by service loader in %s: %s", SERVICE_TYPE, getClass().getSimpleName(), Arrays.toString(providerSupplier.get())); {code} should be {code} log.tracef("No %s provided by provider loader in %s: %s", SERVICE_TYPE, getClass().getSimpleName(), Arrays.toString(providerSupplier.get())); {code} It means "service loader" -> "provider loader" -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2068) HTTPSConnectionWithCLITestCase and HTTPSManagementInterfaceTestCase Failing Due To Native Protocol Issue

by Martin Švehla (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2068?page=com.atlassian.jira.plugi... ] Martin Švehla commented on WFCORE-2068: --------------------------------------- Sorry about the priority changes, wrong issue :( > HTTPSConnectionWithCLITestCase and HTTPSManagementInterfaceTestCase Failing Due To Native Protocol Issue > -------------------------------------------------------------------------------------------------------- > > Key: WFCORE-2068 > URL: https://issues.jboss.org/browse/WFCORE-2068 > Project: WildFly Core > Issue Type: Bug > Components: Remoting, Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 3.0.0.Beta15 > > > The listed test case is failing during clean up with the following error: - > {noformat} > java.io.IOException: java.io.IOException: WFLYPRT0054: Channel closed > at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:166) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:135) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:59) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:135) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:110) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:80) > {noformat} > The stage of the test using HTTP Upgrade over a HTTPS connection appears to be working fine, the issue is with the native management interface used for test clean up. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2068) HTTPSConnectionWithCLITestCase and HTTPSManagementInterfaceTestCase Failing Due To Native Protocol Issue

by Martin Švehla (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2068?page=com.atlassian.jira.plugi... ] Martin Švehla updated WFCORE-2068: ---------------------------------- Priority: Blocker (was: Critical) > HTTPSConnectionWithCLITestCase and HTTPSManagementInterfaceTestCase Failing Due To Native Protocol Issue > -------------------------------------------------------------------------------------------------------- > > Key: WFCORE-2068 > URL: https://issues.jboss.org/browse/WFCORE-2068 > Project: WildFly Core > Issue Type: Bug > Components: Remoting, Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 3.0.0.Beta15 > > > The listed test case is failing during clean up with the following error: - > {noformat} > java.io.IOException: java.io.IOException: WFLYPRT0054: Channel closed > at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:166) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:135) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:59) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:135) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:110) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:80) > {noformat} > The stage of the test using HTTP Upgrade over a HTTPS connection appears to be working fine, the issue is with the native management interface used for test clean up. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2068) HTTPSConnectionWithCLITestCase and HTTPSManagementInterfaceTestCase Failing Due To Native Protocol Issue

by Martin Švehla (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2068?page=com.atlassian.jira.plugi... ] Martin Švehla updated WFCORE-2068: ---------------------------------- Priority: Critical (was: Blocker) > HTTPSConnectionWithCLITestCase and HTTPSManagementInterfaceTestCase Failing Due To Native Protocol Issue > -------------------------------------------------------------------------------------------------------- > > Key: WFCORE-2068 > URL: https://issues.jboss.org/browse/WFCORE-2068 > Project: WildFly Core > Issue Type: Bug > Components: Remoting, Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 3.0.0.Beta15 > > > The listed test case is failing during clean up with the following error: - > {noformat} > java.io.IOException: java.io.IOException: WFLYPRT0054: Channel closed > at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:166) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:135) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:59) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:135) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:110) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:80) > {noformat} > The stage of the test using HTTP Upgrade over a HTTPS connection appears to be working fine, the issue is with the native management interface used for test clean up. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8563) Boolean attributes CLI autocomplete does not offer true option

by Martin Choma (JIRA)

Martin Choma created WFLY-8563: ---------------------------------- Summary: Boolean attributes CLI autocomplete does not offer true option Key: WFLY-8563 URL: https://issues.jboss.org/browse/WFLY-8563 Project: WildFly Issue Type: Bug Components: CLI Reporter: Martin Choma Assignee: Jason Greene Priority: Minor Having {{debug}} attribute defined as {code} "debug" => { "type" => BOOLEAN, "description" => "Should the JAAS step of obtaining the credential have debug logging enabled.", "expressions-allowed" => true, "required" => false, "nillable" => true, "default" => false, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "resource-services" } {code} CLI autocomplete offers just false option {code} [standalone@localhost:9990 /] /subsystem=elytron/kerberos-security-factory=a:add(debug<TAB> ) , =false {code} I would expect also true option provided {code} [standalone@localhost:9990 /] /subsystem=elytron/kerberos-security-factory=a:add(debug<TAB> ) , =false =true {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1078) Elytron MatchRule.toString() method throws StringIndexOutOfBoundsException

by Ondrej Lukas (JIRA)

Ondrej Lukas created ELY-1078: --------------------------------- Summary: Elytron MatchRule.toString() method throws StringIndexOutOfBoundsException Key: ELY-1078 URL: https://issues.jboss.org/browse/ELY-1078 Project: WildFly Elytron Issue Type: Bug Reporter: Ondrej Lukas Assignee: Darran Lofthouse Priority: Critical In case when implementation of {{asString(StringBuilder b)}} for MatchRule does not change length of passed parameter (which is 0) then 'java.lang.StringIndexOutOfBoundsException: String index out of range: -1' is thrown for calling {{MatchRule.toString()}} due to calling {{StringBuilder.setLength(-1)}}. e.g. MatchRule {{ALL}} in implementation {{asString(StringBuilder b)}} just returns passed parameter, which results to mentioned exception. Thrown exception: {code} java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.AbstractStringBuilder.setLength(AbstractStringBuilder.java:180) at java.lang.StringBuilder.setLength(StringBuilder.java:76) at org.wildfly.security.auth.client.MatchRule.toString(MatchRule.java:581) ... {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 April 2017