October 2012 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-465) Consider allowing JDBCImple to manage connection lifecycles

by Mark Little (JIRA)

Consider allowing JDBCImple to manage connection lifecycles ----------------------------------------------------------- Key: JBTM-465 URL: https://jira.jboss.org/jira/browse/JBTM-465 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.5 Reporter: Mark Little Fix For: future JDBCImple assumes that the JDBCAccess class manages the lifecycle of connections it returns. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 12 months

3
13
0 / 0

[JBoss JIRA] Created: (JBTM-589) Document static initializers

by Mark Little (JIRA)

Document static initializers ---------------------------- Key: JBTM-589 URL: https://jira.jboss.org/jira/browse/JBTM-589 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA, JTS, Recovery, Transaction Core, XTS Affects Versions: 4.7.0 Reporter: Mark Little Assignee: Mark Little Fix For: future -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 12 months

2
13
0 / 0

[JBoss JIRA] (JBTM-1313) Performance related work that involves other products should be in a separate repository

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-1313: -------------------------------------- Summary: Performance related work that involves other products should be in a separate repository Key: JBTM-1313 URL: https://issues.jboss.org/browse/JBTM-1313 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Demonstrator Affects Versions: 5.0.0.M1 Reporter: Michael Musgrove Assignee: Michael Musgrove Priority: Minor Fix For: 5.0.0.M2 Any performance related activities done by the dev team that require installation of other transaction managers should done a repo that is separate from the main narayana repo. Currently this includes: - some changes to the jts quickstart - the performance harness in qa/tests/product -- 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, 12 months

2
3
0 / 0

[JBoss JIRA] (JBTM-1299) Narayana artifacts are difficult to find after a build

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-1299: -------------------------------------- Summary: Narayana artifacts are difficult to find after a build Key: JBTM-1299 URL: https://issues.jboss.org/browse/JBTM-1299 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build System Affects Versions: 4.17.0 Reporter: Michael Musgrove Assignee: Tom Jenkinson Fix For: 5.0.0.M2 The new build system leaves the installable jars in their respective module target directories. It is not obvious which jars are which so it would be nice if we can provide, near the top of the top level README, a brief description of the purpose and location of each target produced by the build. -- 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, 12 months

2
3
0 / 0

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

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1184: ----------------------------------- Summary: Update documentation for application server changes AS7 Key: JBTM-1184 URL: https://issues.jboss.org/browse/JBTM-1184 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Tom Jenkinson 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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 12 months

1
3
0 / 0

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

by Michel PRUNET (JIRA)

Michel PRUNET created JBTM-1249: ----------------------------------- Summary: 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, JCA, JTS Affects Versions: 4.16.2 Environment: JBoss AS 7.1.1 Final, Windows, Oracle Reporter: Michel PRUNET Assignee: Tom Jenkinson 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, 12 months

3
11
0 / 0

[JBoss JIRA] (JBTM-1330) Support Last Logging Resource

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1330: ----------------------------------- Summary: Support Last Logging Resource Key: JBTM-1330 URL: https://issues.jboss.org/browse/JBTM-1330 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.0.0.M3 Where you multiplex the users application table and the transaction log in the same JDBC local 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, 12 months

1
5
0 / 0

[JBoss JIRA] Created: (JBTM-312) Add clustering support

by Mark Little (JIRA)

Add clustering support ---------------------- Key: JBTM-312 URL: http://jira.jboss.com/jira/browse/JBTM-312 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Implementation, JTS Implementation, Recovery, Transaction Core, WS-T Implementation Affects Versions: 4.3.0.BETA2 Reporter: Mark Little Assigned To: Mark Little -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 12 months

5
10
0 / 0

[JBoss JIRA] (JBTM-1278) Additional debug information required for transaction's Xid with Oracle

by Tom Ross (JIRA)

Tom Ross created JBTM-1278: ------------------------------ Summary: Additional debug information required for transaction's Xid with Oracle Key: JBTM-1278 URL: https://issues.jboss.org/browse/JBTM-1278 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.16.1 Environment: Jboss EAP 5.x Reporter: Tom Ross Assignee: Tom Jenkinson It seems that Oracle is returning different XIDs each time (with the same content) which makes it difficult to debug if the same XID is in more than one scan. Additional debug information is required in Xid to make debugging easier. -- 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, 12 months

2
4
0 / 0

[JBoss JIRA] (JBTM-1116) Document properties

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1116: ----------------------------------- Summary: Document properties Key: JBTM-1116 URL: https://issues.jboss.org/browse/JBTM-1116 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Reporter: Tom Jenkinson Assignee: Tom Jenkinson In the pre-Bean days of setting properties, we had all of the TS properties called out in a properties.xml file. In that file there were copious comments to say what the property was for and whether it should be changed. We also documented these properties in the docs. It seems from some investigation that Mike and I have done today that the migration away from the properties file to using MBeans has removed those comments and the docs for the properties. Sometimes the comments do appear in the code. If you go back to before everything got turned everything into a Bean (probably 4.6.1 GA) then look in the etc directories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 12 months

4
11
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues October 2012