April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2304) ASYM_ENCRYPT: see if FragmentedMessages are handled correctly

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2304?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2304: --------------------------- Fix Version/s: 5.0.0.Alpha5 (was: 5.0.0.Alpha4) > ASYM_ENCRYPT: see if FragmentedMessages are handled correctly > ------------------------------------------------------------- > > Key: JGRP-2304 > URL: https://issues.redhat.com/browse/JGRP-2304 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0.0.Alpha5 > > > Check the following scenario: > * FRAG4 fragments a message into 4 FragmentedMessages > * Confirm that ASYM_ENCRYPT correctly encrypts only the fragments > Ditto for COMPRESS -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2106) Prepare for JDK 11

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2106?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2106: --------------------------- Fix Version/s: 5.0.0.Alpha5 (was: 5.0.0.Alpha4) > Prepare for JDK 11 > ------------------ > > Key: JGRP-2106 > URL: https://issues.redhat.com/browse/JGRP-2106 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0.0.Alpha5 > > > Investigate the changes needed to run with JDK 11. Probably module.info classes are all that's needed. > Other things to investigate: > * Replace {{Condition}} with {{Predicate}} > * Remove {{FORWARD_TO_COORD}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2442) Performance tests

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2442?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2442: --------------------------- Fix Version/s: 5.0.0.Alpha5 (was: 5.0.0.Alpha4) > Performance tests > ----------------- > > Key: JGRP-2442 > URL: https://issues.redhat.com/browse/JGRP-2442 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0.0.Alpha5 > > > Run UPerf/MPerf before releasing 5.0.0.Final. > Performance should be slightly better due to reduced memory pressure (LongMessage, EmptyMessage, one less memory allocation)... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2407) CompositeMessage: collapse into BytesMessage at the receiver

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2407?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2407: --------------------------- Fix Version/s: 5.0.0.Alpha5 (was: 5.0.0.Alpha4) > CompositeMessage: collapse into BytesMessage at the receiver > ------------------------------------------------------------ > > Key: JGRP-2407 > URL: https://issues.redhat.com/browse/JGRP-2407 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0.0.Alpha5 > > > If a sender sends a CompositeMessage, say of an NioMessage of 500 bytes and a BytesMessage of 10 bytes, provide the option to unmarshal the message into a BytesMessage of 510 bytes at the receiver. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-1122) UPI provisioning not working for OCP 4.4

by Filip Brychta (Jira)

Filip Brychta created SWSQE-1122: ------------------------------------ Summary: UPI provisioning not working for OCP 4.4 Key: SWSQE-1122 URL: https://issues.redhat.com/browse/SWSQE-1122 Project: Kiali QE Issue Type: Bug Reporter: Filip Brychta Assignee: Filip Brychta This job is failing for OCP 4.4 - https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/view/infra-jobs/job... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13379) Redirect after "j_security_check" login does not work if URL has no trailing slash

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-13379?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFLY-13379: ------------------------------------ Component/s: Security (was: Server) > Redirect after "j_security_check" login does not work if URL has no trailing slash > ---------------------------------------------------------------------------------- > > Key: WFLY-13379 > URL: https://issues.redhat.com/browse/WFLY-13379 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 19.0.0.Final > Reporter: Wolfgang Knauf > Assignee: Darran Lofthouse > Priority: Major > Attachments: Security.ear, configure.cli, restore-configuration.cli > > > Attached file "Security.ear" contains a web application with a single jsp page "index.jsp" and form based login, which is secured by a Database Identity Store (Elytron). > When calling the root URL of the webapp without specifiying any page and {color:red}*no*{color} trailing slash (http://localhost:8080/SecurityWeb), on WildFly 11 the login form is shown, and then the welcome file "index.jsp" is shown. > On WildFly 19, the login form is shown, and after successful login, there is an error message "404 - Not Found", and the URL in the adress bar changes to http://localhost:8080/j_security_check > It works if the URL is "http://localhost:8080/SecurityWeb/" (trailing slash). It seems WildFly 11 appends the "/" automatically when redirecting to the login form, while WildFly 19 keeps this URL. > To run the sample, you have to add the Elytron config - the script "configure.cli" can be used for this: > jboss-cli.bat --file=path_to\configure.cli > The script "restore-configuration.cli" undoes this configuration. > Username/Password are e.g. "admin"/"admin" - the sample creates a user table based on an ejb and "import.sql" inserts users. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13379) Redirect after "j_security_check" login does not work if URL has no trailing slash

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-13379?page=com.atlassian.jira.plugi... ] Darran Lofthouse reassigned WFLY-13379: --------------------------------------- Assignee: Darran Lofthouse (was: Brian Stansberry) > Redirect after "j_security_check" login does not work if URL has no trailing slash > ---------------------------------------------------------------------------------- > > Key: WFLY-13379 > URL: https://issues.redhat.com/browse/WFLY-13379 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 19.0.0.Final > Reporter: Wolfgang Knauf > Assignee: Darran Lofthouse > Priority: Major > Attachments: Security.ear, configure.cli, restore-configuration.cli > > > Attached file "Security.ear" contains a web application with a single jsp page "index.jsp" and form based login, which is secured by a Database Identity Store (Elytron). > When calling the root URL of the webapp without specifiying any page and {color:red}*no*{color} trailing slash (http://localhost:8080/SecurityWeb), on WildFly 11 the login form is shown, and then the welcome file "index.jsp" is shown. > On WildFly 19, the login form is shown, and after successful login, there is an error message "404 - Not Found", and the URL in the adress bar changes to http://localhost:8080/j_security_check > It works if the URL is "http://localhost:8080/SecurityWeb/" (trailing slash). It seems WildFly 11 appends the "/" automatically when redirecting to the login form, while WildFly 19 keeps this URL. > To run the sample, you have to add the Elytron config - the script "configure.cli" can be used for this: > jboss-cli.bat --file=path_to\configure.cli > The script "restore-configuration.cli" undoes this configuration. > Username/Password are e.g. "admin"/"admin" - the sample creates a user table based on an ejb and "import.sql" inserts users. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12654) Switch from javax.jws:jsr181-api to jakarta.jws:jakarta.jws-api

by Parul Sharma (Jira)

[ https://issues.redhat.com/browse/WFLY-12654?page=com.atlassian.jira.plugi... ] Parul Sharma commented on WFLY-12654: ------------------------------------- Hi [~jim.ma] are you working in this? Thanks, Parul Sharma > Switch from javax.jws:jsr181-api to jakarta.jws:jakarta.jws-api > --------------------------------------------------------------- > > Key: WFLY-12654 > URL: https://issues.redhat.com/browse/WFLY-12654 > Project: WildFly > Issue Type: Task > Components: Web Services > Reporter: Scott Marlow > Assignee: Jim Ma > Priority: Major > Fix For: 20.0.0.Beta1 > > > Update WildFly to use jakarta.jws:jakarta.jws-api from https://github.com/eclipse-ee4j/jws-api, note that version 2.1 is not yet available as mentioned on [https://github.com/eclipse-ee4j/jws-api/issues/48]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-1121) Smee client and github webhooks for new operator repo (kiali-release job)

by Filip Brychta (Jira)

Filip Brychta created SWSQE-1121: ------------------------------------ Summary: Smee client and github webhooks for new operator repo (kiali-release job) Key: SWSQE-1121 URL: https://issues.redhat.com/browse/SWSQE-1121 Project: Kiali QE Issue Type: Sub-task Reporter: Filip Brychta Assignee: Filip Brychta https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/kiali-workflow/... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-1120) Update code coverage job to work with new operator repo

by Filip Brychta (Jira)

Filip Brychta created SWSQE-1120: ------------------------------------ Summary: Update code coverage job to work with new operator repo Key: SWSQE-1120 URL: https://issues.redhat.com/browse/SWSQE-1120 Project: Kiali QE Issue Type: Sub-task Reporter: Filip Brychta Assignee: Filip Brychta -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

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 2020