March 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-400) Compensation transactions for SOA Platform

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-400?page=com.atlassian.jira.plugin.s... ] Mark Little commented on JBTM-400: ---------------------------------- The idea is that compensation transactions are supported in a local (in JVM) manner and also via ESB "transports", such as JMS, FTP, file, JDBC etc. Since this issue was created (4 years ago), we've added REST-TX now and I don't recall seeing much push for this within SOA-P, JBossESB or Switchyard, I think we could close the issue with the assumption that we've now done enough to support the original intention. But it's definitely not a duplicate of 1472. > Compensation transactions for SOA Platform > ------------------------------------------ > > Key: JBTM-400 > URL: https://issues.jboss.org/browse/JBTM-400 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Transaction Core, XTS > Reporter: Mark Little > > Needs serious discussions within the team. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-396) Provide one-phase commit optimization for WS-TX

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-396?page=com.atlassian.jira.plugin.s... ] Mark Little reassigned JBTM-396: -------------------------------- Assignee: Paul Robinson > Provide one-phase commit optimization for WS-TX > ----------------------------------------------- > > Key: JBTM-396 > URL: https://issues.jboss.org/browse/JBTM-396 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: XTS > Affects Versions: 4.4.CR1 > Reporter: Mark Little > Assignee: Paul Robinson > > WS-AT does not support 1PC optimization. WS-ACID from WS-CAF does. It would be good to provide a configurable option for WS-AT users to enable 1PC optimization. This obviously breaks interoperability, which is why the default should be to have it disabled. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-609) TwoPhaseOutcome needs modifying

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-609?page=com.atlassian.jira.plugin.s... ] Mark Little resolved JBTM-609. ------------------------------ Resolution: Done I was originally thinking about making this an enum or something more dynamic. But I'm not convinced it's such a good idea any more, especially as this is a major part of our public API. > TwoPhaseOutcome needs modifying > ------------------------------- > > Key: JBTM-609 > URL: https://issues.jboss.org/browse/JBTM-609 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Transaction Core > Reporter: Mark Little > Assignee: Mark Little > > More outcomes possible since the early days of C++ Arjuna. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-609) TwoPhaseOutcome needs modifying

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-609?page=com.atlassian.jira.plugin.s... ] Mark Little closed JBTM-609. ---------------------------- > TwoPhaseOutcome needs modifying > ------------------------------- > > Key: JBTM-609 > URL: https://issues.jboss.org/browse/JBTM-609 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Transaction Core > Reporter: Mark Little > Assignee: Mark Little > > More outcomes possible since the early days of C++ Arjuna. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1407) Have a build option that builds JTS only against JacORB or IDLJ, but not both.

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1407?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-1407: ----------------------------------- Since I'm still receiving the following using the latest JDK 7 build for OSX ... [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.9:test (surefire-idlj) on project jts: Execution surefire-idlj of goal org.apache.maven.plugins:maven-surefire-plugin:2.9:test failed: java.lang.reflect.InvocationTargetException; nested exception is java.lang.reflect.InvocationTargetException: null: com/arjuna/ArjunaOTS/OTSAbstractRecordPOA: com.arjuna.ArjunaOTS.OTSAbstractRecordPOA -> [Help 1] I'm assuming we haven't made the automatic build the default? Building for both ORBs is something that has only just happened. So users currently really don't expect an IDLJ build. However, as a developer what I'd prefer is for the build system to not cr*p out ;-) if it can only find one ORB. If it can't find both and I asked it to build JTS then that's definitely an error. But if I just specify JTS on the build line I think I'm either meaning "Build JTS with JacORB" (given the last 7 years of history) or "Build JTS and I really don't care which ORB you use". Therefore, I suggest changing the build so that it only fails if it can't find either ORB. If it can't find both ORBs then at the end it should print out a message saying which one failed to build. Plus add a jacorb option to the build to correspond to the idlj option, so someone can specify "build jacorb only". This would mean the following: ./build.sh -P jts --> build with any ORB, I really don't care which ./build.sh -P jts idlj --> build with only the IDLJ ORB ./build.sh -P jts jacorb --> build with only JacORB > Have a build option that builds JTS only against JacORB or IDLJ, but not both. > ------------------------------------------------------------------------------ > > Key: JBTM-1407 > URL: https://issues.jboss.org/browse/JBTM-1407 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System, JTS > Affects Versions: 4.17.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.0.0.M3 > > Time Spent: 3 days, 1 hour, 50 minutes > Remaining Estimate: 1 hour > > This boils down to supporting two new profiles: > ./build.sh -P jts-jacorb > ./build.sh -P jts-idlj -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1442) Prepare a blog post to announce M2

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1442?page=com.atlassian.jira.plugin.... ] Work on JBTM-1442 started by Tom Jenkinson. > Prepare a blog post to announce M2 > ---------------------------------- > > Key: JBTM-1442 > URL: https://issues.jboss.org/browse/JBTM-1442 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation > Affects Versions: 5.0.0.M2 > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1479) Create a quickstart to show how to use IronJacamar and JBTM inside tomcat

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1479?page=com.atlassian.jira.plugin.... ] Work on JBTM-1479 started by Gytis Trikleris. > Create a quickstart to show how to use IronJacamar and JBTM inside tomcat > ------------------------------------------------------------------------- > > Key: JBTM-1479 > URL: https://issues.jboss.org/browse/JBTM-1479 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.Final > > Attachments: test-ds.xml, transaction.xml > > Original Estimate: 3 days > Time Spent: 6 hours > Remaining Estimate: 2 days, 2 hours > > See JBTM-809 for the algorithm > You might want to put the startup in the context listener: > public class MyServletContextListener implements ServletContextListener { > public void contextInitialized(ServletContextEvent sce) { > // Initialize RecoveryManager > // Initialize TransactionManager > // Initialize IronJacamar > } > > @Override > public void contextDestroyed(ServletContextEvent sce) { > // Clean IronJacamar > // Clean TransactionManager > // Clean RecoveryManager > } > } > Quickstart application should connect to the database (say PostgreSQL), dummy XA resource and coordinate the transaction. The PostgreSQL data source needs to be accessed via IronJacamar. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1513) ArjunaJTS/jtax/tests/classes/WedgedResourceDemonstrator.java test failed

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1513?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1513. --------------------------------- Resolution: Done > ArjunaJTS/jtax/tests/classes/WedgedResourceDemonstrator.java test failed > ------------------------------------------------------------------------ > > Key: JBTM-1513 > URL: https://issues.jboss.org/browse/JBTM-1513 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTS, Testing > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 4.17.4 > > > See: http://172.17.131.2/job/jbossts-EAP601/319 > {noformat} > BUILD FAILED > /home/hudson/workspace/jbossts-EAP601/build.xml:55: The following error occurred while executing this line: > /home/hudson/workspace/jbossts-EAP601/sharedbuild.xml:283: The following error occurred while executing this line: > /home/hudson/workspace/jbossts-EAP601/sharedbuild.xml:285: The following error occurred while executing this line: > /home/hudson/workspace/jbossts-EAP601/ArjunaJTS/jtax/build.xml:66: The following error occurred while executing this line: > /home/hudson/workspace/jbossts-EAP601/sharedbuild.xml:468: The following error occurred while executing this line: > /home/hudson/workspace/jbossts-EAP601/sharedbuild.xml:528: Test WedgedResourceDemonstrator failed > {noformat} -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1513) ArjunaJTS/jtax/tests/classes/WedgedResourceDemonstrator.java test failed

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-1513: ------------------------------------- Summary: ArjunaJTS/jtax/tests/classes/WedgedResourceDemonstrator.java test failed Key: JBTM-1513 URL: https://issues.jboss.org/browse/JBTM-1513 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS, Testing Reporter: Gytis Trikleris Assignee: Tom Jenkinson Priority: Minor Fix For: 4.17.4 See: http://172.17.131.2/job/jbossts-EAP601/319 {noformat} BUILD FAILED /home/hudson/workspace/jbossts-EAP601/build.xml:55: The following error occurred while executing this line: /home/hudson/workspace/jbossts-EAP601/sharedbuild.xml:283: The following error occurred while executing this line: /home/hudson/workspace/jbossts-EAP601/sharedbuild.xml:285: The following error occurred while executing this line: /home/hudson/workspace/jbossts-EAP601/ArjunaJTS/jtax/build.xml:66: The following error occurred while executing this line: /home/hudson/workspace/jbossts-EAP601/sharedbuild.xml:468: The following error occurred while executing this line: /home/hudson/workspace/jbossts-EAP601/sharedbuild.xml:528: Test WedgedResourceDemonstrator failed {noformat} -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1512) com.hp.mwtests.ts.jts.local.transactions.TransactionTest1 failed

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1512?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1512. --------------------------------- Resolution: Done > com.hp.mwtests.ts.jts.local.transactions.TransactionTest1 failed > ---------------------------------------------------------------- > > Key: JBTM-1512 > URL: https://issues.jboss.org/browse/JBTM-1512 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTS, Testing > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 4.17.4 > > > See: http://172.17.131.2/job/jbossts-EAP601/318 > {noformat} > /home/hudson/workspace/jbossts-EAP601/build.xml:55: The following error occurred while executing this line: > /home/hudson/workspace/jbossts-EAP601/sharedbuild.xml:283: The following error occurred while executing this line: > /home/hudson/workspace/jbossts-EAP601/sharedbuild.xml:285: The following error occurred while executing this line: > /home/hudson/workspace/jbossts-EAP601/ArjunaJTS/jts/build.xml:85: The following error occurred while executing this line: > /home/hudson/workspace/jbossts-EAP601/sharedbuild.xml:468: The following error occurred while executing this line: > /home/hudson/workspace/jbossts-EAP601/sharedbuild.xml:528: Test com.hp.mwtests.ts.jts.local.transactions.TransactionTest1 failed > {noformat} -- 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, 9 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