March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11821) Remove ha-singleton-service/with-backups quickstart since it's no longer supported without deprecated API usage

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-11821?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-11821: ---------------------------------- Component/s: Clustering Quickstarts > Remove ha-singleton-service/with-backups quickstart since it's no longer supported without deprecated API usage > --------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11821 > URL: https://issues.jboss.org/browse/WFLY-11821 > Project: WildFly > Issue Type: Task > Components: Clustering, Quickstarts > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > Remove ha-singleton-service/with-backups quickstart since it's no longer supported without deprecated API usage. This is due to MSC-203. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11821) Remove ha-singleton-service/with-backups quickstart since it's no longer supported without deprecated API usage

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-11821?page=com.atlassian.jira.plugin... ] Radoslav Husar reassigned WFLY-11821: ------------------------------------- Assignee: Radoslav Husar (was: Brian Stansberry) > Remove ha-singleton-service/with-backups quickstart since it's no longer supported without deprecated API usage > --------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11821 > URL: https://issues.jboss.org/browse/WFLY-11821 > Project: WildFly > Issue Type: Task > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > Remove ha-singleton-service/with-backups quickstart since it's no longer supported without deprecated API usage. This is due to MSC-203. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11821) Remove ha-singleton-service/with-backups quickstart since it's no longer supported without deprecated API usage

by Radoslav Husar (Jira)

Radoslav Husar created WFLY-11821: ------------------------------------- Summary: Remove ha-singleton-service/with-backups quickstart since it's no longer supported without deprecated API usage Key: WFLY-11821 URL: https://issues.jboss.org/browse/WFLY-11821 Project: WildFly Issue Type: Task Reporter: Radoslav Husar Assignee: Brian Stansberry Remove ha-singleton-service/with-backups quickstart since it's no longer supported without deprecated API usage. This is due to MSC-203. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-631) Move Polarion Test Cases To Approved

by Sunil kondkar (Jira)

[ https://issues.jboss.org/browse/SWSQE-631?page=com.atlassian.jira.plugin.... ] Sunil kondkar resolved SWSQE-631. --------------------------------- Resolution: Done > Move Polarion Test Cases To Approved > ------------------------------------ > > Key: SWSQE-631 > URL: https://issues.jboss.org/browse/SWSQE-631 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matt Mahoney > Assignee: Sunil kondkar > Priority: Major > > There are Polarion Test Cases in Status "Proposed" that need to be "Approve". > Please move the status of these tests cases to Approved: > https://polarion.engineering.redhat.com/polarion/#/project/SwiftSunshine/... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-631) Move Polarion Test Cases To Approved

by Sunil kondkar (Jira)

[ https://issues.jboss.org/browse/SWSQE-631?page=com.atlassian.jira.plugin.... ] Sunil kondkar commented on SWSQE-631: ------------------------------------- The test cases are changed to Approved. > Move Polarion Test Cases To Approved > ------------------------------------ > > Key: SWSQE-631 > URL: https://issues.jboss.org/browse/SWSQE-631 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matt Mahoney > Assignee: Sunil kondkar > Priority: Major > > There are Polarion Test Cases in Status "Proposed" that need to be "Approve". > Please move the status of these tests cases to Approved: > https://polarion.engineering.redhat.com/polarion/#/project/SwiftSunshine/... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-634) Setup Kubernetes Cluster on Packet for Security Audit

by Gary Brown (Jira)

[ https://issues.jboss.org/browse/SWSQE-634?page=com.atlassian.jira.plugin.... ] Gary Brown commented on SWSQE-634: ---------------------------------- FYI, the project has already been setup: https://app.packet.net/projects/40917a22-d63d-4d85-af6a-fb4b93fd14ef Let me know the email addresses of anyone else who needs access to this project. > Setup Kubernetes Cluster on Packet for Security Audit > ----------------------------------------------------- > > Key: SWSQE-634 > URL: https://issues.jboss.org/browse/SWSQE-634 > Project: Kiali QE > Issue Type: Task > Reporter: Kevin Earls > Priority: Major > > [~objectiser] has requested we setup a Kubernetes cluster with Jaeger installed via the operator on Packet. This is needed for a security audit of Jaeger which will be done by a third party at the beginning of April. > I will need admin help with this when someone is available. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11820) Enhance Elytron JDBC Realm documentation

by Darran Lofthouse (Jira)

Darran Lofthouse created WFLY-11820: --------------------------------------- Summary: Enhance Elytron JDBC Realm documentation Key: WFLY-11820 URL: https://issues.jboss.org/browse/WFLY-11820 Project: WildFly Issue Type: Task Components: Documentation, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 17.0.0.Beta1 Presently we have a lot of user questions in relation to the JDBC security realm in WildFly Elytron. As a complex security realm this will benefit from it's own in-depth documentation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11819) max-allowed-connected-nodes element in jboss-ejb-client.xml not used

by Jörg Bäsner (Jira)

[ https://issues.jboss.org/browse/WFLY-11819?page=com.atlassian.jira.plugin... ] Jörg Bäsner updated WFLY-11819: ------------------------------- Environment: (was: In a cluster with used {{remote-outbound-connections}} for remote EJB invocations and a {{clusters}} definition containing the {{max-allowed-connected-nodes}}, like: {code} <jboss-ejb-client xmlns="urn:jboss:ejb-client:1.2"> ... <clusters> <cluster name="ejb" ... max-allowed-connected-nodes="1"> </cluster> </clusters> </client-context> </jboss-ejb-client> {code}) > max-allowed-connected-nodes element in jboss-ejb-client.xml not used > -------------------------------------------------------------------- > > Key: WFLY-11819 > URL: https://issues.jboss.org/browse/WFLY-11819 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 16.0.0.Final > Reporter: Jörg Bäsner > Assignee: Jörg Bäsner > Priority: Major > > An application uses {{remote-outbound-connections}} for remote EJB invocations and the {{jboss-ejb-client.xml}} contains a {{clusters}} definition containing the {{max-allowed-connected-nodes}}, like below: > {code} > <jboss-ejb-client xmlns="urn:jboss:ejb-client:1.2"> > ... > <clusters> > <cluster name="ejb" ... max-allowed-connected-nodes="20"> > </cluster> > </clusters> > </client-context> > </jboss-ejb-client> > {code} > In the actually used {{EJBClientContext}} this value doesn't get assigned and the hard coded default value of _10_ is being used. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-634) Setup Kubernetes Cluster on Packet for Security Audit

by Kevin Earls (Jira)

Kevin Earls created SWSQE-634: --------------------------------- Summary: Setup Kubernetes Cluster on Packet for Security Audit Key: SWSQE-634 URL: https://issues.jboss.org/browse/SWSQE-634 Project: Kiali QE Issue Type: Task Reporter: Kevin Earls [~objectiser] has requested we setup a Kubernetes cluster with Jaeger installed via the operator on Packet. This is needed for a security audit of Jaeger which will be done by a third party at the beginning of April. I will need admin help with this when someone is available. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11819) max-allowed-connected-nodes element in jboss-ejb-client.xml not used

by Jörg Bäsner (Jira)

[ https://issues.jboss.org/browse/WFLY-11819?page=com.atlassian.jira.plugin... ] Jörg Bäsner updated WFLY-11819: ------------------------------- Description: An application uses {{remote-outbound-connections}} for remote EJB invocations and the {{jboss-ejb-client.xml}} contains a {{clusters}} definition containing the {{max-allowed-connected-nodes}}, like below: {code} <jboss-ejb-client xmlns="urn:jboss:ejb-client:1.2"> ... <clusters> <cluster name="ejb" ... max-allowed-connected-nodes="20"> </cluster> </clusters> </client-context> </jboss-ejb-client> {code} In the actually used {{EJBClientContext}} this value doesn't get assigned and the hard coded default value of _10_ is being used. was: An application uses {{remote-outbound-connections}} for remote EJB invocations and the {{jboss-ejb-client.xml}} contains a {{clusters}} definition containing the {{max-allowed-connected-nodes}}, like below: {code} <jboss-ejb-client xmlns="urn:jboss:ejb-client:1.2"> ... <clusters> <cluster name="ejb" ... max-allowed-connected-nodes="20"> </cluster> </clusters> </client-context> </jboss-ejb-client> {code} In the actually used {{EJBClientContext}} this value doesn't get assigned and the hard coded default value of _10_ is being used. > max-allowed-connected-nodes element in jboss-ejb-client.xml not used > -------------------------------------------------------------------- > > Key: WFLY-11819 > URL: https://issues.jboss.org/browse/WFLY-11819 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 16.0.0.Final > Environment: In a cluster with used {{remote-outbound-connections}} for remote EJB invocations and a {{clusters}} definition containing the {{max-allowed-connected-nodes}}, like: > {code} > <jboss-ejb-client xmlns="urn:jboss:ejb-client:1.2"> > ... > <clusters> > <cluster name="ejb" ... max-allowed-connected-nodes="1"> > </cluster> > </clusters> > </client-context> > </jboss-ejb-client> > {code} > Reporter: Jörg Bäsner > Assignee: Jörg Bäsner > Priority: Major > > An application uses {{remote-outbound-connections}} for remote EJB invocations and the {{jboss-ejb-client.xml}} contains a {{clusters}} definition containing the {{max-allowed-connected-nodes}}, like below: > {code} > <jboss-ejb-client xmlns="urn:jboss:ejb-client:1.2"> > ... > <clusters> > <cluster name="ejb" ... max-allowed-connected-nodes="20"> > </cluster> > </clusters> > </client-context> > </jboss-ejb-client> > {code} > In the actually used {{EJBClientContext}} this value doesn't get assigned and the hard coded default value of _10_ is being used. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 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 March 2019