February 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1488) Implement the REST-JDI spericification

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-1488: -------------------------------------- Summary: Implement the REST-JDI spericification Key: JBTM-1488 URL: https://issues.jboss.org/browse/JBTM-1488 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: REST Reporter: Michael Musgrove Assignee: Michael Musgrove Priority: Optional https://community.jboss.org/wiki/CompensatingRESTfulTransactions/ -- 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-1479) Create a quickstart to show how to use IronJacamar and JBTM inside tomcat

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1479?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1479: -------------------------------- Issue Type: Task (was: Feature Request) > 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) > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M2 > > 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

13 years, 1 month

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: -------------------------------- Issue Type: Task (was: Feature Request) > 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: 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

13 years, 1 month

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: -------------------------------- Component/s: Build System > 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1181) Add JBOSS Transactional File I/O User Guide TXFileInJava into documentation repo and use jdocbook

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1181?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1181: -------------------------------- Issue Type: Task (was: Feature Request) > Add JBOSS Transactional File I/O User Guide TXFileInJava into documentation repo and use jdocbook > ------------------------------------------------------------------------------------------------- > > Key: JBTM-1181 > URL: https://issues.jboss.org/browse/JBTM-1181 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation > Reporter: Amos Feng > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.0.0.Final > > Original Estimate: 1 day > Time Spent: 1 hour, 30 minutes > Remaining Estimate: 6 hours, 30 minutes > > there is https://svn.jboss.org/repos/labs/labs/jbosstm/workspace/transactionalFile... -- 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-1369) Benchmark performance difference between JacORB and JDK ORB

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1369?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1369: -------------------------------- Issue Type: Task (was: Feature Request) > Benchmark performance difference between JacORB and JDK ORB > ----------------------------------------------------------- > > Key: JBTM-1369 > URL: https://issues.jboss.org/browse/JBTM-1369 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTS, Performance Testing > Affects Versions: 4.17.0 > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Fix For: 5.0.0.M2 > > > JBTM-934 added support for the JDK orb to JTS. IOR sizes can range in size from 512 bytes to entirely unbounded, with the ORB being able to add arbitrary data within specific portions. Since the IOR is packed into transaction logs and if the IOR sizes are significantly different we may find that transaction throughput has been improved or degraded. We should run some benchmarks to see what the impact is. -- 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-1390) Update BaseCrashTest to use global arguments

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1390?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1390: -------------------------------- Issue Type: Task (was: Feature Request) > Update BaseCrashTest to use global arguments > -------------------------------------------- > > Key: JBTM-1390 > URL: https://issues.jboss.org/browse/JBTM-1390 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing, XTS > Reporter: Paul Robinson > > Ideally we should only have the byteman, memory and ipv6 args in a single place (root pom.xml). However, these are hardcoded in the BaseCrashTest of the XTS recovery tests. > These should be using the values set in the pom. > {code} > protected String BytemanArgs = "-Xms64m -Xmx1024m -XX:MaxPermSize=512m -Dorg.jboss.byteman.verbose -Djboss.modules.system.pkgs=org.jboss.byteman -Dorg.jboss.byteman.transform.all -javaagent:target/test-classes/lib/byteman.jar=script:target/test-classes/scripts/@BMScript@.txt,boot:target/test-classes/lib/byteman.jar,listener:true"; > protected String iPv6Args = "-Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true -Djboss.bind.address=[::1] -Djboss.bind.address.management=[::1] -Djboss.bind.address.unsecure=[::1] "; > {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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1016) Run bmcheck.sh regularly to spot inconsistencies between byteman scripts and the code

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1016?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1016: -------------------------------- Issue Type: Task (was: Enhancement) > Run bmcheck.sh regularly to spot inconsistencies between byteman scripts and the code > ------------------------------------------------------------------------------------- > > Key: JBTM-1016 > URL: https://issues.jboss.org/browse/JBTM-1016 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Amos Feng > Labels: assign > Fix For: 5.0.0.M3 > > > I've found many bugs in the XTS crash recovery tests that where due to changes being made to the XTS code without updating the byteman scripts. The problem is that these inconsistencies often go unnoticed when the tests run, until you notice a failure in the test. > Can we run bmcheck as part of the maven build and make the build fail if it detects errors? Needs to be integrated into the poms, perhaps by an exec in an antrun plugin > NOTE: Before raising the pull req it will be necessary to resolve any the discovered 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-1184) Update documentation for application server changes AS7

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1184?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1184: -------------------------------- Issue Type: Task (was: Feature Request) > Update documentation for application server changes AS7 > ------------------------------------------------------- > > Key: JBTM-1184 > URL: https://issues.jboss.org/browse/JBTM-1184 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1339) Ensure that JTS can use the JDK ORB provided by AS7

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1339?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1339: ----------------------------------- Fix Version/s: (was: 4.17.4) > Ensure that JTS can use the JDK ORB provided by AS7 > --------------------------------------------------- > > Key: JBTM-1339 > URL: https://issues.jboss.org/browse/JBTM-1339 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTS > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.0.Final > > Original Estimate: 2 days > Remaining Estimate: 2 days > -- 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