February 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1489) Create a blog post outlining integration with JBossWS

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1489?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1489: -------------------------------- Issue Type: Task (was: Feature Request) > Create a blog post outlining integration with JBossWS > ----------------------------------------------------- > > Key: JBTM-1489 > URL: https://issues.jboss.org/browse/JBTM-1489 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: TXFramework, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M2 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1481) Transaction::commit on an transaction that the reaper has tried to rollback but has a wedged resource will not raise an exception

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1481?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1481: -------------------------------- Fix Version/s: 4.16.7 4.17.4 5.0.0.M2 > Transaction::commit on an transaction that the reaper has tried to rollback but has a wedged resource will not raise an exception > --------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-1481 > URL: https://issues.jboss.org/browse/JBTM-1481 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.6.1.CP13 > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 4.6.1.CP14, 4.16.7, 4.17.4, 5.0.0.M2 > > Attachments: JBTM-1481.patch, WedgedResourceDemonstrator.java > > > If you are getting a wedged resource. What then happens is that we interrupt the original reaper thread that is calling XAResource::rollback on the wedged resource which because you are using JacORB and have an in progress call will generate a null pointer exception when the thread is interrupted (you can see this in my attached log file, it prints a stack trace where the logging didn't do so before) which generates a org.omg.CORBA.TRANSACTION_ROLLEDBACK exception. > The problem is that after the reaper tries to rollback the transaction but stalls on a wedged resource, it is then possible for the app thread to unwedged and to do a JTA::commit() and not get an exception. Debugging through the code, it doesn't pose data integrity issues on the transaction as what is happening is that internally we are checking the status of the transaction: > ./ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/coordinator/ArjunaTransactionImple.java:340 > And because the transaction is not RUNNING or ABORT_ONLY, we are: > ./ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/coordinator/ArjunaTransactionImple.java:398: > throw new INVALID_TRANSACTION(0, CompletionStatus.COMPLETED_NO) > Which is all good so far but then ends up in: > ./ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/TransactionImple.java:1425 > catch (INVALID_TRANSACTION e6) > { > /* > * In JTS/OTS we can indicate that something was terminated by another thread. > * JTA doesn't really prevent this, but ... > */ > > //throw new IllegalStateException( > // jtaLogger.loggerI18N.getString("com.arjuna.ats.internal.jta.transaction.jts.invalidtx2")); > } > Where it appears at some point we would have thrown an exception but decided to make the call that this was not valid anymore. > As I say, it doesn't pose data integrity implications to the specific transaction, but if your app thread unwedges and you then make a decision on the outcome of the transaction (send email, acknowledge success) then it would break the business rules of that application. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1357) Add coloured output to build.sh

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1357?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1357: -------------------------------- Issue Type: Task (was: Feature Request) > Add coloured output to build.sh > ------------------------------- > > Key: JBTM-1357 > URL: https://issues.jboss.org/browse/JBTM-1357 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Robinson > Priority: Minor > > The following script: https://github.com/builddoctor/maven-antsy-color will colour-code maven output. In particular failed tests come out in red and passes in green. I'm using it on my machine for regular maven builds and I find it makes it a lot easier to spot errors. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1367) Create a quickstart for the XTS plugin for the Arquillian Transaction Extension

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1367?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1367: -------------------------------- Issue Type: Task (was: Feature Request) > Create a quickstart for the XTS plugin for the Arquillian Transaction Extension > ------------------------------------------------------------------------------- > > Key: JBTM-1367 > URL: https://issues.jboss.org/browse/JBTM-1367 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1391) Prepare a blog post to introduce the TXFramework

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1391?focusedWorklogId=12428724&page=... ] Paul Robinson logged work on JBTM-1391: --------------------------------------- Author: Paul Robinson Created on: 26/Feb/13 9:54 AM Start Date: 26/Feb/13 9:54 AM Worklog Time Spent: 6 hours Issue Time Tracking ------------------- Remaining Estimate: 3 hours (was: 1 day, 4 hours) Time Spent: 1 day, 2 hours, 40 minutes (was: 4 hours, 40 minutes) Worklog Id: (was: 12428724) > Prepare a blog post to introduce the TXFramework > ------------------------------------------------ > > Key: JBTM-1391 > URL: https://issues.jboss.org/browse/JBTM-1391 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation, TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M2 > > Original Estimate: 2 days > Time Spent: 1 day, 2 hours, 40 minutes > Remaining Estimate: 3 hours > -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1489) Create a blog post outlining integration with JBossWS

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1489: ----------------------------------- Summary: Create a blog post outlining integration with JBossWS Key: JBTM-1489 URL: https://issues.jboss.org/browse/JBTM-1489 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: TXFramework, XTS Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M2 -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1299) Narayana artifacts are difficult to find after a build

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1299?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1299: -------------------------------- Issue Type: Task (was: Enhancement) > Narayana artifacts are difficult to find after a build > ------------------------------------------------------ > > Key: JBTM-1299 > URL: https://issues.jboss.org/browse/JBTM-1299 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 4.17.0 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.0.Final > > > The new build system leaves the installable jars in their respective module target directories. It is not obvious which jars are which so it would be nice if we can provide, near the top of the top level README, a brief description of the purpose and location of each target produced by the build. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1327) QA Test Suite Failures

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1327?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1327: -------------------------------- Issue Type: Bug (was: Feature Request) > QA Test Suite Failures > ---------------------- > > Key: JBTM-1327 > URL: https://issues.jboss.org/browse/JBTM-1327 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.0.Final > > > Parent JIRA for QA test failures -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1299) Narayana artifacts are difficult to find after a build

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1299?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1299: -------------------------------- Issue Type: Enhancement (was: Feature Request) > Narayana artifacts are difficult to find after a build > ------------------------------------------------------ > > Key: JBTM-1299 > URL: https://issues.jboss.org/browse/JBTM-1299 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 4.17.0 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.0.Final > > > The new build system leaves the installable jars in their respective module target directories. It is not obvious which jars are which so it would be nice if we can provide, near the top of the top level README, a brief description of the purpose and location of each target produced by the build. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1368) Allow multiple JDBC Object Store jobs using a table prefix of the job name

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1368?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1368: -------------------------------- Summary: Allow multiple JDBC Object Store jobs using a table prefix of the job name (was: Consider allowing multiple JDBC Object Store jobs using a table prefix of the job name) > Allow multiple JDBC Object Store jobs using a table prefix of the job name > -------------------------------------------------------------------------- > > Key: JBTM-1368 > URL: https://issues.jboss.org/browse/JBTM-1368 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Tom Jenkinson > Assignee: Ondřej Chaloupka > Fix For: 4.17.4, 5.0.0.Final > > -- 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

13 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues February 2013