January 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2580) Create a Narayana troubleshooting guide

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2580?page=com.atlassian.jira.plugin.... ] Work on JBTM-2580 started by Tom Jenkinson. ------------------------------------------- > Create a Narayana troubleshooting guide > --------------------------------------- > > Key: JBTM-2580 > URL: https://issues.jboss.org/browse/JBTM-2580 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > This information may already exist but is possibly fragmented. This issue is to record the fact that we need to collate this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 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.... ] Work on JBTM-2605 started by 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 > Assignee: Tom Jenkinson > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2606) Create Spring Boot starter for Narayana

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2606?page=com.atlassian.jira.plugin.... ] Work on JBTM-2606 started by Tom Jenkinson. ------------------------------------------- > Create Spring Boot starter for Narayana > --------------------------------------- > > Key: JBTM-2606 > URL: https://issues.jboss.org/browse/JBTM-2606 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Fix For: 5.next > > > Spring provides a bunch of Spring Boot starter artefacts in order to make integration of certain projects easier. We should investigate having one for Narayana. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2614) JCA TransactionImporter should be thread safe

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2614?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2614: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > JCA TransactionImporter should be thread safe > --------------------------------------------- > > Key: JBTM-2614 > URL: https://issues.jboss.org/browse/JBTM-2614 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JCA > Affects Versions: 5.2.12.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > I have a unit test that shows there's a race condition (first observed by [~dmlloyd]) in com.arjuna.ats.internal.jta.transaction.arjunacore.jca.TransactionImporterImple#importTransaction(javax.transaction.xa.Xid, int). > If two threads call this method at the same time, two separate transaction objects may be created. Here's the sequence of events: > T1: call importTransaction for XID1 > T2: call importTransaction for XID1 > T1: getImportedTransaction returns null > T2: getImportedTransaction returns null > T1: create new transaction, add to map > T2: create new transaction, add to map (overwriting T1's) > There is nothing in the documentation to indicate that this is not a valid situation or that access to the TransactionImporter has to be single-threaded in any way. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2614) JCA TransactionImporter should be thread safe

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2614?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-2614: ---------------------------------------- [~tomjenkinson] yes, I added two unit tests one for JTA the other for JTS > JCA TransactionImporter should be thread safe > --------------------------------------------- > > Key: JBTM-2614 > URL: https://issues.jboss.org/browse/JBTM-2614 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JCA > Affects Versions: 5.2.12.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > I have a unit test that shows there's a race condition (first observed by [~dmlloyd]) in com.arjuna.ats.internal.jta.transaction.arjunacore.jca.TransactionImporterImple#importTransaction(javax.transaction.xa.Xid, int). > If two threads call this method at the same time, two separate transaction objects may be created. Here's the sequence of events: > T1: call importTransaction for XID1 > T2: call importTransaction for XID1 > T1: getImportedTransaction returns null > T2: getImportedTransaction returns null > T1: create new transaction, add to map > T2: create new transaction, add to map (overwriting T1's) > There is nothing in the documentation to indicate that this is not a valid situation or that access to the TransactionImporter has to be single-threaded in any way. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2614) JCA TransactionImporter should be thread safe

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2614?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2614: ----------------------------------- Status: Pull Request Sent (was: Open) > JCA TransactionImporter should be thread safe > --------------------------------------------- > > Key: JBTM-2614 > URL: https://issues.jboss.org/browse/JBTM-2614 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JCA > Affects Versions: 5.2.12.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > I have a unit test that shows there's a race condition (first observed by [~dmlloyd]) in com.arjuna.ats.internal.jta.transaction.arjunacore.jca.TransactionImporterImple#importTransaction(javax.transaction.xa.Xid, int). > If two threads call this method at the same time, two separate transaction objects may be created. Here's the sequence of events: > T1: call importTransaction for XID1 > T2: call importTransaction for XID1 > T1: getImportedTransaction returns null > T2: getImportedTransaction returns null > T1: create new transaction, add to map > T2: create new transaction, add to map (overwriting T1's) > There is nothing in the documentation to indicate that this is not a valid situation or that access to the TransactionImporter has to be single-threaded in any way. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2612) Deploy jdbc module to the Maven repository

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2612?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2612: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Deploy jdbc module to the Maven repository > ------------------------------------------ > > Key: JBTM-2612 > URL: https://issues.jboss.org/browse/JBTM-2612 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Fix For: 5.next > > > Currently jdbc module is not available in Maven repository. Therefore, jta uber jar is needed to get access to those classes. If we want to discourage uber jar usage, we should provide jdbc module through Maven. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2612) Deploy jdbc module to the Maven repository

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2612?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Tom Jenkinson created pull request #972 in GitHub ------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Deploy jdbc module to the Maven repository > ------------------------------------------ > > Key: JBTM-2612 > URL: https://issues.jboss.org/browse/JBTM-2612 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Fix For: 5.next > > > Currently jdbc module is not available in Maven repository. Therefore, jta uber jar is needed to get access to those classes. If we want to discourage uber jar usage, we should provide jdbc module through Maven. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2615) Exclude org.omg.CORBA classes from narayana-jts-idlj uber jar

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2615?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2615: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Exclude org.omg.CORBA classes from narayana-jts-idlj uber jar > ------------------------------------------------------------- > > Key: JBTM-2615 > URL: https://issues.jboss.org/browse/JBTM-2615 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Affects Versions: 5.2.12.Final > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Looks to be due to a new dependency not excluded from the uber jar -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2615) Exclude org.omg.CORBA classes from narayana-jts-idlj uber jar

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2615?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Tom Jenkinson created pull request #971 in GitHub ------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Exclude org.omg.CORBA classes from narayana-jts-idlj uber jar > ------------------------------------------------------------- > > Key: JBTM-2615 > URL: https://issues.jboss.org/browse/JBTM-2615 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Affects Versions: 5.2.12.Final > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Looks to be due to a new dependency not excluded from the uber jar -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 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 January 2016