June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13600) EJB client over HTTP Fail on Java SE

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13600?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFLY-13600: --------------------------------------- Component/s: EJB (was: Application Client) Assignee: Cheng Fang (was: Brian Stansberry) > EJB client over HTTP Fail on Java SE > ------------------------------------ > > Key: WFLY-13600 > URL: https://issues.redhat.com/browse/WFLY-13600 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 20.0.0.Final > Reporter: Gergely Molnár > Assignee: Cheng Fang > Priority: Major > > Java SE code: > {code:java} > public class Application { > private static final String REMOTE_CALC = "ejb:/remote-ejb/RemoteCalc!" + RemoteCalc.class.getName(); > /** > * Lookup remote \{@link RemoteCalc}. > * > * @return a \{@link RemoteCalc} object > * @throws NamingException Something is wrong > */ > public static RemoteCalc getRemoteCalc() throws NamingException { > Hashtable<String, Object> jndiProps = new Hashtable<>(); > jndiProps.put(Context.INITIAL_CONTEXT_FACTORY, "org.wildfly.naming.client.WildFlyInitialContextFactory"); > // remote+http connection (work fine) > //jndiProps.put(Context.PROVIDER_URL, "remote+http://127.0.0.1:8080/remote-ejb"); > // http connection (fail) > jndiProps.put(Context.PROVIDER_URL, "http://127.0.0.1:8080/wildfly-services"); > Context context = new InitialContext(jndiProps); > return (RemoteCalc) context.lookup(REMOTE_CALC); > } > /** > * Call to run (main). > * > * @param args parameters (not used) > * @throws NamingException Something is wrong > */ > public static void main(String[] args) throws NamingException { > > RemoteCalc remoteCalc = getRemoteCalc(); > System.out.println("Remote calc 95 + 76: " + remoteCalc.add(95, 76)); > } > } > {code} > Exception: > Exception in thread "main" javax.naming.InvalidNameException: WFNAM00007: Invalid URL scheme name "http" > at org.wildfly.naming.client.WildFlyRootContext.getProviderContext(WildFlyRootContext.java:808) > at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:140) > at javax.naming.InitialContext.lookup(Unknown Source) > at com.bosch.emea.bpart.remoteejbclient.Application.getRemoteCalc(Application.java:34) > at com.bosch.emea.bpart.remoteejbclient.Application.main(Application.java:47) > Lib: > {code:java} > @Remote > public interface RemoteCalc { > /** > * Add two integer. > * > * @param a an integer > * @param b an integer > * @return a + b > */ > public int add(int a, int b); > > } > {code} > Config: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <configuration> > <authentication-client xmlns="urn:elytron:1.0"> > <authentication-rules> > <rule use-configuration="default" /> > </authentication-rules> > <authentication-configurations> > <configuration name="default"> > <sasl-mechanism-selector selector="#ALL" /> > <set-mechanism-properties> > <property key="wildfly.sasl.local-user.quiet-auth" value="true" /> > </set-mechanism-properties> > <providers> > <use-service-loader/> > </providers> > </configuration> > </authentication-configurations> > </authentication-client> > </configuration> > {code} > Maven dependency: > {code:xml} > <dependency> > <groupId>org.wildfly</groupId> > <artifactId>wildfly-ejb-client-bom</artifactId> > <version>20.0.0.Final</version> > <type>pom</type> > </dependency> > {code} > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-2003) Upgrading jboss-logmanager to 2.1.17.Final

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-2003?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-2003: ---------------------------- Fix Version/s: 1.13.0.CR2 > Upgrading jboss-logmanager to 2.1.17.Final > ------------------------------------------- > > Key: ELY-2003 > URL: https://issues.redhat.com/browse/ELY-2003 > Project: WildFly Elytron > Issue Type: Component Upgrade > Reporter: Sonia Zaldana > Assignee: Sonia Zaldana > Priority: Major > Fix For: 1.13.0.CR2 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-2003) Upgrading jboss-logmanager to 2.1.17.Final

by Sonia Zaldana (Jira)

[ https://issues.redhat.com/browse/ELY-2003?page=com.atlassian.jira.plugin.... ] Sonia Zaldana updated ELY-2003: ------------------------------- Git Pull Request: https://github.com/wildfly-security/wildfly-elytron/pull/1422 > Upgrading jboss-logmanager to 2.1.17.Final > ------------------------------------------- > > Key: ELY-2003 > URL: https://issues.redhat.com/browse/ELY-2003 > Project: WildFly Elytron > Issue Type: Component Upgrade > Reporter: Sonia Zaldana > Assignee: Sonia Zaldana > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-2003) Upgrading jboss-logmanager to 2.1.17.Final

by Sonia Zaldana (Jira)

[ https://issues.redhat.com/browse/ELY-2003?page=com.atlassian.jira.plugin.... ] Sonia Zaldana reassigned ELY-2003: ---------------------------------- Assignee: Sonia Zaldana (was: Darran Lofthouse) > Upgrading jboss-logmanager to 2.1.17.Final > ------------------------------------------- > > Key: ELY-2003 > URL: https://issues.redhat.com/browse/ELY-2003 > Project: WildFly Elytron > Issue Type: Component Upgrade > Reporter: Sonia Zaldana > Assignee: Sonia Zaldana > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-2003) Upgrading jboss-logmanager to 2.1.17.Final

by Sonia Zaldana (Jira)

Sonia Zaldana created ELY-2003: ---------------------------------- Summary: Upgrading jboss-logmanager to 2.1.17.Final Key: ELY-2003 URL: https://issues.redhat.com/browse/ELY-2003 Project: WildFly Elytron Issue Type: Component Upgrade Reporter: Sonia Zaldana Assignee: Darran Lofthouse -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1984) Add a wrapper HttpServerAuthenticationMechanismFactory that sets the peer address using the current authentication request

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1984?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1984: ---------------------------- Fix Version/s: 1.13.0.CR2 > Add a wrapper HttpServerAuthenticationMechanismFactory that sets the peer address using the current authentication request > -------------------------------------------------------------------------------------------------------------------------- > > Key: ELY-1984 > URL: https://issues.redhat.com/browse/ELY-1984 > Project: WildFly Elytron > Issue Type: Task > Components: HTTP > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.13.0.CR2 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1168) Document alternatives for PSI OpenStack

by Matthew Mahoney (Jira)

[ https://issues.redhat.com/browse/SWSQE-1168?page=com.atlassian.jira.plugi... ] Matthew Mahoney commented on SWSQE-1168: ---------------------------------------- QuickLab for OCP provisioning (4.3 and 4.4): [https://quicklab.upshift.redhat.com|https://quicklab.upshift.redhat.com/] > Document alternatives for PSI OpenStack > --------------------------------------- > > Key: SWSQE-1168 > URL: https://issues.redhat.com/browse/SWSQE-1168 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > When the PSI OpenStack is down, we need to use something else to provisioning OCP clusters. > We need to document options: > * AWS > * https://quicklab.upshift.redhat.com/clusters > * bot on coreos slack -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1077) Kiali Test For Istio.io

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1077?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1077: ---------------------------------- Sprint: Kiali Sprint #32, Kiali Sprint #36, Kiali Sprint #37, Kiali Sprint #38, Kiali Sprint #39, Kiali Sprint #40, Kiali Sprint #41, Kiali Sprint #42 (was: Kiali Sprint #32, Kiali Sprint #36, Kiali Sprint #37, Kiali Sprint #38, Kiali Sprint #39, Kiali Sprint #40, Kiali Sprint #41) > Kiali Test For Istio.io > ----------------------- > > Key: SWSQE-1077 > URL: https://issues.redhat.com/browse/SWSQE-1077 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matthew Mahoney > Priority: Major > Labels: infrastructure > > The Istio.io team is requesting a Kiali test case that can be run on each submitted PR. The purpose of this test case is to validate that Kiali is not broken upon a PR submittal. > Meeting with [~brian.avery] [~gbaufake]: > 1) BrianA to port existing Kiali test case that was developed in old Istio.io test framework to new istiso.io framework > https://github.com/istio/istio/blob/master/tests/e2e/tests/kiali/kiali_te... > 2) Kiali team then to add an api test case(s) via 'curl' to validate the Istio/Kiali integration is properly functioning. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1089) Remove hardcoded waiting for webhook "smcp.validation.maistra.io"

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1089?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1089: ---------------------------------- Sprint: Kiali Sprint #36, Kiali Sprint #37, Kiali Sprint #38, Kiali Sprint #39, Kiali Sprint #40, Kiali Sprint #41, Kiali Sprint #42 (was: Kiali Sprint #36, Kiali Sprint #37, Kiali Sprint #38, Kiali Sprint #39, Kiali Sprint #40, Kiali Sprint #41) > Remove hardcoded waiting for webhook "smcp.validation.maistra.io" > ----------------------------------------------------------------- > > Key: SWSQE-1089 > URL: https://issues.redhat.com/browse/SWSQE-1089 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Optional > Labels: infrastructure > > https://gitlab.cee.redhat.com/istio/kiali-qe/kiali-qe-jenkins-dsl/blob/ma... > There is no need to wait that long. We need some dynamic check. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1155) UI Automations Labels for Applications

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1155?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1155: ---------------------------------- Sprint: Kiali Sprint #41, Kiali Sprint #42 (was: Kiali Sprint #41) > UI Automations Labels for Applications > -------------------------------------- > > Key: SWSQE-1155 > URL: https://issues.redhat.com/browse/SWSQE-1155 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > It is commented and TODO: Service name label should be taken from OC. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2020