April 2016 - jbossts-issues - Jboss List Archives

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

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2606?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-2606: --------------------------------------- This feature was merged into the Spring Boot master: https://github.com/spring-projects/spring-boot/commit/a2adc5a1304f2eb2412... > 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: Gytis Trikleris > 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, 7 months

1
0
0 / 0

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

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2606?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2606: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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: Gytis Trikleris > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2642) Interoperability issues with ArjunaJTS CosTransactions idl

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-2642?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-2642: ----------------------------------- Our version was based on the initial draft of 1.2 and then the final version. However, we had some ifdefs in the original file (a template file) so we could support different versions due to compliance issues with ORBs. It's possible the ifdef locations produced a different ordering or that there were changes in the standards we didn't track. > Interoperability issues with ArjunaJTS CosTransactions idl > ---------------------------------------------------------- > > Key: JBTM-2642 > URL: https://issues.jboss.org/browse/JBTM-2642 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 6.later > > > The copy of CosTransactions.idl in our source tree does not match any of the OTS spec versions, in partciular the enum ordering of Status values is different so we get the wrong status when asking foreign application servers for the status of a transaction. > I checked versions 1.0 and 1.1 (http://www.omg.org/spec/OTS/) and versions 1.3 and 1.4 (http://www.omg.org/spec/TRANS/), I could not locate version 1.2. The idl used by other application servers seems to match versions 1.3 and 1.4: > {code} > enum Status { > StatusActive, > StatusMarkedRollback, > StatusPrepared, > StatusCommitted, > StatusRolledBack, > StatusUnknown, > StatusNoTransaction, > StatusPreparing, > StatusCommitting, > StatusRollingBack > }; > {code} > whereas we are using > {code} > enum Status { StatusActive, StatusMarkedRollback, StatusPrepared, > StatusCommitted, StatusRolledBack, StatusUnknown, > StatusPreparing, StatusCommitting, StatusRollingBack, > StatusNoTransaction }; > {code} > Notice that the enum position of StatusNoTransaction is different. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2629) Implement TransactionalDriver alternative for JMS

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2629?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2629: ---------------------------------- Fix Version/s: (was: 5.next) > Implement TransactionalDriver alternative for JMS > ------------------------------------------------- > > Key: JBTM-2629 > URL: https://issues.jboss.org/browse/JBTM-2629 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > > JMS integration is done. In order to make it easier to use it in standalone Narayana, we should implement a similar utility as TransactionalDriver in JDBC. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

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

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2606?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2606: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/spring-projects/spring-boot/pull/5552 > 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: Gytis Trikleris > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2651) "number-of-application-rollbacks" statistic counted multiple times during single rollback

by Tomas Hofman (JIRA)

Tomas Hofman created JBTM-2651: ---------------------------------- Summary: "number-of-application-rollbacks" statistic counted multiple times during single rollback Key: JBTM-2651 URL: https://issues.jboss.org/browse/JBTM-2651 Project: JBoss Transaction Manager Issue Type: Bug Components: Transaction Core Reporter: Tomas Hofman Assignee: Tomas Hofman Fix For: 5.next During transaction timeout, "number-of-application-rollbacks" stat is incremented twice. As a result, "number-of-application-rollbacks" can be higher then "number-of-aborted-transactions". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2642) Interoperability issues with ArjunaJTS CosTransactions idl

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2642?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2642: ----------------------------------- Forum Reference: https://developer.jboss.org/message/953835 > Interoperability issues with ArjunaJTS CosTransactions idl > ---------------------------------------------------------- > > Key: JBTM-2642 > URL: https://issues.jboss.org/browse/JBTM-2642 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 6.later > > > The copy of CosTransactions.idl in our source tree does not match any of the OTS spec versions, in partciular the enum ordering of Status values is different so we get the wrong status when asking foreign application servers for the status of a transaction. > I checked versions 1.0 and 1.1 (http://www.omg.org/spec/OTS/) and versions 1.3 and 1.4 (http://www.omg.org/spec/TRANS/), I could not locate version 1.2. The idl used by other application servers seems to match versions 1.3 and 1.4: > {code} > enum Status { > StatusActive, > StatusMarkedRollback, > StatusPrepared, > StatusCommitted, > StatusRolledBack, > StatusUnknown, > StatusNoTransaction, > StatusPreparing, > StatusCommitting, > StatusRollingBack > }; > {code} > whereas we are using > {code} > enum Status { StatusActive, StatusMarkedRollback, StatusPrepared, > StatusCommitted, StatusRolledBack, StatusUnknown, > StatusPreparing, StatusCommitting, StatusRollingBack, > StatusNoTransaction }; > {code} > Notice that the enum position of StatusNoTransaction is different. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1804) JTS remote tests not run and no code coverage

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1804?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1804: ---------------------------------- Fix Version/s: 5.next (was: 5.3.2.Final) > JTS remote tests not run and no code coverage > --------------------------------------------- > > Key: JBTM-1804 > URL: https://issues.jboss.org/browse/JBTM-1804 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTS, Testing > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > The tests in .remote. package for JTS are not run by default. We should consider adding a build option so that they are run (will require some mods to the tests since many of them are client/server based - see associated Readme.txt files); don't run them by default since they will add delay to a normal build. > It would then be beneficial to have them instrumented by emma to get code coverage. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-223) Check WL-to-JBossTS interoperability (via JTS).

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-223?page=com.atlassian.jira.plugin.s... ] Gytis Trikleris updated JBTM-223: --------------------------------- Fix Version/s: 5.next (was: 5.3.2.Final) > Check WL-to-JBossTS interoperability (via JTS). > ----------------------------------------------- > > Key: JBTM-223 > URL: https://issues.jboss.org/browse/JBTM-223 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Reporter: Mark Little > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Extensible header structure corba call > key value slot ids > slot for transaction context is not in the well known slot > tx context was not defined so we used the market leader at the time -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2553) Investigate the test with byteman do not work with the jacoco

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2553?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2553: ---------------------------------- Fix Version/s: 5.next (was: 5.3.2.Final) > Investigate the test with byteman do not work with the jacoco > ------------------------------------------------------------- > > Key: JBTM-2553 > URL: https://issues.jboss.org/browse/JBTM-2553 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Testing > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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