March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2530) :read-boot-errors() operation does not follow its operation description

by Harald Pehl (JIRA)

Harald Pehl created WFCORE-2530: ----------------------------------- Summary: :read-boot-errors() operation does not follow its operation description Key: WFCORE-2530 URL: https://issues.jboss.org/browse/WFCORE-2530 Project: WildFly Core Issue Type: Bug Reporter: Harald Pehl The reply properties of the {{:read-boot-errors()}} operation lists the attribute {{missing-transitive-dependency-problems}} which is defined as {code} "missing-transitive-dependency-problems" => { "type" => OBJECT, "description" => "Missing transitive dependency issues found during execution of the operation.", "expressions-allowed" => false, "required" => false, "nillable" => true, "value-type" => { "services-missing-transitive-dependencies" => { "type" => LIST, "description" => "Services that had a missing transitive dependency.", "expressions-allowed" => false, "required" => true, "nillable" => false, "value-type" => STRING }, "possible-causes" => { "type" => LIST, "description" => "Services that are missing and may be the cause of the missing transitive dependency.", "expressions-allowed" => false, "required" => true, "nillable" => false, "value-type" => STRING } } } {code} However the result uses the string "Services that were unable to start:" and "Services that may be the cause:" instead of {{services-missing-transitive-dependencies}} and {{possible-causes}}: {code} ... "missing-transitive-dependency-problems" => { "Services that were unable to start:" => ["jboss.messaging-activemq.default.jms.manager"], "Services that may be the cause:" => [ "jboss.http-upgrade-registry.default", "jboss.remoting.remotingConnectorInfoService.http-remoting-connector" ] } ... {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-764) Delete the dependency to commons-lang 2 in all poms in Drools and jBPM (use commons-lang 3 instead)

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-764?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer commented on DROOLS-764: ----------------------------------------------- upgrading guvnor/guvnor-ala/guvnor-ala-spi/pom from <dependency> <groupId>commons-lang</groupId> <artifactId>commons-lang</artifactId> </dependency> to <dependency> <groupId>org.apache.commons</groupId> <artifactId>commons-lang3</artifactId> </dependency> finds 2 illegal transitive type dependencies in artifact 'org.guvnor:guvnor-ala-spi:jar:7.0.0-SNAPSHOT': 1.) org.apache.commons.lang.text.StrLookup 2.) org.apache.commons.lang.text.StrSubstitutor https://gist.github.com/mbiarnes/10c4df6e41976889aa6688c60b6c2874 > Delete the dependency to commons-lang 2 in all poms in Drools and jBPM (use commons-lang 3 instead) > --------------------------------------------------------------------------------------------------- > > Key: DROOLS-764 > URL: https://issues.jboss.org/browse/DROOLS-764 > Project: Drools > Issue Type: Task > Reporter: Geoffrey De Smet > Assignee: Michael Biarnes Kiefer > Priority: Minor > > Make an inventory of all modules that still use commons-lang and ask their owners to replace the commons-lang 2 usage with commons-lang 3. > See recipe below how they can quickly do that. > Once all our modules are upgraded, see if we can remove the commons-lang 2 dependency as much as possible (including the ip-bom hopefully). > {code} > Currently we have commons-lang 2.6 and 3.1 in our classpath > (which is not a problem because they use a different package namespace). > Nevertheless, having it twice doesn't look good > and 2.6 might miss security fixes. > Luckily upgrading is easy (it took me 15 minutes for optaplanner): > 1) Replace: > <dependency> > <groupId>commons-lang</groupId> > <artifactId>commons-lang</artifactId> > </dependency> > with > <dependency> > <groupId>org.apache.commons</groupId> > <artifactId>commons-lang3</artifactId> > </dependency> > (Both are already in the ip-bom, so no need to worry about <version>) > 2) Replace "import org.apache.commons.lang." > with "import org.apache.commons.lang3." > I had about 170 occurrences. > 3) Compile. If you have a compile error, look for that class on: > https://commons.apache.org/proper/commons-lang/article3_0.html > I only had 1 error. Replacing "StringEscapeUtils.escapeHtml(s)" > with "StringEscapeUtils.ESCAPE_HTML4.translate(s)" fixed that. > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2529) Elytron Client with Management CLI still prompts for password

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2529?page=com.atlassian.jira.plugi... ] Bartosz Baranowski updated WFCORE-2529: --------------------------------------- Component/s: Security > Elytron Client with Management CLI still prompts for password > ------------------------------------------------------------- > > Key: WFCORE-2529 > URL: https://issues.jboss.org/browse/WFCORE-2529 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Bartosz Baranowski > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2529) Elytron Client with Management CLI still prompts for password

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2529?page=com.atlassian.jira.plugi... ] Bartosz Baranowski reassigned WFCORE-2529: ------------------------------------------ Assignee: Bartosz Baranowski > Elytron Client with Management CLI still prompts for password > ------------------------------------------------------------- > > Key: WFCORE-2529 > URL: https://issues.jboss.org/browse/WFCORE-2529 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2529) Elytron Client with Management CLI still prompts for password

by Bartosz Baranowski (JIRA)

Bartosz Baranowski created WFCORE-2529: ------------------------------------------ Summary: Elytron Client with Management CLI still prompts for password Key: WFCORE-2529 URL: https://issues.jboss.org/browse/WFCORE-2529 Project: WildFly Core Issue Type: Bug Reporter: Bartosz Baranowski -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-989) Create tests for AuthenticationContext

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/ELY-989?page=com.atlassian.jira.plugin.sy... ] Ondrej Lukas updated ELY-989: ----------------------------- Fix Version/s: 1.1.0.Beta29 > Create tests for AuthenticationContext > -------------------------------------- > > Key: ELY-989 > URL: https://issues.jboss.org/browse/ELY-989 > Project: WildFly Elytron > Issue Type: Bug > Components: Testsuite > Affects Versions: 1.1.0.Beta28 > Reporter: Ondrej Lukas > Assignee: Ondrej Lukas > Fix For: 1.1.0.Beta29 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8356) (7.1.0.DR12) jboss-client.jar cannot be used for remote JNDI lookup - "javax.naming.OperationNotSupportedException: WFNAM00026: No provider for found for URI: null"

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-8356?page=com.atlassian.jira.plugin.... ] Stuart Douglas moved JBEAP-9536 to WFLY-8356: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8356 (was: JBEAP-9536) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS Naming (was: JMS) (was: Naming) Affects Version/s: (was: 7.1.0.DR12) (was: 7.1.0.DR13) Affects Testing: (was: Regression,Blocks Testing) > (7.1.0.DR12) jboss-client.jar cannot be used for remote JNDI lookup - "javax.naming.OperationNotSupportedException: WFNAM00026: No provider for found for URI: null" > -------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-8356 > URL: https://issues.jboss.org/browse/WFLY-8356 > Project: WildFly > Issue Type: Bug > Components: JMS, Naming > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Priority: Blocker > Labels: eap71_alpha > > Customer impact: Customer cannot use jboss-client.jar (from 7.1.0.DR12) in its client application to perform remote JNDI lookup to server. This affects most basic JMS scenarios and is regression against EAP 7.0.0 and EAP 7.1.0.DR11. > Exception thrown from client when performing JNDI lookup: > {code} > javax.naming.OperationNotSupportedException: WFNAM00026: No provider for found for URI: null > at org.wildfly.naming.client.WildFlyRootContext.getProviderContext(WildFlyRootContext.java:488) > at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:127) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at ProducerTransSession.run(ProducerTransSession.java:91) > Producer got exception and ended:javax.naming.OperationNotSupportedException: WFNAM00026: No provider for found for URI: null > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8355) jdr is not reporting the name of zip file created

by Brad Maxwell (JIRA)

[ https://issues.jboss.org/browse/WFLY-8355?page=com.atlassian.jira.plugin.... ] Brad Maxwell moved JBEAP-9534 to WFLY-8355: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8355 (was: JBEAP-9534) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JDR (was: JDR) Affects Version/s: (was: 7.1.0.DR8) Affects Testing: (was: Regression) > jdr is not reporting the name of zip file created > ------------------------------------------------- > > Key: WFLY-8355 > URL: https://issues.jboss.org/browse/WFLY-8355 > Project: WildFly > Issue Type: Bug > Components: JDR > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Priority: Critical > > JDR don't report name of created zip file > This is regression against EAP 7.0.0 and EAP 7.1.0.DR7 > *Steps to reproduce:* > # ./standalone.sh > # ./jdr.sh > *Actual results:* > {noformat} > [mkopecky@dhcp-10-40-4-133 bin]$ ./jdr.sh > Initializing JBoss Diagnostic Reporter... > [mkopecky@dhcp-10-40-4-133 bin]$ > {noformat} > *Expected results:* > {noformat} > [mkopecky@dhcp-10-40-4-133 bin]$ ./jdr.sh > Initializing JBoss Diagnostic Reporter... > JDR started: Fri Nov 25 13:25:49 CET 2016 > JDR ended: Fri Nov 25 13:25:51 CET 2016 > JDR location: /home/mkopecky/playground/eap/7.1.0.DR6/jboss-eap-7.1/standalone/tmp/jdr_16-11-25_01-25-49_dhcp-10-40-4-133.zip > [mkopecky@dhcp-10-40-4-133 bin]$ > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7215) Reintroduce JNDI over HTTP/HTTPS capability

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7215?page=com.atlassian.jira.plugin.... ] Stuart Douglas resolved WFLY-7215. ---------------------------------- Fix Version/s: 11.0.0.Alpha1 Resolution: Done > Reintroduce JNDI over HTTP/HTTPS capability > ------------------------------------------- > > Key: WFLY-7215 > URL: https://issues.jboss.org/browse/WFLY-7215 > Project: WildFly > Issue Type: Feature Request > Components: Naming, Security, Web (Undertow) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1958) Clean up testsuite Elytron registration

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1958?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-1958: ---------------------------------------- Fix Version/s: 3.0.0.Beta8 (was: 3.0.0.Beta9) Assignee: Brian Stansberry (was: Darran Lofthouse) Resolution: Done I cloned this to WFCORE-2528 – a separate issue for VaultPasswordsInCLITestCase. So I'm going to resolve this based on the RBAC tests being enabled now. > Clean up testsuite Elytron registration > --------------------------------------- > > Key: WFCORE-1958 > URL: https://issues.jboss.org/browse/WFCORE-1958 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Reporter: Darran Lofthouse > Assignee: Brian Stansberry > Priority: Blocker > Fix For: 3.0.0.Beta8 > > > In a couple of places we have artificially registered the WildFly Elytron Security provider, we need to address this so tests can automatically have it available to them.. > Also re-enable the following test case: - > * org.jboss.as.test.integration.domain.suites.FullRbacProviderRunAsTestSuite -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 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 March 2017