May 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3146) Better support for Quarkus

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3146?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #1451 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Better support for Quarkus > -------------------------- > > Key: JBTM-3146 > URL: https://issues.jboss.org/browse/JBTM-3146 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Common > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > To facilitate use of Narayana with containers such as Quarkus we want to minimise things like XML parsing and java archive parsing. The two main enhancements that would be useful in this respect are: > * to inject build information into a java class (via the org.jboss.maven.plugins:maven-injection-plugin plugin); > * to avoid the need for runtime parsing of XML properties it would be useful to allow the properties factory delegate to be supplied externally -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3146) Better support for Quarkus

by Michael Musgrove (Jira)

Michael Musgrove created JBTM-3146: -------------------------------------- Summary: Better support for Quarkus Key: JBTM-3146 URL: https://issues.jboss.org/browse/JBTM-3146 Project: JBoss Transaction Manager Issue Type: Bug Components: Common Affects Versions: 5.9.5.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next To facilitate use of Narayana with containers such as Quarkus we want to minimise things like XML parsing and java archive parsing. The two main enhancements that would be useful in this respect are: * to inject build information into a java class (via the org.jboss.maven.plugins:maven-injection-plugin plugin); * to avoid the need for runtime parsing of XML properties it would be useful to allow the properties factory delegate to be supplied externally -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2924) Add some more trace statement to make it clear which connection modifier is in use for the TransactionalDriver

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-2924?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka closed JBTM-2924. ---------------------------------- > Add some more trace statement to make it clear which connection modifier is in use for the TransactionalDriver > -------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2924 > URL: https://issues.jboss.org/browse/JBTM-2924 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transactional Driver > Reporter: Thomas Jenkinson > Assignee: Thomas Jenkinson > Priority: Minor > Fix For: 5.7.0.Final > > > It is not clear which one is used and whether the override is in effect -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2924) Add some more trace statement to make it clear which connection modifier is in use for the TransactionalDriver

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-2924?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka updated JBTM-2924: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.7.0.Final Resolution: Done I'm setting the resolution to `Done` as there is a merge PR which seems to address the issue. > Add some more trace statement to make it clear which connection modifier is in use for the TransactionalDriver > -------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2924 > URL: https://issues.jboss.org/browse/JBTM-2924 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transactional Driver > Reporter: Thomas Jenkinson > Assignee: Thomas Jenkinson > Priority: Minor > Fix For: 5.7.0.Final > > > It is not clear which one is used and whether the override is in effect -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2924) Add some more trace statement to make it clear which connection modifier is in use for the TransactionalDriver

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-2924?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka updated JBTM-2924: ----------------------------------- Issue Type: Enhancement (was: Component Upgrade) > Add some more trace statement to make it clear which connection modifier is in use for the TransactionalDriver > -------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2924 > URL: https://issues.jboss.org/browse/JBTM-2924 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transactional Driver > Reporter: Thomas Jenkinson > Assignee: Thomas Jenkinson > Priority: Minor > > It is not clear which one is used and whether the override is in effect -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2924) Add some more trace statement to make it clear which connection modifier is in use for the TransactionalDriver

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-2924?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka updated JBTM-2924: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1206 > Add some more trace statement to make it clear which connection modifier is in use for the TransactionalDriver > -------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2924 > URL: https://issues.jboss.org/browse/JBTM-2924 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transactional Driver > Reporter: Thomas Jenkinson > Assignee: Thomas Jenkinson > Priority: Minor > > It is not clear which one is used and whether the override is in effect -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3145) LRA TCK test failure on JDK11

by Michael Musgrove (Jira)

Michael Musgrove created JBTM-3145: -------------------------------------- Summary: LRA TCK test failure on JDK11 Key: JBTM-3145 URL: https://issues.jboss.org/browse/JBTM-3145 Project: JBoss Transaction Manager Issue Type: Bug Components: LRA Affects Versions: 5.9.5.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The test TckTests#timeLimit fails every time on the JDK 11 CI run (but not on JDK 8). For example http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/416/PROFILE=LRA,j... -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3087) Ensure the LRA implementation is up to date

by Martin Stefanko (Jira)

[ https://issues.jboss.org/browse/JBTM-3087?page=com.atlassian.jira.plugin.... ] Martin Stefanko commented on JBTM-3087: --------------------------------------- Next PR - https://github.com/jbosstm/narayana/pull/1450. Versions: {code:xml} <version.microprofile.lra.api>1.0-20190519.061148-384</version.microprofile.lra.api> <version.microprofile.lra.tck>1.0-20190519.061150-384</version.microprofile.lra.tck> {code} > Ensure the LRA implementation is up to date > ------------------------------------------- > > Key: JBTM-3087 > URL: https://issues.jboss.org/browse/JBTM-3087 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The microprofile-lra API has undergone a number of changes recently. The narayana implementation of the specification needs updating to match the new version of it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3136) Verify that Narayaya projects download dependencies via HTTPS

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3136?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3136: ----------------------------------- Security: (was: Security Issue) > Verify that Narayaya projects download dependencies via HTTPS > ------------------------------------------------------------- > > Key: JBTM-3136 > URL: https://issues.jboss.org/browse/JBTM-3136 > Project: JBoss Transaction Manager > Issue Type: Task > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > Verify and fix if necessary that the following projects download dependencies using HTTPS: > https://github.com/jboss/jboss-transaction-api_spec > https://github.com/jbosstm/jboss-transaction-spi > https://github.com/jbosstm/narayana > https://github.com/jbosstm/quickstart -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3144) LRA TCK Test Failure

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3144?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3144: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done The TCK ran to completion against the PR so assuming the fix is good > LRA TCK Test Failure > -------------------- > > Key: JBTM-3144 > URL: https://issues.jboss.org/browse/JBTM-3144 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The TCK test TckTests.acceptCancelTest is failing consistently. The test needs to wait for a recovery pass but the upstream project (Microprofile LRA) where the test is defined was recently changed to use timeouts and I suspect the test is not waiting long enough for the recovery to occur. > TckTests.timeLimit has also been seen to fail (probably for the same reason) -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 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 May 2019