March 2020 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3273) Avoid implementing InvocationHandler in jtaLogger

by Sanne Grinovero (Jira)

Sanne Grinovero created JBTM-3273: ------------------------------------- Summary: Avoid implementing InvocationHandler in jtaLogger Key: JBTM-3273 URL: https://issues.redhat.com/browse/JBTM-3273 Project: JBoss Transaction Manager Issue Type: Enhancement Components: JTA Reporter: Sanne Grinovero Context: optimisations for Quarkus Class {{com.arjuna.ats.jta.logging.jtaLogger}} is implementing {{InvocationHandler}}, and this is causing some difficulties in optimising Narayana for GraalVM native images. One problem is that all classes which use the logger have access to the {{InvocationHandler}}, which makes the analysis phase of the compiler quite more complex; this gets confusing when there is a compilation failure as this gets occasionally reported as the root cause (even though it's just one of the paths leading to a non-real issue). A secondary problem is that this class is inizializing a rather expensive proxy; this is less important but it would be great for the sake of bootstrap optimisations to refactor the {{i18NLogger}} field to not be a proxy. See also https://github.com/quarkusio/quarkus/pull/5343 : with such invocation handlers being widely reachable, it's very hard to support its native compilation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3272) The test for reading old records should only run against filesystem stores

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3272?page=com.atlassian.jira.plugin... ] Issue was automatically transitioned when Michael Musgrove created pull request #1579 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > The test for reading old records should only run against filesystem stores > -------------------------------------------------------------------------- > > Key: JBTM-3272 > URL: https://issues.redhat.com/browse/JBTM-3272 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Affects Versions: 5.10.3.Final > Reporter: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The test (com.hp.mwtests.ts.arjuna.objectstore.TestJBTM3262) was added while fixing https://issues.redhat.com/browse/JBTM-3262 in order to verify that records written with the old string serialization code could be read by later revisions of that code. Since the same string serialization code is used for all store types we only need to test against a single store type (adding the same test for all store types would be overkill). > The test is coded to work with stores that inherit from ObjectStore (such as ShadowNoFileLockStore) but it fails with some store types such as the JDBCStore with the error: > bq. TestJBTM3249.test:86 com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore cannot be cast to com.arjuna.ats.arjuna.objectstore.ObjectStore -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3272) The test for reading old records should only run against filesystem stores

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3272?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3272: ----------------------------------- Description: The test (com.hp.mwtests.ts.arjuna.objectstore.TestJBTM3262) was added while fixing https://issues.redhat.com/browse/JBTM-3262 in order to verify that records written with the old string serialization code could be read by later revisions of that code. Since the same string serialization code is used for all store types we only need to test against a single store type (adding the same test for all store types would be overkill). The test is coded to work with stores that inherit from ObjectStore (such as ShadowNoFileLockStore) but it fails with some store types such as the JDBCStore with the error: bq. TestJBTM3249.test:86 com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore cannot be cast to com.arjuna.ats.arjuna.objectstore.ObjectStore was: The test (com.hp.mwtests.ts.arjuna.objectstore.TestJBTM3249) was added while fixing JBTM3249 to verify that records in the old format could still be read by the latest code. The test only needs to be verified against file based stores (since the same fails with the JDBCStore: bq. TestJBTM3249.test:86 com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore cannot be cast to com.arjuna.ats.arjuna.objectstore.ObjectStore > The test for reading old records should only run against filesystem stores > -------------------------------------------------------------------------- > > Key: JBTM-3272 > URL: https://issues.redhat.com/browse/JBTM-3272 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Affects Versions: 5.10.3.Final > Reporter: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The test (com.hp.mwtests.ts.arjuna.objectstore.TestJBTM3262) was added while fixing https://issues.redhat.com/browse/JBTM-3262 in order to verify that records written with the old string serialization code could be read by later revisions of that code. Since the same string serialization code is used for all store types we only need to test against a single store type (adding the same test for all store types would be overkill). > The test is coded to work with stores that inherit from ObjectStore (such as ShadowNoFileLockStore) but it fails with some store types such as the JDBCStore with the error: > bq. TestJBTM3249.test:86 com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore cannot be cast to com.arjuna.ats.arjuna.objectstore.ObjectStore -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3272) The test for reading old records should only run against filesystem stores

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3272?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3272: ----------------------------------- Description: The test (com.hp.mwtests.ts.arjuna.objectstore.TestJBTM3249) was added while fixing JBTM3249 to verify that records in the old format could still be read by the latest code. The test only needs to be verified against file based stores (since the same fails with the JDBCStore: bq. TestJBTM3249.test:86 com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore cannot be cast to com.arjuna.ats.arjuna.objectstore.ObjectStore was: The test (com.hp.mwtests.ts.arjuna.objectstore.TestJBTM3249) added while fixing JBTM3249 fails with the JDBCStore: bq. TestJBTM3249.test:86 com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore cannot be cast to com.arjuna.ats.arjuna.objectstore.ObjectStore > The test for reading old records should only run against filesystem stores > -------------------------------------------------------------------------- > > Key: JBTM-3272 > URL: https://issues.redhat.com/browse/JBTM-3272 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Affects Versions: 5.10.3.Final > Reporter: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The test (com.hp.mwtests.ts.arjuna.objectstore.TestJBTM3249) was added while fixing JBTM3249 to verify that records in the old format could still be read by the latest code. The test only needs to be verified against file based stores (since the same > fails with the JDBCStore: > bq. TestJBTM3249.test:86 com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore cannot be cast to com.arjuna.ats.arjuna.objectstore.ObjectStore -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3272) The test for reading old records should only run against filesystem stores

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3272?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3272: ----------------------------------- Summary: The test for reading old records should only run against filesystem stores (was: The test for reading old records does not work with all store types) > The test for reading old records should only run against filesystem stores > -------------------------------------------------------------------------- > > Key: JBTM-3272 > URL: https://issues.redhat.com/browse/JBTM-3272 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Affects Versions: 5.10.3.Final > Reporter: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The test (com.hp.mwtests.ts.arjuna.objectstore.TestJBTM3249) added while fixing JBTM3249 fails with the JDBCStore: > bq. TestJBTM3249.test:86 com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore cannot be cast to com.arjuna.ats.arjuna.objectstore.ObjectStore -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3272) The test for reading old records does not work with all store types

by Michael Musgrove (Jira)

Michael Musgrove created JBTM-3272: -------------------------------------- Summary: The test for reading old records does not work with all store types Key: JBTM-3272 URL: https://issues.redhat.com/browse/JBTM-3272 Project: JBoss Transaction Manager Issue Type: Bug Components: Transaction Core Affects Versions: 5.10.3.Final Reporter: Michael Musgrove Fix For: 5.next The test (com.hp.mwtests.ts.arjuna.objectstore.TestJBTM3249) added while fixing JBTM3249 fails with the JDBCStore: bq. TestJBTM3249.test:86 com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore cannot be cast to com.arjuna.ats.arjuna.objectstore.ObjectStore -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3233) Port the JTA recovery quickstart to run with the Quarkus Narayana JTA extension

by Mayank Kunwar (Jira)

[ https://issues.redhat.com/browse/JBTM-3233?page=com.atlassian.jira.plugin... ] Mayank Kunwar reassigned JBTM-3233: ----------------------------------- Assignee: Mayank Kunwar > Port the JTA recovery quickstart to run with the Quarkus Narayana JTA extension > ------------------------------------------------------------------------------- > > Key: JBTM-3233 > URL: https://issues.redhat.com/browse/JBTM-3233 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Quickstarts > Affects Versions: 5.10.1.Final > Reporter: Michael Musgrove > Assignee: Mayank Kunwar > Priority: Major > Fix For: 5.next > > > The [JTA recovery quickstart|https://github.com/jbosstm/quickstart/tree/master/ArjunaJTA/re...] with maven artefact id: org.jboss.narayana.quickstart.jta:recovery looks like it should run fine with the [Quarkus Narayana JTA extension|https://github.com/quarkusio/quarkus/tree/master/extensions/nar...]. > This task is to check what we need to do with the quickstart to run it with the extension. Maybe include it as one of the [Quarkus quickstart examples|https://github.com/quarkusio/quarkus-quickstarts]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3271) javadoc error when building with JDK11

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3271?page=com.atlassian.jira.plugin... ] Issue was automatically transitioned when Michael Musgrove created pull request #1576 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > javadoc error when building with JDK11 > -------------------------------------- > > Key: JBTM-3271 > URL: https://issues.redhat.com/browse/JBTM-3271 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.10.3.Final > Reporter: Michael Musgrove > Priority: Major > Fix For: 5.next > > > When we build using JDK11 we get javadoc errors. For example building ArjunaCore/arjunacore: > bq. javadoc: error - The code being documented uses modules but the packages defined in https://docs.oracle.com/javase/8/docs/api/ are in the unnamed module. > More context is here: https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8212233 > A fix is to configure the javadoc plugin (org.apache.maven.plugins:maven-javadoc-plugin) to use <source>8</source> in the plugin configuration section. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3271) javadoc error when building with JDK11

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3271?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3271: ----------------------------------- Description: When we build using JDK11 we get javadoc errors. For example building ArjunaCore/arjunacore: bq. javadoc: error - The code being documented uses modules but the packages defined in https://docs.oracle.com/javase/8/docs/api/ are in the unnamed module. More context is here: https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8212233 A fix is to configure the javadoc plugin (org.apache.maven.plugins:maven-javadoc-plugin) to use <source>8</source> in the plugin configuration section. was: When we build using JDK11 we get javadoc errors. For example building ArjunaCore/arjunacore: bq. javadoc: error - The code being documented uses modules but the packages defined in https://docs.oracle.com/javase/8/docs/api/ are in the unnamed module. A fix is to configure the javadoc plugin (org.apache.maven.plugins:maven-javadoc-plugin) to use <source>8</source> in the plugin configuration section. > javadoc error when building with JDK11 > -------------------------------------- > > Key: JBTM-3271 > URL: https://issues.redhat.com/browse/JBTM-3271 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.10.3.Final > Reporter: Michael Musgrove > Priority: Major > Fix For: 5.next > > > When we build using JDK11 we get javadoc errors. For example building ArjunaCore/arjunacore: > bq. javadoc: error - The code being documented uses modules but the packages defined in https://docs.oracle.com/javase/8/docs/api/ are in the unnamed module. > More context is here: https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8212233 > A fix is to configure the javadoc plugin (org.apache.maven.plugins:maven-javadoc-plugin) to use <source>8</source> in the plugin configuration section. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3271) javadoc error when building with JDK11

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3271?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3271: ----------------------------------- Description: When we build using JDK11 we get javadoc errors. For example building ArjunaCore/arjunacore: bq. javadoc: error - The code being documented uses modules but the packages defined in https://docs.oracle.com/javase/8/docs/api/ are in the unnamed module. A fix is to configure the javadoc plugin (org.apache.maven.plugins:maven-javadoc-plugin) to use <source>8</source> in the plugin configuration section. was: When we build ArjunaCore/arjunacore using JDK11 we get the following error: bq. javadoc: error - The code being documented uses modules but the packages defined in https://docs.oracle.com/javase/8/docs/api/ are in the unnamed module. A fix is to configure the javadoc plugin (org.apache.maven.plugins:maven-javadoc-plugin) to use <source>8</source> in the plugin configuration section. > javadoc error when building with JDK11 > -------------------------------------- > > Key: JBTM-3271 > URL: https://issues.redhat.com/browse/JBTM-3271 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.10.3.Final > Reporter: Michael Musgrove > Priority: Major > Fix For: 5.next > > > When we build using JDK11 we get javadoc errors. For example building ArjunaCore/arjunacore: > bq. javadoc: error - The code being documented uses modules but the packages defined in https://docs.oracle.com/javase/8/docs/api/ are in the unnamed module. > A fix is to configure the javadoc plugin (org.apache.maven.plugins:maven-javadoc-plugin) to use <source>8</source> in the plugin configuration section. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 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 March 2020