February 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2622) Implement possible new compensations api from the meeting

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2622?page=com.atlassian.jira.plugin.... ] Gytis Trikleris reassigned JBTM-2622: ------------------------------------- Assignee: Gytis Trikleris > Implement possible new compensations api from the meeting > --------------------------------------------------------- > > Key: JBTM-2622 > URL: https://issues.jboss.org/browse/JBTM-2622 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > Attachments: 20160209_105648.jpg > > > Implement mock api from the meeting in order to be able to have a discussion about it on the forum. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2622) Implement possible new compensations api from the meeting

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2622?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2622: ---------------------------------- Attachment: 20160209_105648.jpg > Implement possible new compensations api from the meeting > --------------------------------------------------------- > > Key: JBTM-2622 > URL: https://issues.jboss.org/browse/JBTM-2622 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Compensations > Reporter: Gytis Trikleris > Fix For: 5.next > > Attachments: 20160209_105648.jpg > > > Implement mock api from the meeting in order to be able to have a discussion about it on the forum. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2622) Implement possible new compensations api from the meeting

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-2622: ------------------------------------- Summary: Implement possible new compensations api from the meeting Key: JBTM-2622 URL: https://issues.jboss.org/browse/JBTM-2622 Project: JBoss Transaction Manager Issue Type: Sub-task Components: Compensations Reporter: Gytis Trikleris Fix For: 5.next Implement mock api from the meeting in order to be able to have a discussion about it on the forum. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2180) Determine whether or not we should use a specific collections framework

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2180?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2180: -------------------------------- Fix Version/s: 6.later (was: 5.later) > Determine whether or not we should use a specific collections framework > ----------------------------------------------------------------------- > > Key: JBTM-2180 > URL: https://issues.jboss.org/browse/JBTM-2180 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTA, JTS, Performance Testing, REST, Transaction Core > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Tom Jenkinson > Priority: Optional > Fix For: 6.later > > > We use many of the inbuilt collections implementations (such as Hashtable) which are well known to be suboptimal in certain cases. Should we use a separate collections framework, e.g., https://github.com/goldmansachs/gs-collections > There are pros and cons of doing this. But first we need to determine whether it really makes sense from a performance perspective. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2583) Try to contact the transaction status connection manager to determine if a transaction containing XAResources is still in-flight before relying on orphan detection

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2583?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2583: -------------------------------- Fix Version/s: 6.later (was: 5.later) > Try to contact the transaction status connection manager to determine if a transaction containing XAResources is still in-flight before relying on orphan detection > ------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2583 > URL: https://issues.jboss.org/browse/JBTM-2583 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 6.later > > > Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. > This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. > > There are a couple of advantages to this: > 1. In the common case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > 2. In the case where the recovery manager and transaction manager are distributed, the current behaviour of orphan detection can be employed (or the timeout interval extended) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2598) Merge in BlackTie Javadocs to main Narayana javadocs

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2598?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2598: -------------------------------- Fix Version/s: 6.later (was: 5.next) > Merge in BlackTie Javadocs to main Narayana javadocs > ---------------------------------------------------- > > Key: JBTM-2598 > URL: https://issues.jboss.org/browse/JBTM-2598 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, Documentation > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 6.later > > > The BlackTie javadocs are still separate http://narayana.io/documentation/index.html - it would be useful to ensure that they are in the same place as the rest of the Narayana javadocs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2598) Merge in BlackTie Javadocs to main Narayana javadocs

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2598?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Tom Jenkinson created pull request #977 in GitHub ------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Merge in BlackTie Javadocs to main Narayana javadocs > ---------------------------------------------------- > > Key: JBTM-2598 > URL: https://issues.jboss.org/browse/JBTM-2598 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, Documentation > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > The BlackTie javadocs are still separate http://narayana.io/documentation/index.html - it would be useful to ensure that they are in the same place as the rest of the Narayana javadocs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2409) XARecoveryModuleHelpersUnitTest hang

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2409?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Tom Jenkinson created pull request #976 in GitHub ------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Reopened) > XARecoveryModuleHelpersUnitTest hang > ------------------------------------ > > Key: JBTM-2409 > URL: https://issues.jboss.org/browse/JBTM-2409 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > Attachments: 32287.jstack, hang.jstack > > > The test checks that recovery helpers can be removed at the correct stages during recovery scans. The CI job http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/196 shows the hang. > The junit test thread: > - starts 2 threads that will remove a recovery helper > - triggers xaRecoveryModule.periodicWorkFirstPass() > - triggers xaRecoveryModule.periodicWorkSecondPass() > - joins with remover threads > The jstack output shows: > - the two threads in the process of removing a recovery helper and are waiting for the first pass to finish; > - the junit test thread is waiting to join with these two threads; > Since both recovery passes must have completed it looks like the remover threads weren't notified when the first pass completed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2621) Tests that rely on the old perf benchmark harness need porting to use JMH

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2621: -------------------------------------- Summary: Tests that rely on the old perf benchmark harness need porting to use JMH Key: JBTM-2621 URL: https://issues.jboss.org/browse/JBTM-2621 Project: JBoss Transaction Manager Issue Type: Task Components: Performance Testing Affects Versions: 5.2.13.Final Reporter: Michael Musgrove Assignee: Michael Musgrove The relevant tests are: com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance1 com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance2 com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance3 if there are no others then once ported the old performance benchmark harness can be removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2605) Narayana Spring integration

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2605?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2605: ----------------------------------- Assignee: (was: Tom Jenkinson) > Narayana Spring integration > --------------------------- > > Key: JBTM-2605 > URL: https://issues.jboss.org/browse/JBTM-2605 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, Documentation, JTA > Reporter: Gytis Trikleris > Fix For: 5.next > > > This is a wrapper for all subtasks related with Spring integration. > As per Tom's request we should improve Narayana integration with Spring and Spring Boot. Also, provide documentation and quickstarts for it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 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 February 2016