April 2020 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3278) Require that LRA method must be combined with Compensate or AfterLRA (LRA issue 272)

by Martin Stefanko (Jira)

Martin Stefanko created JBTM-3278: ------------------------------------- Summary: Require that LRA method must be combined with Compensate or AfterLRA (LRA issue 272) Key: JBTM-3278 URL: https://issues.redhat.com/browse/JBTM-3278 Project: JBoss Transaction Manager Issue Type: Bug Components: LRA Affects Versions: 5.10.3.Final Reporter: Martin Stefanko Assignee: Martin Stefanko LRA issue 272 - https://github.com/eclipse/microprofile-lra/issues/272 We must require (fail the deployment otherwise) that LRA method must be combined with either Compensate method or AfterLRA method in the same LRA resource. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3277) LRA quickstarts fail on Narayana AMS CI with curl could not find the target server

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3277?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3277: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/quickstart/pull/274 > LRA quickstarts fail on Narayana AMS CI with curl could not find the target server > ---------------------------------------------------------------------------------- > > Key: JBTM-3277 > URL: https://issues.redhat.com/browse/JBTM-3277 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Quickstarts > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Minor > > The quickstarts fails on CI as it seems the CI is now dual stack and for normal run we need to enforce the IPv4 to be used. > The when {{localhost}} is used then {{curl}} is directed to {{::1}} while java Thorntail is started at {{0.0.0.0}}. > The workaround the setup the curl should force the IPv4 to be used {{-4}}. > The CI error is observed with errors > {code} > ===== injecting a fault which should halt the service on pid > ... > WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:8080 > ... > Failed to connect to ::1: Network is unreachable > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3277) LRA quickstarts fail on Narayana AMS CI with curl could not find the target server

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3277?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3277: ----------------------------------- Description: The quickstarts fails on CI as it seems the CI is now dual stack and for normal run we need to enforce the IPv4 to be used. The when {{localhost}} is used then {{curl}} is directed to {{::1}} while java Thorntail is started at {{0.0.0.0}}. The workaround the setup the curl should force the IPv4 to be used {{-4}}. The CI error is observed with errors {code} ===== injecting a fault which should halt the service on pid ... WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:8080 ... Failed to connect to ::1: Network is unreachable {code} was: The quickstarts fails on CI as it seems the CI is now dual stack and for normal run we need to enforce the IPv4 to be used. The when {{localhost}} is used then {{curl}} is directed to {{::1}} while java Thorntail is started at {{0.0.0.0}}. The workaround the setup the curl should force the IPv4 to be used {{-4}}. The CI error is observed with errors {code} WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:8080 ... Failed to connect to ::1: Network is unreachable {code} > LRA quickstarts fail on Narayana AMS CI with curl could not find the target server > ---------------------------------------------------------------------------------- > > Key: JBTM-3277 > URL: https://issues.redhat.com/browse/JBTM-3277 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Quickstarts > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Minor > > The quickstarts fails on CI as it seems the CI is now dual stack and for normal run we need to enforce the IPv4 to be used. > The when {{localhost}} is used then {{curl}} is directed to {{::1}} while java Thorntail is started at {{0.0.0.0}}. > The workaround the setup the curl should force the IPv4 to be used {{-4}}. > The CI error is observed with errors > {code} > ===== injecting a fault which should halt the service on pid > ... > WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:8080 > ... > Failed to connect to ::1: Network is unreachable > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3277) LRA quickstarts fail on Narayana AMS CI with curl could not find the target server

by Ondrej Chaloupka (Jira)

Ondrej Chaloupka created JBTM-3277: -------------------------------------- Summary: LRA quickstarts fail on Narayana AMS CI with curl could not find the target server Key: JBTM-3277 URL: https://issues.redhat.com/browse/JBTM-3277 Project: JBoss Transaction Manager Issue Type: Bug Components: Quickstarts Reporter: Ondrej Chaloupka Assignee: Ondrej Chaloupka The quickstarts fails on CI as it seems the CI is now dual stack and for normal run we need to enforce the IPv4 to be used. The when {{localhost}} is used then {{curl}} is directed to {{::1}} while java Thorntail is started at {{0.0.0.0}}. The workaround the setup the curl should force the IPv4 to be used {{-4}}. The CI error is observed with errors {code} WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:8080 ... Failed to connect to ::1: Network is unreachable {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3276) add SlotStore ObjectStore implementation

by Anonymous (Jira)

[ https://issues.redhat.com/browse/JBTM-3276?page=com.atlassian.jira.plugin... ] Issue was automatically transitioned when jhalliday created pull request #1585 in GitHub ---------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > add SlotStore ObjectStore implementation > ---------------------------------------- > > Key: JBTM-3276 > URL: https://issues.redhat.com/browse/JBTM-3276 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Affects Versions: 5.10.3.Final > Reporter: Jonathan Halliday > Assignee: Jonathan Halliday > Priority: Minor > > The SlotStore provides an alternative ObjectStore implementation that dispenses with the file create/open/close/delete overhead of the FileStore, whilst also eschewing the write batching of the JournalStore. This combination is particularly tailored to new persistent memory hardware, for which the file write sync operation can be done in userspace with low overhead and a high degree of parallelism. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

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

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3273?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka reassigned JBTM-3273: -------------------------------------- Assignee: Ondrej Chaloupka > 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 > Assignee: Ondrej Chaloupka > Priority: Major > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3276) add SlotStore ObjectStore implementation

by Jonathan Halliday (Jira)

Jonathan Halliday created JBTM-3276: --------------------------------------- Summary: add SlotStore ObjectStore implementation Key: JBTM-3276 URL: https://issues.redhat.com/browse/JBTM-3276 Project: JBoss Transaction Manager Issue Type: Enhancement Components: Transaction Core Affects Versions: 5.10.3.Final Reporter: Jonathan Halliday Assignee: Jonathan Halliday The SlotStore provides an alternative ObjectStore implementation that dispenses with the file create/open/close/delete overhead of the FileStore, whilst also eschewing the write batching of the JournalStore. This combination is particularly tailored to new persistent memory hardware, for which the file write sync operation can be done in userspace with low overhead and a high degree of parallelism. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3261) Merge LRA branch to the master branch

by Martin Stefanko (Jira)

[ https://issues.redhat.com/browse/JBTM-3261?page=com.atlassian.jira.plugin... ] Martin Stefanko updated JBTM-3261: ---------------------------------- Summary: Merge LRA branch to the master branch (was: Ensure the LRA branch is up to date) > Merge LRA branch to the master branch > ------------------------------------- > > Key: JBTM-3261 > URL: https://issues.redhat.com/browse/JBTM-3261 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Reporter: Michael Musgrove > Assignee: Martin Stefanko > Priority: Major > > We have a git branch called [LRA|https://github.com/jbosstm/narayana/tree/LRA] which tracks the [microprofile-lra|https://github.com/eclipse/microprofile-lra] project. > This branch should periodically by synced up with the master branch. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3261) Ensure the LRA branch is up to date

by Martin Stefanko (Jira)

[ https://issues.redhat.com/browse/JBTM-3261?page=com.atlassian.jira.plugin... ] Martin Stefanko reassigned JBTM-3261: ------------------------------------- Assignee: Martin Stefanko (was: Michael Musgrove) > Ensure the LRA branch is up to date > ----------------------------------- > > Key: JBTM-3261 > URL: https://issues.redhat.com/browse/JBTM-3261 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Reporter: Michael Musgrove > Assignee: Martin Stefanko > Priority: Major > > We have a git branch called [LRA|https://github.com/jbosstm/narayana/tree/LRA] which tracks the [microprofile-lra|https://github.com/eclipse/microprofile-lra] project. > This branch should periodically by synced up with the master branch. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3158) jta-and-hibernate-standalone Narayana quickstart will not execute properly - EntityExistsException

by Mayank Kunwar (Jira)

[ https://issues.redhat.com/browse/JBTM-3158?page=com.atlassian.jira.plugin... ] Mayank Kunwar updated JBTM-3158: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > jta-and-hibernate-standalone Narayana quickstart will not execute properly - EntityExistsException > -------------------------------------------------------------------------------------------------- > > Key: JBTM-3158 > URL: https://issues.redhat.com/browse/JBTM-3158 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Miloslav Žežulka > Assignee: Mayank Kunwar > Priority: Minor > > One of the [Narayana quickstarts|https://github.com/jbosstm/quickstart] throws the following exception when executed according to the steps in README.md: > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:498) > at org.codehaus.mojo.exec.ExecJavaMojo$1.run (ExecJavaMojo.java:293) > at java.lang.Thread.run (Thread.java:748) > Caused by: javax.persistence.EntityExistsException: A different object with the same identifier value was already associated with the session : [org.jboss.narayana.quickstart.jta.QuickstartEntity#1] > at org.hibernate.jpa.spi.AbstractEntityManagerImpl.convert (AbstractEntityManagerImpl.java:1664) > at org.hibernate.jpa.spi.AbstractEntityManagerImpl.convert (AbstractEntityManagerImpl.java:1602) > at org.hibernate.jpa.spi.AbstractEntityManagerImpl.convert (AbstractEntityManagerImpl.java:1608) > at org.hibernate.jpa.spi.AbstractEntityManagerImpl.persist (AbstractEntityManagerImpl.java:1152) > at org.jboss.narayana.quickstart.jta.QuickstartEntityRepository.save (QuickstartEntityRepository.java:45) > at org.jboss.narayana.quickstart.jta.QuickstartEntityRepository$Proxy$_$$_WeldSubclass.save$$super (Unknown Source) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:498) > at org.jboss.weld.interceptor.proxy.TerminalAroundInvokeInvocationContext.proceedInternal (TerminalAroundInvokeInvocationContext.java:49) > at org.jboss.weld.interceptor.proxy.AroundInvokeInvocationContext.proceed (AroundInvokeInvocationContext.java:77) > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.invokeInCallerTx (TransactionalInterceptorBase.java:186) > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequired.doIntercept (TransactionalInterceptorRequired.java:55) > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.intercept (TransactionalInterceptorBase.java:88) > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequired.intercept (TransactionalInterceptorRequired.java:47) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:498) > at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke (SimpleInterceptorInvocation.java:74) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeAroundInvoke (InterceptorMethodHandler.java:84) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception (InterceptorMethodHandler.java:72) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke (InterceptorMethodHandler.java:56) > at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke (CombinedInterceptorAndDecoratorStackMethodHandler.java:79) > at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke (CombinedInterceptorAndDecoratorStackMethodHandler.java:68) > at org.jboss.narayana.quickstart.jta.QuickstartEntityRepository$Proxy$_$$_WeldSubclass.save (Unknown Source) > at org.jboss.narayana.quickstart.jta.QuickstartService.executeDemonstration (QuickstartService.java:106) > at org.jboss.narayana.quickstart.jta.QuickstartService.demonstrateCommit (QuickstartService.java:55) > at org.jboss.narayana.quickstart.jta.QuickstartApplication.main (QuickstartApplication.java:78) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:498) > at org.codehaus.mojo.exec.ExecJavaMojo$1.run (ExecJavaMojo.java:293) > at java.lang.Thread.run (Thread.java:748) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 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 April 2020