November 2017 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2966) narayana-quickstarts-jts quickstart does not run standalone

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2966: -------------------------------------- Summary: narayana-quickstarts-jts quickstart does not run standalone Key: JBTM-2966 URL: https://issues.jboss.org/browse/JBTM-2966 Project: JBoss Transaction Manager Issue Type: Bug Components: Demonstrator Affects Versions: 5.7.1.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The recovery quickstart does not run due to missing maven jboss-transaction-spi dependency. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2965) Unused source directory in the quickstart repository

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2965: -------------------------------------- Summary: Unused source directory in the quickstart repository Key: JBTM-2965 URL: https://issues.jboss.org/browse/JBTM-2965 Project: JBoss Transaction Manager Issue Type: Task Components: Demonstrator Affects Versions: 5.7.1.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Priority: Minor Fix For: 5.next There is an artifact in our quickstart repo that does not look like a quickstart and no other pom in the quickstart and performance repositories references the artifact: https://github.com/jbosstm/quickstart/tree/master/ArjunaJTS/jta It has never changed since the initial commit: {quote} commit caabc37803bac12e47f4986baca21f9052e14abc Author: Tom Jenkinson <tom.jenkinson(a)redhat.com> Date: Tue Oct 2 11:05:51 2012 +0100 Initial version of a performance comparitor for jts and jta {quote} This artefact needs deleting. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2964) Clarify the build instructions in the README

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2964: ----------------------------------- Summary: Clarify the build instructions in the README Key: JBTM-2964 URL: https://issues.jboss.org/browse/JBTM-2964 Project: JBoss Transaction Manager Issue Type: Task Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.next There are parts of the readme that are unclear about how to build individual modules or skipping tests. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBTM-1732) Durable STM instances require explicit sync to save state

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1732?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1732: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Durable STM instances require explicit sync to save state > --------------------------------------------------------- > > Key: JBTM-1732 > URL: https://issues.jboss.org/browse/JBTM-1732 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: STM > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Michael Musgrove > Priority: Optional > > As with TXOJ, a persistent STM object isn't written to disk until a write lock is acquired on it within the scope of a transaction. Consider automating this at creation time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2960) STM quickstart commits an aborted action

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2960?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2960: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > STM quickstart commits an aborted action > ---------------------------------------- > > Key: JBTM-2960 > URL: https://issues.jboss.org/browse/JBTM-2960 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: STM > Affects Versions: 5.7.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > PCCExample STM quickstart commits an abort action and there is a typo in the attempt to compare the STM object with its clone. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2963) Upgrade Artemis Journal to match version in WildFly

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2963?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Tom Jenkinson created pull request #1259 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Upgrade Artemis Journal to match version in WildFly > --------------------------------------------------- > > Key: JBTM-2963 > URL: https://issues.jboss.org/browse/JBTM-2963 > Project: JBoss Transaction Manager > Issue Type: Component Upgrade > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Sync up with the version in WFLY-9345 rather than latest 2 release. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2963) Upgrade Artemis Journal to match version in WildFly

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2963: ----------------------------------- Summary: Upgrade Artemis Journal to match version in WildFly Key: JBTM-2963 URL: https://issues.jboss.org/browse/JBTM-2963 Project: JBoss Transaction Manager Issue Type: Component Upgrade Components: Transaction Core Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.next Sync up with the version in WFLY-9345 rather than latest 2 release. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2962) Quickstart README indicates all quoickstarts need an app server

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-2962?page=com.atlassian.jira.plugin.... ] Mark Little reassigned JBTM-2962: --------------------------------- Assignee: Michael Musgrove > Quickstart README indicates all quoickstarts need an app server > --------------------------------------------------------------- > > Key: JBTM-2962 > URL: https://issues.jboss.org/browse/JBTM-2962 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Reporter: Mark Little > Assignee: Michael Musgrove > Priority: Minor > > The Narayana Quickstart top-level README tells people to set JBOSS_HOME to run quickstarts but not all of them need an app server, let alone a Java EE app server. I'm thinking specifically about Vert.x and perhaps any Swarm examples. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2962) Quickstart README indicates all quoickstarts need an app server

by Mark Little (JIRA)

Mark Little created JBTM-2962: --------------------------------- Summary: Quickstart README indicates all quoickstarts need an app server Key: JBTM-2962 URL: https://issues.jboss.org/browse/JBTM-2962 Project: JBoss Transaction Manager Issue Type: Bug Components: Demonstrator Reporter: Mark Little Priority: Minor The Narayana Quickstart top-level README tells people to set JBOSS_HOME to run quickstarts but not all of them need an app server, let alone a Java EE app server. I'm thinking specifically about Vert.x and perhaps any Swarm examples. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2949) Remove synchronization from ThreadUtil.getThreadId

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-2949?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-2949: ----------------------------------- Don't forget about public API changes, if any. > Remove synchronization from ThreadUtil.getThreadId > -------------------------------------------------- > > Key: JBTM-2949 > URL: https://issues.jboss.org/browse/JBTM-2949 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Luis Barreiro > Attachments: specj_349Q.png > > > JBTM-2808 adds synchronization on {{ThreadUtil.getThreadId()}} but that solution does not scale well enough under high contention. > There seems to be ways to remove this synchronization: > # *ConcurrentWeakHashMap* - replace the current {{WeakHashMap}} for a similar data structure that can handle concurrent access. This keeps the same behavior. > # *Use Thread.getId()* - remove all mappings and generate the {{threadId}} from the {{Thread}}. Although the javadoc mentions that IDs can be reused, the implementation is a counter, like what {{ThreadUtil}} has now. This is the simplest and most elegant fix. > # *Remove {{threadId}}* - remove the generation of {{threadId}} and use the {{Thread}} throughout the code, generating string IDs when necessary. Probably yields the best performance, but requires the most changes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues November 2017