August 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1875) Update all Maven plugins

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1875?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1875: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Update all Maven plugins > ------------------------ > > Key: JBTM-1875 > URL: https://issues.jboss.org/browse/JBTM-1875 > 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.M5 > > > I've noticed many of our maven plugins are getting out of date. Running old plugins can dramatically slow down the build and has caused memory leaks in the past. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1721) REST-AT participant support framework should support synchronizations

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1721?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1721: ---------------------------------- Fix Version/s: 5.0.0.Final > REST-AT participant support framework should support synchronizations > --------------------------------------------------------------------- > > Key: JBTM-1721 > URL: https://issues.jboss.org/browse/JBTM-1721 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: REST > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Fix For: 5.0.0.Final > > > JBTM-1365 introduced an interface for simplifying participant registration into a REST-AT transaction by providing a callback for prepare/commit/rollback support. Please can we also have a similar mechanism for synchronizations. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1618) Git pull requests: retest this please!

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1618?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1618: ---------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.Final) > Git pull requests: retest this please! > -------------------------------------- > > Key: JBTM-1618 > URL: https://issues.jboss.org/browse/JBTM-1618 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Trivial > Fix For: 6.0.0.Final > > > If someone comments on a pull requesting a retest it would be nice that a job got scheduled. > I don't really know how easy it is to do that, maybe the build bot needs to respond to emails? -- 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

10 years, 8 months

1
0
0 / 0

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

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1181?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1181: ---------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.Final) > 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

10 years, 8 months

1
0
0 / 0

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

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1184?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1184: ---------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.Final) > 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

10 years, 8 months

1
0
0 / 0

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

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1369?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1369: ---------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.Final) > 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

10 years, 8 months

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 Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1249?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1249: ---------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.Final) > 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1578) Run a performance benchmark over BlackTie

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1578?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1578: ----------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.Final) > Run a performance benchmark over BlackTie > ----------------------------------------- > > Key: JBTM-1578 > URL: https://issues.jboss.org/browse/JBTM-1578 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: BlackTie, Performance Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Minor > Fix For: 6.0.0.Final > > > Will BlackTie work with: http://www.infor.uva.es/~diego/tpcc-uva.html it is an opensource TPC-C benchmark -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1572) a failure in the txfooapp quickstart does not return -1 so it appears to run even when it hasn't

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1572?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1572: ----------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.Final) > a failure in the txfooapp quickstart does not return -1 so it appears to run even when it hasn't > ------------------------------------------------------------------------------------------------ > > Key: JBTM-1572 > URL: https://issues.jboss.org/browse/JBTM-1572 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 6.0.0.Final > > Attachments: client.valgrind, server.valgrind, windbg.out > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Note, it will definitely be worth doing this in a branch/pull as I suspect the database isn't running atm so that will need a kick too -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1310) Store JTS participant records with their parent transaction

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1310?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1310: ----------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.Final) > Store JTS participant records with their parent transaction > ----------------------------------------------------------- > > Key: JBTM-1310 > URL: https://issues.jboss.org/browse/JBTM-1310 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JTS > Affects Versions: 4.17.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 6.0.0.Final > > > In JTA mode participant records are stored together with their owning transaction but this does not happen in JTS mode even when the parent transaction is local. This results in extra log writes thus impacting throughput. -- 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

10 years, 8 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 August 2013