October 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1184) Update documentation for application server changes AS7

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1184?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-1184: ----------------------------------- Status update please? > 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: 6.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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1249) Update documentation to resolve XA recovery Failed on Oracle (pad-xid=true not propagated to the XARecoveryModule)

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1249?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-1249: ----------------------------------- Isn't this done? > Update documentation to resolve XA recovery Failed on Oracle (pad-xid=true not propagated to the XARecoveryModule) > ------------------------------------------------------------------------------------------------------------------ > > Key: JBTM-1249 > URL: https://issues.jboss.org/browse/JBTM-1249 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Application Server Integration, Documentation, JCA, JTS > Affects Versions: 4.16.2 > Environment: JBoss AS 7.1.1 Final, Windows, Oracle > Reporter: Michel PRUNET > Assignee: Gytis Trikleris > Labels: jboss, jts, recovery, xa > Fix For: 6.0.0.Final > > Attachments: TestEJB.zip > > Original Estimate: 20 minutes > Remaining Estimate: 20 minutes > > The XARecoveryManager is unable to recover an Oracle Prepared Transaction. > The reason: > Oracle needs the Xid to be padded (pad-xid set to true in xa-datasource). > When the method XARecoveryModule.getNewXAResource(Xid xid) is called. The value of xid is not padded (retrieved from the tx-object-store). The XID contained in the RecoveryXids are padded (retrieved from oracle). When the method execute xids.remove(xid), it never found the xid. The transaction is never recovered. > In a debug session, if you pad the xid in that method (change the xid.gtrud_length and or bqual_length), the transaction will be recovered successfully. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1369) Benchmark performance difference between JacORB and JDK ORB

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1369?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-1369: ----------------------------------- Can we have an update on this? > 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: 6.0.0.Final > > > 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1494) Produce performance figures to show performance improvements of Compensations over ACID

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1494?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-1494: ----------------------------------- Performance is a false metric here. People shouldn't use compensations because they want to go faster (or slower). They should use them because ACID transactions are not appropriate. Remember that there is a trade-off here and it's often to do with consistency. > Produce performance figures to show performance improvements of Compensations over ACID > --------------------------------------------------------------------------------------- > > Key: JBTM-1494 > URL: https://issues.jboss.org/browse/JBTM-1494 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Performance Testing, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 6.0.0.Final > > > As part of evangelising compensations, it would be useful to show performance comparisons for different classes of applications. > Ideally, these results should show that that, for certain classes of applications, the performance of a compensation-based transaction is a lot better than for an ACID transaction. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1558) Prune redundant code from jboss-transaction-spi

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1558?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-1558: ----------------------------------- There are a few SPI related issues at the moment. Maybe cross-link them? > Prune redundant code from jboss-transaction-spi > ----------------------------------------------- > > 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: Michael Musgrove > Fix For: 6.0.0.Final > > Attachments: as8.zip, ij-tx-spi.txt > > > We can use jboss-transaction-spi to get started > There is much old code in jboss-transaction-spi that does not get used in AS7 and does not apply to Narayana. > Run tattletale over AS8, identify redundant methods and add new SPI functions if necessary -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1591) Ensure our ESB usage works on AS7

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1591?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-1591: ----------------------------------- ESB = Enterprise Service Bus? > Ensure our ESB usage works on AS7 > --------------------------------- > > Key: JBTM-1591 > URL: https://issues.jboss.org/browse/JBTM-1591 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Tom Jenkinson > -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1699) Changes to the transaction SPI

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1699?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-1699: ----------------------------------- Should we link this to JBTM-1970 as well? > Changes to the transaction SPI > ------------------------------ > > Key: JBTM-1699 > URL: https://issues.jboss.org/browse/JBTM-1699 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Application Server Integration > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 6.0.0.Final > > Original Estimate: 1 week, 3 days > Remaining Estimate: 1 week, 3 days > > wildfly is using a number of our internal com.arjuna interfaces which we would like to resolve by providing the same functionality in the transactions SPI. > Additionally the current SPI contains a number of unused classes which need removing. > I have created https://github.com/jbosstm/jboss-transaction-spi to manage the changes. To avoid any potential confusion and to make it clear who is responsible for the SPI we will be changing the package names. -- 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, 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 Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1181?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-1181: ----------------------------------- Now that we have moved the transactional file to a different repo, we should remove all references of it from the mainline docs (move any docs it has to the same repo as the source). > 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: 6.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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1773) Tidy up OrbPortability module

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1773?page=com.atlassian.jira.plugin.... ] Mark Little resolved JBTM-1773. ------------------------------- Fix Version/s: 5.0.0.M6 Resolution: Done > Tidy up OrbPortability module > ----------------------------- > > Key: JBTM-1773 > URL: https://issues.jboss.org/browse/JBTM-1773 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTS > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Mark Little > Priority: Minor > Fix For: 5.0.0.M6 > > > Readme.txt can probably be removed, for instance. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1773) Tidy up OrbPortability module

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1773?page=com.atlassian.jira.plugin.... ] Mark Little closed JBTM-1773. ----------------------------- > Tidy up OrbPortability module > ----------------------------- > > Key: JBTM-1773 > URL: https://issues.jboss.org/browse/JBTM-1773 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTS > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Mark Little > Priority: Minor > Fix For: 5.0.0.M6 > > > Readme.txt can probably be removed, for instance. -- 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, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues October 2013