June 2020 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3309) Investigate using MicroProfile JSON Web Token to secure interaction with an LRA coordinator

by Mayank Kunwar (Jira)

[ https://issues.redhat.com/browse/JBTM-3309?page=com.atlassian.jira.plugin... ] Mayank Kunwar updated JBTM-3309: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1636 > Investigate using MicroProfile JSON Web Token to secure interaction with an LRA coordinator > ------------------------------------------------------------------------------------------- > > Key: JBTM-3309 > URL: https://issues.redhat.com/browse/JBTM-3309 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Affects Versions: 5.10.4.Final > Reporter: Michael Musgrove > Assignee: Mayank Kunwar > Priority: Critical > > The Narayana implementation of the MicroProfile LRA specification uses a JAX-RS filter to communicate with a remote coordinator. The interaction is currently insecure. This issue is to investigate the best way of securing this channel. Since the JAX-RS filter is applied to the MicroProfile service we should initially investigate the MicroProfile security solution (MicroProfile JSON Web Token). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3311) JMH upgrade and code refactor

by Mayank Kunwar (Jira)

[ https://issues.redhat.com/browse/JBTM-3311?page=com.atlassian.jira.plugin... ] Mayank Kunwar updated JBTM-3311: -------------------------------- Fix Version/s: 5.next > JMH upgrade and code refactor > ----------------------------- > > Key: JBTM-3311 > URL: https://issues.redhat.com/browse/JBTM-3311 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Mayank Kunwar > Assignee: Mayank Kunwar > Priority: Major > Fix For: 5.next > > > This JIRA is for updating JMH to its latest version (i.e. 1.23) and code refactoring. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3324) Fix the findings of the static code analysis by Coverity

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3324?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3324: ----------------------------------- Fix Version/s: 5.next > Fix the findings of the static code analysis by Coverity > -------------------------------------------------------- > > Key: JBTM-3324 > URL: https://issues.redhat.com/browse/JBTM-3324 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.10.4.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Minor > Fix For: 5.next > > > I've checked the new records found by Coverity static analysis tool (one running by EAP QE team, with more info on internal page https://mojo.redhat.com/docs/DOC-180330). > There are two bugs that should be considered to be fixed,: > * {{RecoveryManager#terminate}} changes the recovery manager instance to {{null}}. But the {{_recoveryManager}} is a static variable which should be synchorinzed on class not on the instance. Especially when {{#manager(boolean}} method is {{public static}}, see https://github.com/jbosstm/narayana/blob/5.10.5.Final/ArjunaCore/arjuna/c... > * If the {{XAResourceRecord}} is called with {{params != null}} then the check verifies if the params length is with equal or more than the value of constant {{XACONNECTION}}. If the constant {{XACONNECTION}} is zero then for empty params array the access to {{params[0]}} will fail with {{ArrayIndexOutOfBoundsException}}, see https://github.com/jbosstm/narayana/blob/5.10.5.Final/ArjunaJTA/jta/class... > Plus few minor ones. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3308) Some TCK tests pass but leave the LRAs in not finished state

by Martin Stefanko (Jira)

[ https://issues.redhat.com/browse/JBTM-3308?page=com.atlassian.jira.plugin... ] Martin Stefanko edited comment on JBTM-3308 at 6/5/20 8:21 AM: --------------------------------------------------------------- I don't see the way how to link different JBTMs. I will keep the list of forked issues in this comment: * https://issues.redhat.com/browse/JBTM-3312 * https://issues.redhat.com/browse/JBTM-3320 * https://issues.redhat.com/browse/JBTM-3326 was (Author: mstefank): I don't see the way how to link different JBTMs. I will keep the list of forked issues in this comment: * https://issues.redhat.com/browse/JBTM-3312 * https://issues.redhat.com/browse/JBTM-3320 > Some TCK tests pass but leave the LRAs in not finished state > ------------------------------------------------------------ > > Key: JBTM-3308 > URL: https://issues.redhat.com/browse/JBTM-3308 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.4.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > It seems that the LRA is correctly closed but the /lra-coordinator still reports it in Active status. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3326) Nested participant AfterLRA call in complete scenario should be postponed until the parent LRA completes/compensates

by Martin Stefanko (Jira)

[ https://issues.redhat.com/browse/JBTM-3326?page=com.atlassian.jira.plugin... ] Martin Stefanko updated JBTM-3326: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1634 > Nested participant AfterLRA call in complete scenario should be postponed until the parent LRA completes/compensates > -------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-3326 > URL: https://issues.redhat.com/browse/JBTM-3326 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.4.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > Currently, the nested participant enters the H_H state after it completes and the recovery calls the after LRA method in the first pass. This call should be postponed until the parent LRA finishes. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3322) Quickstart shell scripts should consider MFACTOR for any used timeout

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3322?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3322: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.next Resolution: Done > Quickstart shell scripts should consider MFACTOR for any used timeout > --------------------------------------------------------------------- > > Key: JBTM-3322 > URL: https://issues.redhat.com/browse/JBTM-3322 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Quickstarts > Affects Versions: 5.10.4.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > Fix For: 5.next > > > Some of the Narayana quickstarts uses the shell scripts to run the quickstarts. > Some of them use the {{sleep}} or waiting for some time to get response. Any of these attempts which are using timeout to wait/sleep should be using factor of timeout that could be set in jenkins job which starts the quickstarts scripts. > For the Narayana CI AMS the we hit failures where server is not started fast enough and failure occurs. > E.g. in the next snippet the LRA thorntail was not able to start in 10 seconds > {code} > + echo '===== starting service on port 8082' > ===== starting service on port 8082 > + service_pid=22993 > + sleep 10 > + java -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv4Addresses -Dthorntail.http.port=8082 -Dlra.http.port=8080 -Dthorntail.transactions.object-store-path=../txlogs -jar target/lra-participant-example-thorntail.jar > 2020-05-19 07:31:21,337 WARN [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.lra-coordinator.war" is using a private module ("org.jboss.jts") which may be changed or removed in future versions without notice. > 2020-05-19 07:31:21,353 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment lra-coordinator.war > 2020-05-19 07:31:28,225 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: Thorntail 2.6.0.Final (WildFly Core 10.0.3.Final) starting > 2020-05-19 07:31:28,268 INFO [org.wildfly.swarm] (MSC service thread 1-2) THORN0019: Install MSC service for command line args: [] > 2020-05-19 07:31:29,370 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server. > 2020-05-19 07:31:30,942 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0018: Host default-host starting > + '[' '' = true ']' > + echo '===== testing service' > + test_service '1 completed and 0 compensated' > ===== testing service > + curl -4 -X PUT -I http://localhost:8082/cdi > % Total % Received % Xferd Average Speed Time Time Time Current > Dload Upload Total Spent Left Speed > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > 0 74 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > HTTP/1.1 404 Not Found > ... > 2020-05-19 07:31:32,469 INFO [org.jboss.as.server] (main) WFLYSRV0010: Deployed "lra-participant-example.war" (runtime-name : "lra-participant-example.war") > 2020-05-19 07:31:32,475 INFO [org.wildfly.swarm] (main) THORN99999: Thorntail is Ready > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3327) Update Quarkus to 1.5.0.Final

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3327?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3327: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Update Quarkus to 1.5.0.Final > ----------------------------- > > Key: JBTM-3327 > URL: https://issues.redhat.com/browse/JBTM-3327 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.10.4.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > We are still shipping LRA coordinator with Quarkus 0.22.0 which is quite outdated. I would suggest upgrading. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3324) Fix the findings of the static code analysis by Coverity

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3324?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3324: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Fix the findings of the static code analysis by Coverity > -------------------------------------------------------- > > Key: JBTM-3324 > URL: https://issues.redhat.com/browse/JBTM-3324 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.10.4.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Minor > > I've checked the new records found by Coverity static analysis tool (one running by EAP QE team, with more info on internal page https://mojo.redhat.com/docs/DOC-180330). > There are two bugs that should be considered to be fixed,: > * {{RecoveryManager#terminate}} changes the recovery manager instance to {{null}}. But the {{_recoveryManager}} is a static variable which should be synchorinzed on class not on the instance. Especially when {{#manager(boolean}} method is {{public static}}, see https://github.com/jbosstm/narayana/blob/5.10.5.Final/ArjunaCore/arjuna/c... > * If the {{XAResourceRecord}} is called with {{params != null}} then the check verifies if the params length is with equal or more than the value of constant {{XACONNECTION}}. If the constant {{XACONNECTION}} is zero then for empty params array the access to {{params[0]}} will fail with {{ArrayIndexOutOfBoundsException}}, see https://github.com/jbosstm/narayana/blob/5.10.5.Final/ArjunaJTA/jta/class... > Plus few minor ones. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3321) The REST-AT inbound bridge provider wrongly uses the customer priority

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3321?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3321: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > The REST-AT inbound bridge provider wrongly uses the customer priority > ---------------------------------------------------------------------- > > Key: JBTM-3321 > URL: https://issues.redhat.com/browse/JBTM-3321 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.10.4.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > > The current REST-AT inbound bridge wrongly uses the user {{@Priority}} value (https://docs.oracle.com/javaee/7/api/javax/ws/rs/Priorities.html#USER). > The transactional interceptor should not be called at the same time as the user interceptors and it has to go before them. > This is a not expected ordering and it may cause issues when a user adds his own provider. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3311) JMH upgrade and code refactor

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3311?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3311: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > JMH upgrade and code refactor > ----------------------------- > > Key: JBTM-3311 > URL: https://issues.redhat.com/browse/JBTM-3311 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Mayank Kunwar > Assignee: Mayank Kunwar > Priority: Major > > This JIRA is for updating JMH to its latest version (i.e. 1.23) and code refactoring. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues June 2020