March 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3125) Some LRA&RTS tests uses wrong String.format parameters

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3125?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3125: ----------------------------------- Fix Version/s: 5.next > Some LRA&RTS tests uses wrong String.format parameters > ------------------------------------------------------ > > Key: JBTM-3125 > URL: https://issues.jboss.org/browse/JBTM-3125 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA, REST > Affects Versions: 5.9.3.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Optional > Fix For: 5.next > > > Some tests uses wrong {{String.format}}. For example wrong number of arguments for the {{format}} methdo > {code} > System.out.printf("SRA: %s: Updating hotel participant state to: ", bookingId, status); > {code} > should be > {code} > System.out.printf("SRA: %s: Updating hotel participant state to: %s", bookingId, status); > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3117) Upgrade to the latest LRA spec version

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3117?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3117: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.next Resolution: Done > Upgrade to the latest LRA spec version > -------------------------------------- > > Key: JBTM-3117 > URL: https://issues.jboss.org/browse/JBTM-3117 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.9.3.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > Fix For: 5.next > > > Upgrade to the latest LRA API and TCK snapshots: > ``` > <version.microprofile.lra.api>1.0-20190306.071209-294</version.microprofile.lra.api> > <version.microprofile.lra.tck>1.0-20190306.071211-294</version.microprofile.lra.tck> > ``` -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3103) LRA api-particpant quickstart needs aligning with the latest MP LRA spec changes

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3103?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3103: ----------------------------------- Component/s: LRA > LRA api-particpant quickstart needs aligning with the latest MP LRA spec changes > -------------------------------------------------------------------------------- > > Key: JBTM-3103 > URL: https://issues.jboss.org/browse/JBTM-3103 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > > This quickstart depends on LRAParticipantDeserializer to recreate participants during crash recovery but [MP LRA issue #61|https://github.com/eclipse/microprofile-lra/issues/61] has removed this class. The alternative registration mechanism is still outstanding [see the comments on issue #35|https://github.com/eclipse/microprofile-lra/issues/35] for a discussion of the new way of registering participants. > Until a PR is raised for this issue I would like to disable the quickstarts that utilise LRAParticipantDeserializer. > Note that this has only just become an issue since previouslythe Narayana implementation of LRA depended on a specific snapshot build in the eclipse repo (since the LRA spec is in flux), but snapshots are purged after a month so the old way of registering participants is no longer available. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3103) LRA api-particpant quickstart needs aligning with the latest MP LRA spec changes

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3103?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson reassigned JBTM-3103: -------------------------------------- Assignee: Michael Musgrove > LRA api-particpant quickstart needs aligning with the latest MP LRA spec changes > -------------------------------------------------------------------------------- > > Key: JBTM-3103 > URL: https://issues.jboss.org/browse/JBTM-3103 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > > This quickstart depends on LRAParticipantDeserializer to recreate participants during crash recovery but [MP LRA issue #61|https://github.com/eclipse/microprofile-lra/issues/61] has removed this class. The alternative registration mechanism is still outstanding [see the comments on issue #35|https://github.com/eclipse/microprofile-lra/issues/35] for a discussion of the new way of registering participants. > Until a PR is raised for this issue I would like to disable the quickstarts that utilise LRAParticipantDeserializer. > Note that this has only just become an issue since previouslythe Narayana implementation of LRA depended on a specific snapshot build in the eclipse repo (since the LRA spec is in flux), but snapshots are purged after a month so the old way of registering participants is no longer available. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2799) Javadoc Tomcat module

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2799?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson closed JBTM-2799. ---------------------------------- Fix Version/s: (was: 5.later) Resolution: Migrated to another ITS Other ITS is: https://github.com/web-servers/narayana-tomcat/issues > Javadoc Tomcat module > --------------------- > > Key: JBTM-2799 > URL: https://issues.jboss.org/browse/JBTM-2799 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Application Server Integration > Reporter: Gytis Trikleris > Assignee: Thomas Jenkinson > Priority: Minor > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3019) Testsuite: Docker controller leaves stray volumes and fills up disk space unnecessairly over time

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3019?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson closed JBTM-3019. ---------------------------------- Fix Version/s: (was: 5.next) Resolution: Migrated to another ITS Other ITS is: https://github.com/web-servers/narayana-tomcat/issues > Testsuite: Docker controller leaves stray volumes and fills up disk space unnecessairly over time > ------------------------------------------------------------------------------------------------- > > Key: JBTM-3019 > URL: https://issues.jboss.org/browse/JBTM-3019 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.8.1.Final > Environment: Docker enabled Jenkins slaves > Reporter: Michal Karm Babacek > Assignee: Michal Karm Babacek > Priority: Minor > > h3. Problem > The Docker controller that allocates databases as Docker containers cleans up containers and does not leave unnecessary images: > {code} > [root@karm-centos7-x86-64 ~]# docker images > REPOSITORY TAG IMAGE ID CREATED SIZE > docker.io/postgres 9.4 26bd9b04b948 6 days ago 232 MB > docker.io/postgres 10 0965cdc98045 6 days ago 234 MB > docker.io/postgres <none> ed5db6e669ff 7 weeks ago 263 MB > docker.io/postgres <none> 30121e967865 7 weeks ago 289 MB > [root@karm-centos7-x86-64 ~]# docker ps -a > CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES > [root@karm-centos7-x86-64 ~]# > {code} > Although it leaves stray container volumes for some reason: > {code} > [root@karm-centos7-x86-64 ~]# du -hs /var/lib/docker-latest/volumes > 15G /var/lib/docker-latest/volumes > [root@karm-centos7-x86-64 ~]# docker volume ls -qf dangling=true | wc -l > 409 > {code} > It unnecessarily clogs the slaves' disk space. The 15G of garbage has been created over dozens and dozens of builds with at least two containers each, but it shouldn't be happening anyway. > h3. Call to action > Review whether [removeContainerCmd|https://github.com/jbosstm/narayana/blob/master/tools/...] is supposed to be enough to not only remove the container but to also remove its volume. > h3. Workaround > {code} > docker volume prune > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2830) Consider possible compensations framework architecture improvements

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2830?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson reassigned JBTM-2830: -------------------------------------- Assignee: Ondrej Chaloupka > Consider possible compensations framework architecture improvements > ------------------------------------------------------------------- > > Key: JBTM-2830 > URL: https://issues.jboss.org/browse/JBTM-2830 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Ondrej Chaloupka > Priority: Major > > I've created a document with a list of possible compensations framework improvements. I'm attaching a link to the google doc for you to review and schedule work once appropriate. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2886) Automatize XTS ssl quickstart to be tested in CI on Windows

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2886?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson reassigned JBTM-2886: -------------------------------------- Assignee: Ondrej Chaloupka > Automatize XTS ssl quickstart to be tested in CI on Windows > ----------------------------------------------------------- > > Key: JBTM-2886 > URL: https://issues.jboss.org/browse/JBTM-2886 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Affects Versions: 4.2 > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > > There was created a shell script for JBTM-2882 which automatize testing of XTS over SSL. The steps were already written in `README.md` but that was not run automatically on CI. > The linux version with shell script was provided but we need windows version with `.bat`. This is a followup task to provide the bat script for the automatization on Windows. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3056) Remove the xts-test-servlet dependency in narayana-full

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3056?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson reassigned JBTM-3056: -------------------------------------- Assignee: Ondrej Chaloupka > Remove the xts-test-servlet dependency in narayana-full > ------------------------------------------------------- > > Key: JBTM-3056 > URL: https://issues.jboss.org/browse/JBTM-3056 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Reporter: Amos Feng > Assignee: Ondrej Chaloupka > Priority: Major > > this dependency is generated by the module XTS/WSAS/xts-test-servlet but does not produce any files. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3106) Firing an @Initialized(TransactionScoped.class) event

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3106?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-3106: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.next Resolution: Done > Firing an @Initialized(TransactionScoped.class) event > ----------------------------------------------------- > > Key: JBTM-3106 > URL: https://issues.jboss.org/browse/JBTM-3106 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Affects Versions: 5.9.2.Final > Reporter: Ondra Chaloupka > Assignee: Laird Nelson > Priority: Major > Fix For: 5.next > > > It would be beneficial to have the CDI-specific wrapper around Narayana's TransactionManagerImple that fires an @Initialized(TransactionScoped.class)-qualified event. > For the CDI, it's a good practice. The all built-in scopes have to provide this behaviour. > > The CDI specification says (in section 6.7): > {quote} > Portable extensions are encouraged to synchronously fire: > * an event with qualifier @Initialized(X.class) when a custom context is initialized, i.e. ready for use, > * an event with qualifier @BeforeDestroyed(X.class) when a custom context is about to be destroyed, i.e. before the actual destruction, > * an event with qualifier @Destroyed(X.class) when a custom context is destroyed, i.e. after the actual destruction, > where X is the scope type associated with the context. > A suitable event payload should be chosen. > {quote} > > The {{begin()}} method a Narayana-supplied but CDI-specific transaction manager wrapping Narayana's "ordinary" one should do: > {code} > @Inject > @Initialized(TransactionScoped.class) > private Event<Transaction> initializationBroadcaster; > @Inject @BeforeDestroyed(TransactionScoped.class) > private Event<Transaction> beforeDestructionBroadcaster; > @Inject @Destroyed(TransactionScoped.class) > private Event<TransactionManager> destructionBroadcaster; > // in its begin() method: > super.begin(); > initializationBroadcaster.fire(this.getTransaction()); > // in its commit() and rollback() methods and anywhere else I'm forgetting: > beforeDestructionBroadcaster.fire(this.getTransaction()); > super.commit(); // or rollback or whatever > destructionBroadcaster.fire(this); > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

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 2019