March 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1364) Migrate "REST-AT to JTA" bridge into REST-TX component

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1364?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1364: ---------------------------------- Description: The task is to the work Gytis did on his internship and migrate it into the REST-TX project. Tasks: 1. Review the current solution looking for: 1.1 Major issues that prevent an initial release 1.2 Test coverage 2. Make any required changes 3. Merge into the REST-TX project 4. Migrate the quickstarts accross 5. Create a blog post 5.1 Consider what the end user will need to do to use this technology. We may want to wait until REST-AT and this Bridge are shipped with a Narayana build of AS7. Otherwise the steps to get this working could be rather lengthy. was: The task is to the work Gytis did on his internship and migrate it into the TXBridge project. Tasks: 1. Review the current solution looking for: 1.1 Major issues that prevent an initial release 1.2 Test coverage 2. Make any required changes 3. Merge into the TXBridge project 4. Migrate the quickstarts accross 5. Create a blog post 5.1 Consider what the end user will need to do to use this technology. We may want to wait until REST-AT and this Bridge are shipped with a Narayana build of AS7. Otherwise the steps to get this working could be rather lengthy. > Migrate "REST-AT to JTA" bridge into REST-TX component > ------------------------------------------------------ > > Key: JBTM-1364 > URL: https://issues.jboss.org/browse/JBTM-1364 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator, REST, TxBridge > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Labels: assign > Fix For: 5.0.0.M3 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > The task is to the work Gytis did on his internship and migrate it into the REST-TX project. > Tasks: > 1. Review the current solution looking for: > 1.1 Major issues that prevent an initial release > 1.2 Test coverage > 2. Make any required changes > 3. Merge into the REST-TX project > 4. Migrate the quickstarts accross > 5. Create a blog post > 5.1 Consider what the end user will need to do to use this technology. We may want to wait until REST-AT and this Bridge are shipped with a Narayana build of AS7. Otherwise the steps to get this working could be rather lengthy. -- 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-1454) Compare performance of REST-AT with JTS

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1454?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-1454: ---------------------------------------- We support both transaction transports in BlackTie so it would be nice to quantify any benefits. I will look into creating a Byteman script to subtract out the overhead imposed by the communications stack. > Compare performance of REST-AT with JTS > --------------------------------------- > > Key: JBTM-1454 > URL: https://issues.jboss.org/browse/JBTM-1454 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Performance Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Minor > Fix For: 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1530) Create a test to show the difference between JTS and JTA afterCompletion TransactionManager::getStatus responses

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1530?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1530: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Create a test to show the difference between JTS and JTA afterCompletion TransactionManager::getStatus responses > ---------------------------------------------------------------------------------------------------------------- > > Key: JBTM-1530 > URL: https://issues.jboss.org/browse/JBTM-1530 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.0.0.M3 > > Original Estimate: 1 day > Time Spent: 1 day > Remaining Estimate: 1 hour > -- 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-1554) Create a job for PR on 5_BRANCH and 4_BRANCH

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1554?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1554: -------------------------------- Assignee: Gytis Trikleris (was: Paul Robinson) > Create a job for PR on 5_BRANCH and 4_BRANCH > -------------------------------------------- > > Key: JBTM-1554 > URL: https://issues.jboss.org/browse/JBTM-1554 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M3 > > > This will allow us to test changes to our AS fork before merging. I suggest we run all the tests that AS run on lightning, followed by all the Narayana tests. > We should also come up with a plan for building PR on 4_BRANCH or 5_BRANCH and Narayana together. This is required for situations when we need to make commits to both code basis that are mutually dependent. -- 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-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.... ] Gytis Trikleris commented on JBTM-1479: --------------------------------------- This commit in IronJacamar is needed to make quickstart work https://source.jboss.org/changelog/IronJacamar?cs=114275 > 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.M3 > > Attachments: test-ds.xml, transaction.xml > > Original Estimate: 3 days > Time Spent: 4 days, 1 hour, 30 minutes > Remaining Estimate: 3 hours, 30 minutes > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1482) If a naughty afterCompletion sync throws an exception, log the exception call stack

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1482?page=com.atlassian.jira.plugin.... ] Work on JBTM-1482 stopped by Gytis Trikleris. > If a naughty afterCompletion sync throws an exception, log the exception call stack > ----------------------------------------------------------------------------------- > > Key: JBTM-1482 > URL: https://issues.jboss.org/browse/JBTM-1482 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Transaction Core > Reporter: Scott Marlow > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.0.0.M3 > > > Currently, when this happens with AS, I see: > {quote} > 2013-02-18 16:24:43,837|WARN |[com.arjuna.ats.jta]|(ThreadId: Transaction Reaper Worker 221)|ARJUNA016029: SynchronizationImple.afterCompletion - failed for org.jboss.as.jpa.transaction.TransactionUtil$SessionSynchronization@634ef5a7 with exception: java.lang.NullPointerException > {quote} > From a related email conversation: > {quote} > Here's our Logger code: > @Message(id = 16029, value = "SynchronizationImple.afterCompletion - failed for {0} with exception", format = MESSAGE_FORMAT) > @LogMessage(level = WARN) > public void warn_resources_arjunacore_SynchronizationImple(String arg0, @Cause() Throwable arg1); > Here is where we call our logger: > jtaLogger.i18NLogger.warn_resources_arjunacore_SynchronizationImple(_theSynch.toString(), e); > Maybe the message should have the {1} in it, i.e. it change it like so: > "SynchronizationImple.afterCompletion - failed for {0} with exception {1}" > {quote} -- 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-1365) Deploy REST-AT support as a JBossAS subsystem and module

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1365?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1365: ---------------------------------- Original Estimate: (was: 3 days) Remaining Estimate: (was: 3 days) > Deploy REST-AT support as a JBossAS subsystem and module > -------------------------------------------------------- > > Key: JBTM-1365 > URL: https://issues.jboss.org/browse/JBTM-1365 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: REST > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M3 > > > Currently a user of REST-AT needs to deploy the coordinator and also create a new module for the REST-AT client support. It would be a lot easier for developers if this was already deployed as part of AS7. > I think the way to do this is to create a sub-system for the coordinator (like what we do for the XTS coordinator) and a module for the REST-AT libraries (again, similar to XTS). > The subsystem would need to: > * Bootstrap the coordinator. Currently bootstrapping occurs when the coordinator war is deployed. As there will be no war, the subsystem needs to take care of this bootstrapping. > * Deploy the coordinator endpoint. > The module would need to contain the REST-AT coordinator code and the client libraries. > h3. Open Issues > Need to check with the AS team to see if we add a new Subsystem or make do with an existing one. We can't start this work until this is resolved. -- 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-1405) idlj issue when building on Raspberry Pi

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1405?page=com.atlassian.jira.plugin.... ] Michael Musgrove reassigned JBTM-1405: -------------------------------------- Assignee: Gytis Trikleris (was: Michael Musgrove) This task can be closed once JBTM-1407 is resolved. > idlj issue when building on Raspberry Pi > ---------------------------------------- > > Key: JBTM-1405 > URL: https://issues.jboss.org/browse/JBTM-1405 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTS > Affects Versions: 4.17.3 > Environment: Raspberry Pi with stock distribution installed and openjdk 6. > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.0.0.M3 > > > Early in the build we get ... > [INFO] Processing 3 grammar files to /home/pi/narayana/ArjunaJTS/idl/idlj/target/generated-sources/idl > [INFO] [ERROR] /home/pi/narayana/ArjunaJTS/idl/src/main/idl/omg/CosTransactions.idl (line 35): java.io.FileNotFoundException: orb.idl > #include <orb.idl> > ^ > [ERROR] /home/pi/narayana/ArjunaJTS/idl/src/main/idl/omg/CosTransactions.idl (line 35): java.io.FileNotFoundException: orb.idl > #include <orb.idl> > ^ > [INFO] [ERROR] /home/pi/narayana/ArjunaJTS/idl/src/main/idl/omg/CosTransactions.idl (line 35): java.io.FileNotFoundException: orb.idl > #include <orb.idl> > ^ > [ERROR] /home/pi/narayana/ArjunaJTS/idl/src/main/idl/omg/CosTransactions.idl (line 35): java.io.FileNotFoundException: orb.idl > #include <orb.idl> > ^ > [INFO] [ERROR] /home/pi/narayana/ArjunaJTS/idl/src/main/idl/omg/CosTransactions.idl (line 35): java.io.FileNotFoundException: orb.idl > #include <orb.idl> > ^ > [ERROR] /home/pi/narayana/ArjunaJTS/idl/src/main/idl/omg/CosTransactions.idl (line 35): java.io.FileNotFoundException: orb.idl > #include <orb.idl> > ^ > And eventually this results in ... > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 4:03:24.556s > [INFO] Finished at: Sat Dec 22 20:32:47 UTC 2012 > [INFO] Final Memory: 38M/105M > [INFO] ------------------------------------------------------------------------ > [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: org/omg/CosTransactions/ResourceOperations: org.omg.CosTransactions.ResourceOperations -> [Help 1] > It would also be good if there was a build-time switch to disable using idlj. Building with the idlj option at the start (as mentioned in the README) would imply that this is the way to go and that building just using jts therefore only uses jacorb, but it seems that the jts rule builds with both orbs. -- 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-1407) Have a build option that builds JTS only against JacORB or IDLJ, but not both.

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1407?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1407: -------------------------------- Priority: Minor (was: Major) > 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 > Priority: Minor > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1558) Provide an SPI for the AS

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1558?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1558: -------------------------------- Fix Version/s: 5.0.0.Final (was: 5.0.0.M3) > Provide an SPI for the AS > ------------------------- > > Key: JBTM-1558 > URL: https://issues.jboss.org/browse/JBTM-1558 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Application Server Integration > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.Final > > Attachments: as8.zip, ij-tx-spi.txt > > > We can use jboss-transaction-spi to get started -- 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