November 2014 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2271) ConcurrentModificationException exception raised by CMR Recovery module first pass

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2271?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2271: ----------------------------------------------- tom.jenkinson(a)redhat.com changed the Status of [bug 1152782|https://bugzilla.redhat.com/show_bug.cgi?id=1152782] from ASSIGNED to POST > ConcurrentModificationException exception raised by CMR Recovery module first pass > ---------------------------------------------------------------------------------- > > Key: JBTM-2271 > URL: https://issues.jboss.org/browse/JBTM-2271 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.3 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2274) Create separate assumed complete type for heuristic transactions

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2274?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2274: ----------------------------------------------- tom.jenkinson(a)redhat.com changed the Status of [bug 1080140|https://bugzilla.redhat.com/show_bug.cgi?id=1080140] from ASSIGNED to POST > Create separate assumed complete type for heuristic transactions > ---------------------------------------------------------------- > > Key: JBTM-2274 > URL: https://issues.jboss.org/browse/JBTM-2274 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 4.17.24, 5.0.4 > > > Currently all JTS transaction records are moved to assumed complete store after 3 recovery tries. This is not good if the transaction has a heuristic outcome. It leads to the heuristic participant being rolled back, because recovery coordinator cannot see the log record after the move. > Creating separate locations for such heuristic transactions and checking their status during replay_completion would solve the problem. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2283) Tooling no longer exposes JTS record types

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2283?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2283: ----------------------------------------------- tom.jenkinson(a)redhat.com changed the Status of [bug 1151071|https://bugzilla.redhat.com/show_bug.cgi?id=1151071] from ASSIGNED to POST > Tooling no longer exposes JTS record types > ------------------------------------------ > > Key: JBTM-2283 > URL: https://issues.jboss.org/browse/JBTM-2283 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > Transacton records of type StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple are no longer exposed via the tooling. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2281) Merge the documentation manuals together

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2281?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2281: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/documentation/pull/28 > Merge the documentation manuals together > ---------------------------------------- > > Key: JBTM-2281 > URL: https://issues.jboss.org/browse/JBTM-2281 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > > The documentation for our project is available here: > Narayana Documentation 5.0.2.Final - JBoss Community > > As you can see it consists of several downloads including multiple books, links to various JavaDocs and some IDL files. Personally I think it might be easier to locate documentation entries if there is a single document to consult and a single JavaDoc link. I consulted our users whether anyone would object to us producing a single document and single JavaDoc set and received no objection. I am also thinking of no longer publishing the IDL as separate files as these are always tagged and available in our repo. > One way or another we need to make it clear in the docs what is in product and what is in project. Its not quite so important for our community users to know this but when translating docs into product manuals it is crucial. Currently this is done because everything under https://github.com/jbosstm/documentation/tree/master/docs is product related and things one level up are various community projects. An obvious way to merge the docs is merge everything under docs and then everything under ../* except docs - i.e. 2 manuals -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2281) Merge the documentation manuals together

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2281?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2281: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Merge the documentation manuals together > ---------------------------------------- > > Key: JBTM-2281 > URL: https://issues.jboss.org/browse/JBTM-2281 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > > The documentation for our project is available here: > Narayana Documentation 5.0.2.Final - JBoss Community > > As you can see it consists of several downloads including multiple books, links to various JavaDocs and some IDL files. Personally I think it might be easier to locate documentation entries if there is a single document to consult and a single JavaDoc link. I consulted our users whether anyone would object to us producing a single document and single JavaDoc set and received no objection. I am also thinking of no longer publishing the IDL as separate files as these are always tagged and available in our repo. > One way or another we need to make it clear in the docs what is in product and what is in project. Its not quite so important for our community users to know this but when translating docs into product manuals it is crucial. Currently this is done because everything under https://github.com/jbosstm/documentation/tree/master/docs is product related and things one level up are various community projects. An obvious way to merge the docs is merge everything under docs and then everything under ../* except docs - i.e. 2 manuals -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2292) Update Narayana release script

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2292?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2292: ---------------------------------- Description: Following changes are needed for Narayana release script: * Documentation was completely changed by JBTM-2281, thus links have to be changed * New API bundle was introduced with JBTM-2286. It should be used instead of separate JTA, JTS, XTS, RTS archives * Upload download links to the new web page via github * Replace extracted versions of documentations on the web page * Update narayana release process doc * Update webpage update readme was: Following changes are needed for Narayana release script: * Documentation was completely changed by JBTM-2281, thus links have to be changed * New API bundle was introduced with JBTM-2286. It should be used instead of separate JTA, JTS, XTS, RTS archives * Upload download links to the new web page via github * Replace extracted versions of documentations on the web page > Update Narayana release script > ------------------------------ > > Key: JBTM-2292 > URL: https://issues.jboss.org/browse/JBTM-2292 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.4 > > > Following changes are needed for Narayana release script: > * Documentation was completely changed by JBTM-2281, thus links have to be changed > * New API bundle was introduced with JBTM-2286. It should be used instead of separate JTA, JTS, XTS, RTS archives > * Upload download links to the new web page via github > * Replace extracted versions of documentations on the web page > * Update narayana release process doc > * Update webpage update readme -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2292) Update Narayana release script

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-2292: ------------------------------------- Summary: Update Narayana release script Key: JBTM-2292 URL: https://issues.jboss.org/browse/JBTM-2292 Project: JBoss Transaction Manager Issue Type: Task Components: Release Process Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.0.4 Following changes are needed for Narayana release script: * Documentation was completely changed by JBTM-2281, thus links have to be changed * New API bundle was introduced with JBTM-2286. It should be used instead of separate JTA, JTS, XTS, RTS archives * Upload download links to the new web page via github * Replace extracted versions of documentations on the web page -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2286) Create a zip with all javadocs included

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2286?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2286: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Create a zip with all javadocs included > --------------------------------------- > > Key: JBTM-2286 > URL: https://issues.jboss.org/browse/JBTM-2286 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.4 > > > Currently javadocs are split by component. It would be convenient to produce a single bundle of javadocs of all project as well for ease of publishing on the site. > What we are proposing is to produce a single Javadoc artifact for the Narayana project which has all the public API stuff (ignoring **/internal/**). Same as what you get with the JSE or JEE javadocs. A single link for users to see all public Narayana javadoc. > Each component will create its own JavaDocs as normal but a single uber zip would also be produced and this is what would be published on the site. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2279) Provide a way to allow overriding of a set CheckedActionFactory

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2279?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2279: -------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/jbosstm/narayana/pull/755, https://github.com/jbosstm/narayana/pull/770 (was: https://github.com/jbosstm/narayana/pull/755) I agree Mark. The way I had it was more like the ability to set a default and switch on whether it can be overridden. I think it is much clearer to just allow/suppress setting the single reference of a CAF via that property. I have sent a new PR so when that passes I will merge it in. > Provide a way to allow overriding of a set CheckedActionFactory > --------------------------------------------------------------- > > Key: JBTM-2279 > URL: https://issues.jboss.org/browse/JBTM-2279 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > > Out of the box the BasicAction caches the reference to the checkedactionfactory and so if a users classpath is not available to narayana there is no way for a user to provide a CAF to Narayana. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2279) Provide a way to allow overriding of a set CheckedActionFactory

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2279?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reopened JBTM-2279: --------------------------------- > Provide a way to allow overriding of a set CheckedActionFactory > --------------------------------------------------------------- > > Key: JBTM-2279 > URL: https://issues.jboss.org/browse/JBTM-2279 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > > Out of the box the BasicAction caches the reference to the checkedactionfactory and so if a users classpath is not available to narayana there is no way for a user to provide a CAF to Narayana. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues November 2014