March 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1557) If the same resource manager (isSameRM) is enlisted twice, ignore the second call to enlist

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1557?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1557: -------------------------------- Forum Reference: https://community.jboss.org/message/799730#799730 > If the same resource manager (isSameRM) is enlisted twice, ignore the second call to enlist > ------------------------------------------------------------------------------------------- > > Key: JBTM-1557 > URL: https://issues.jboss.org/browse/JBTM-1557 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA, JTS > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.M3 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1552) CI jobs that build the AS, should not skip tests.

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1552?focusedWorklogId=12428918&page=... ] Paul Robinson logged work on JBTM-1552: --------------------------------------- Author: Paul Robinson Created on: 18/Mar/13 1:15 PM Start Date: 18/Mar/13 1:14 PM Worklog Time Spent: 5 minutes Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 30 minutes) Time Spent: 5 minutes Worklog Id: (was: 12428918) > CI jobs that build the AS, should not skip tests. > ------------------------------------------------- > > Key: JBTM-1552 > URL: https://issues.jboss.org/browse/JBTM-1552 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M3 > > Original Estimate: 30 minutes > Time Spent: 5 minutes > Remaining Estimate: 0 minutes > > Running these tests would have caught an issue at the PR stage, that ended up making it through to the release. > These tests only take about 10-15mins so it's not a massive overhead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1552) CI jobs that build the AS, should not skip tests.

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1552?page=com.atlassian.jira.plugin.... ] Paul Robinson resolved JBTM-1552. --------------------------------- Resolution: Done > CI jobs that build the AS, should not skip tests. > ------------------------------------------------- > > Key: JBTM-1552 > URL: https://issues.jboss.org/browse/JBTM-1552 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M3 > > Original Estimate: 30 minutes > Time Spent: 5 minutes > Remaining Estimate: 0 minutes > > Running these tests would have caught an issue at the PR stage, that ended up making it through to the release. > These tests only take about 10-15mins so it's not a massive overhead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1557) If the same resource manager (isSameRM) is enlisted twice, ignore the second call to enlist

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1557?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1557: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/238 > If the same resource manager (isSameRM) is enlisted twice, ignore the second call to enlist > ------------------------------------------------------------------------------------------- > > Key: JBTM-1557 > URL: https://issues.jboss.org/browse/JBTM-1557 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA, JTS > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.M3 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1472) Initial work on JTA for Compensations

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1472?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1472: -------------------------------- Description: We essentially provide a JTA-like implementation for using compensations. We would support distribution over Web services and REST via WS-BA and REST-JDI. This is similar in how we do distributed ACID transactions today; the application is developed against the JTA, but through configuration we enable distributed transactions over a particular transport (remoting, IIOP, WS). It would be good to have some subset of functionality that worked on a raw VM (i.e. no appserver). This would hopefully broaden the market. This first piece of work is to do some initial research and support an API with potentially a subset of features of the final API. Tasks: # Investigate existing WS-BA APIs ## Try code examples if possible # Produce an initial list of features that should be covered by the API # Create a simple implementation backed by WS-BA. was: We essentially provide a JTA-like implementation for using compensations. We would support distribution over Web services and REST via WS-BA and REST-JDI. This is similar in how we do distributed ACID transactions today; the application is developed against the JTA, but through configuration we enable distributed transactions over a particular transport (remoting, IIOP, WS). It would be good to have some subset of functionality that worked on a raw VM (i.e. no appserver). This would hopefully broaden the market. This first piece of work is to do some initial research and support an API with potentially a subset of features of the final API. Tasks: 1) Investigate existing WS-BA APIs 2) Produce an initial list of features that should be covered by the API 3) Create a simple implementation backed by WS-BA. > Initial work on JTA for Compensations > ------------------------------------- > > Key: JBTM-1472 > URL: https://issues.jboss.org/browse/JBTM-1472 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Transaction Core, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M3 > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > We essentially provide a JTA-like implementation for using compensations. We would support distribution over Web services and REST via WS-BA and REST-JDI. This is similar in how we do distributed ACID transactions today; the application is developed against the JTA, but through configuration we enable distributed transactions over a particular transport (remoting, IIOP, WS). > It would be good to have some subset of functionality that worked on a raw VM (i.e. no appserver). This would hopefully broaden the market. > This first piece of work is to do some initial research and support an API with potentially a subset of features of the final API. > Tasks: > # Investigate existing WS-BA APIs > ## Try code examples if possible > # Produce an initial list of features that should be covered by the API > # Create a simple implementation backed by WS-BA. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1557) If the same resource manager (isSameRM) is enlisted twice, ignore the second call to enlist

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1557: ----------------------------------- Summary: If the same resource manager (isSameRM) is enlisted twice, ignore the second call to enlist Key: JBTM-1557 URL: https://issues.jboss.org/browse/JBTM-1557 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA, JTS Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.0.0.M3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1556) provide way for Synchronization.afterCompletion callee to know if the Reaper thread is calling

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/JBTM-1556?page=com.atlassian.jira.plugin.... ] Scott Marlow updated JBTM-1556: ------------------------------- Affects Version/s: 4.17.3 > provide way for Synchronization.afterCompletion callee to know if the Reaper thread is calling > ---------------------------------------------------------------------------------------------- > > Key: JBTM-1556 > URL: https://issues.jboss.org/browse/JBTM-1556 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 4.17.3 > Reporter: Scott Marlow > Assignee: Tom Jenkinson > > When the Synchronization.afterCompletion is invoked for EE JPA containers, knowledge of whether the current thread is the Reaper thread (cancelling the transaction from a background thread). > The fix to this jira will help with handling the [JPA 2.1 container concurrency requirements|http://java.net/projects/jpa-spec/lists/jsr338-experts/archi...]. > Please implement the solution makes the most sense to you, as this will introduce an additional dependency between other systems and JBossTM/JBossTS that depend on the solution, that will likely be around for a long time. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1556) provide way for Synchronization.afterCompletion callee to know if the Reaper thread is calling

by Scott Marlow (JIRA)

Scott Marlow created JBTM-1556: ---------------------------------- Summary: provide way for Synchronization.afterCompletion callee to know if the Reaper thread is calling Key: JBTM-1556 URL: https://issues.jboss.org/browse/JBTM-1556 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Reporter: Scott Marlow Assignee: Tom Jenkinson When the Synchronization.afterCompletion is invoked for EE JPA containers, knowledge of whether the current thread is the Reaper thread (cancelling the transaction from a background thread). The fix to this jira will help with handling the [JPA 2.1 container concurrency requirements|http://java.net/projects/jpa-spec/lists/jsr338-experts/archi...]. Please implement the solution makes the most sense to you, as this will introduce an additional dependency between other systems and JBossTM/JBossTS that depend on the solution, that will likely be around for a long time. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1533) Create a pre-release script

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1533?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1533: -------------------------------- Fix Version/s: (was: 4.17.4) > Create a pre-release script > --------------------------- > > Key: JBTM-1533 > URL: https://issues.jboss.org/browse/JBTM-1533 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M3 > > > To encompass these steps of the Narayana release process: > {code} > BRANCH=<4.17|master> > CURRENT=<Version number of the release (e.g. 5.0.0.M2)> > NEXT=<Version number of the next release (e.g. 5.0.0.M3)> > > > for REPO in documentation quickstart narayana > do > > git clone git@github.com:jbosstm/$REPO.git > cd $REPO > git checkout $BRANCH > > find . -name \*.java -o -name \*.xml -o -name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | grep -v .idea | xargs sed -i "s/$CURRENT-SNAPSHOT/$CURRENT/g" > git commit -am "Updated to $CURRENT" > git tag $CURRENT > > find . -name \*.java -o -name \*.xml -o -name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | grep -v .idea | xargs sed -i "s/$CURRENT/$NEXT-SNAPSHOT/g" > git commit -am "Updated to $NEXT-SNAPSHOT" > git push origin $BRANCH --tags > cd .. > > done > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1532) TestBASubordinateCrashDuringCommit: jboss-as was not killed by Byteman

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1532?page=com.atlassian.jira.plugin.... ] Paul Robinson resolved JBTM-1532. --------------------------------- Resolution: Deferred Deferring this issue. It happened when we had a mismatched Arquillian AS container (7.1.3 on client, 8.0.0.A1 on server). If we see it again with AS8 on client and server, then re-open. > TestBASubordinateCrashDuringCommit: jboss-as was not killed by Byteman > ---------------------------------------------------------------------- > > Key: JBTM-1532 > URL: https://issues.jboss.org/browse/JBTM-1532 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M3 > > > http://172.17.131.2/job/narayana/194/console -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 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 March 2013