June 2020 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3307) LRACoordinatorRecovery2TestCase regularly fails on CI

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3307?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka reassigned JBTM-3307: -------------------------------------- Assignee: Ondrej Chaloupka (was: Michael Musgrove) > LRACoordinatorRecovery2TestCase regularly fails on CI > ----------------------------------------------------- > > Key: JBTM-3307 > URL: https://issues.redhat.com/browse/JBTM-3307 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.4.Final > Reporter: Michael Musgrove > Assignee: Ondrej Chaloupka > Priority: Blocker > > The test regularly fails CI > [ERROR] testRecovery2(io.narayana.lra.coordinator.LRACoordinatorRecovery2TestCase) Time elapsed: 30.455 s <<< FAILURE! > java.lang.AssertionError: LRA with short timeout should not be active > presumably due to a timing issue (since I cannot reproduce it on my laptop). I will see if there is a way to make the test more robust. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3333) Use Artemis object store in the ArjuraJTA/object_store quickstart.

by Miloslav Žežulka (Jira)

[ https://issues.redhat.com/browse/JBTM-3333?page=com.atlassian.jira.plugin... ] Miloslav Žežulka updated JBTM-3333: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/quickstart/pull/286 > Use Artemis object store in the ArjuraJTA/object_store quickstart. > ------------------------------------------------------------------ > > Key: JBTM-3333 > URL: https://issues.redhat.com/browse/JBTM-3333 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Miloslav Žežulka > Assignee: Miloslav Žežulka > Priority: Minor > > After resolving a bug in Narayana itself, we can now use the Artemis object store in the [quickstart showcasing object store usage|https://github.com/jbosstm/quickstart/tree/master/ArjunaJTA/object_...]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3333) Use Artemis object store in the ArjuraJTA/object_store quickstart.

by Miloslav Žežulka (Jira)

[ https://issues.redhat.com/browse/JBTM-3333?page=com.atlassian.jira.plugin... ] Miloslav Žežulka updated JBTM-3333: ----------------------------------- Description: After resolving a bug in Narayana itself, we can now use the Artemis object store in the [quickstart showcasing object store usage|https://github.com/jbosstm/quickstart/tree/master/ArjunaJTA/object_...]. (was: After resolving a bug in Narayana itself, we can now use the Artemis object store in the quickstart.) > Use Artemis object store in the ArjuraJTA/object_store quickstart. > ------------------------------------------------------------------ > > Key: JBTM-3333 > URL: https://issues.redhat.com/browse/JBTM-3333 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Miloslav Žežulka > Assignee: Miloslav Žežulka > Priority: Minor > > After resolving a bug in Narayana itself, we can now use the Artemis object store in the [quickstart showcasing object store usage|https://github.com/jbosstm/quickstart/tree/master/ArjunaJTA/object_...]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3333) Use Artemis object store in the ArjuraJTA/object_store quickstart.

by Miloslav Žežulka (Jira)

Miloslav Žežulka created JBTM-3333: -------------------------------------- Summary: Use Artemis object store in the ArjuraJTA/object_store quickstart. Key: JBTM-3333 URL: https://issues.redhat.com/browse/JBTM-3333 Project: JBoss Transaction Manager Issue Type: Enhancement Reporter: Miloslav Žežulka Assignee: Miloslav Žežulka After resolving a bug in Narayana itself, we can now use the Artemis object store in the quickstart. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3332) Add constructor to HornetqObjectStoreAdaptor to support named bean lookup.

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3332?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3332: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.next Resolution: Done > Add constructor to HornetqObjectStoreAdaptor to support named bean lookup. > -------------------------------------------------------------------------- > > Key: JBTM-3332 > URL: https://issues.redhat.com/browse/JBTM-3332 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Affects Versions: 5.10.5.Final > Reporter: Miloslav Žežulka > Assignee: Miloslav Žežulka > Priority: Minor > Fix For: 5.next > > > When retrieving reference to the Object Store, Narayana can do a named bean lookup; more specifically, the store manager [searches for the bean|https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/cl...] named _communicationStore._ > Part of the _initStore_ procedure referenced in the link is [class loading|https://github.com/jbosstm/narayana/blob/f370005e0959ad2c1e799d6e...]. As can be decucted from the code, when we try to classload a named bean, the implementation looks for a very specific constructor containing exactly one parameter and the type of such parameter must end with _EnvironmentBean_. > Problem arises (as already noted in the quickstart [ArjunaJTA/object_store|https://github.com/jbosstm/quickstart/blob/master/...]) when we wish to use HornetqObjectStoreAdaptor as our communication store as no such constructor currently exists. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3332) Add constructor to HornetqObjectStoreAdaptor to support named bean lookup.

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3332?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3332: ----------------------------------- Component/s: Transaction Core Git Pull Request: https://github.com/jbosstm/narayana/pull/1638 Affects Version/s: 5.10.5.Final > Add constructor to HornetqObjectStoreAdaptor to support named bean lookup. > -------------------------------------------------------------------------- > > Key: JBTM-3332 > URL: https://issues.redhat.com/browse/JBTM-3332 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Affects Versions: 5.10.5.Final > Reporter: Miloslav Žežulka > Assignee: Miloslav Žežulka > Priority: Minor > > When retrieving reference to the Object Store, Narayana can do a named bean lookup; more specifically, the store manager [searches for the bean|https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/cl...] named _communicationStore._ > Part of the _initStore_ procedure referenced in the link is [class loading|https://github.com/jbosstm/narayana/blob/f370005e0959ad2c1e799d6e...]. As can be decucted from the code, when we try to classload a named bean, the implementation looks for a very specific constructor containing exactly one parameter and the type of such parameter must end with _EnvironmentBean_. > Problem arises (as already noted in the quickstart [ArjunaJTA/object_store|https://github.com/jbosstm/quickstart/blob/master/...]) when we wish to use HornetqObjectStoreAdaptor as our communication store as no such constructor currently exists. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3332) Add constructor to HornetqObjectStoreAdaptor to support named bean lookup.

by Anonymous (Jira)

[ https://issues.redhat.com/browse/JBTM-3332?page=com.atlassian.jira.plugin... ] Issue was automatically transitioned when Miloslav Žežulka created pull request #1638 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Add constructor to HornetqObjectStoreAdaptor to support named bean lookup. > -------------------------------------------------------------------------- > > Key: JBTM-3332 > URL: https://issues.redhat.com/browse/JBTM-3332 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Miloslav Žežulka > Assignee: Miloslav Žežulka > Priority: Minor > > When retrieving reference to the Object Store, Narayana can do a named bean lookup; more specifically, the store manager [searches for the bean|https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/cl...] named _communicationStore._ > Part of the _initStore_ procedure referenced in the link is [class loading|https://github.com/jbosstm/narayana/blob/f370005e0959ad2c1e799d6e...]. As can be decucted from the code, when we try to classload a named bean, the implementation looks for a very specific constructor containing exactly one parameter and the type of such parameter must end with _EnvironmentBean_. > Problem arises (as already noted in the quickstart [ArjunaJTA/object_store|https://github.com/jbosstm/quickstart/blob/master/...]) when we wish to use HornetqObjectStoreAdaptor as our communication store as no such constructor currently exists. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3332) Add constructor to HornetqObjectStoreAdaptor to support named bean lookup.

by Miloslav Žežulka (Jira)

[ https://issues.redhat.com/browse/JBTM-3332?page=com.atlassian.jira.plugin... ] Miloslav Žežulka updated JBTM-3332: ----------------------------------- Description: When retrieving reference to the Object Store, Narayana can do a named bean lookup; more specifically, the store manager [searches for the bean|https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/cl...] named _communicationStore._ Part of the _initStore_ procedure referenced in the link is [class loading|https://github.com/jbosstm/narayana/blob/f370005e0959ad2c1e799d6e...]. As can be decucted from the code, when we try to classload a named bean, the implementation looks for a very specific constructor containing exactly one parameter and the type of such parameter must end with _EnvironmentBean_. Problem arises (as already noted in the quickstart [ArjunaJTA/object_store|https://github.com/jbosstm/quickstart/blob/master/...]) when we wish to use HornetqObjectStoreAdaptor as our communication store as no such constructor currently exists. was: When retrieving reference to the Object Store, Narayana can do a named bean lookup, more specifically the store manager searches for the bean named _communicationStore_ : [https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes...] Part of the _initStore_ procedure referenced in the link is [class loading|https://github.com/jbosstm/narayana/blob/f370005e0959ad2c1e799d6e...]. As can be decucted from the code, when we try to classload a named bean, the implementation looks for a very specific constructor containing exactly one parameter and the type of such parameter must end with _EnvironmentBean_. Problem arises (as already noted in the quickstart [ArjunaJTA/object_store|https://github.com/jbosstm/quickstart/blob/master/...]) when we wish to use HornetqObjectStoreAdaptor as our communication store as no such constructor currently exists. > Add constructor to HornetqObjectStoreAdaptor to support named bean lookup. > -------------------------------------------------------------------------- > > Key: JBTM-3332 > URL: https://issues.redhat.com/browse/JBTM-3332 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Miloslav Žežulka > Assignee: Miloslav Žežulka > Priority: Minor > > When retrieving reference to the Object Store, Narayana can do a named bean lookup; more specifically, the store manager [searches for the bean|https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/cl...] named _communicationStore._ > Part of the _initStore_ procedure referenced in the link is [class loading|https://github.com/jbosstm/narayana/blob/f370005e0959ad2c1e799d6e...]. As can be decucted from the code, when we try to classload a named bean, the implementation looks for a very specific constructor containing exactly one parameter and the type of such parameter must end with _EnvironmentBean_. > Problem arises (as already noted in the quickstart [ArjunaJTA/object_store|https://github.com/jbosstm/quickstart/blob/master/...]) when we wish to use HornetqObjectStoreAdaptor as our communication store as no such constructor currently exists. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3332) Add constructor to HornetqObjectStoreAdaptor to support named bean lookup.

by Miloslav Žežulka (Jira)

Miloslav Žežulka created JBTM-3332: -------------------------------------- Summary: Add constructor to HornetqObjectStoreAdaptor to support named bean lookup. Key: JBTM-3332 URL: https://issues.redhat.com/browse/JBTM-3332 Project: JBoss Transaction Manager Issue Type: Enhancement Reporter: Miloslav Žežulka Assignee: Miloslav Žežulka When retrieving reference to the Object Store, Narayana can do a named bean lookup, more specifically the store manager searches for the bean named _communicationStore_ : [https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes...] Part of the _initStore_ procedure referenced in the link is [class loading|https://github.com/jbosstm/narayana/blob/f370005e0959ad2c1e799d6e...]. As can be decucted from the code, when we try to classload a named bean, the implementation looks for a very specific constructor containing exactly one parameter and the type of such parameter must end with _EnvironmentBean_. Problem arises (as already noted in the quickstart [ArjunaJTA/object_store|https://github.com/jbosstm/quickstart/blob/master/...]) when we wish to use HornetqObjectStoreAdaptor as our communication store as no such constructor currently exists. -- 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: ----------------------------------- Fix Version/s: 5.next > 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 > Fix For: 5.next > > > 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues June 2020