jbossts-issues January 2009

jbossts-issues@lists.jboss.org

1 participants
125 discussions

[JBoss JIRA] Updated: (JBTM-61) JSR 156 support

by Jonathan Halliday (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-61?page=com.atlassian.jira.plugin... ] Jonathan Halliday updated JBTM-61: ---------------------------------- Fix Version/s: future (was: 4.6) Affects: [Documentation (Ref Guide, User Guide, etc.), Interactive Demo/Tutorial] (was: [Interactive Demo/Tutorial, Documentation (Ref Guide, User Guide, etc.)]) > JSR 156 support > --------------- > > Key: JBTM-61 > URL: https://jira.jboss.org/jira/browse/JBTM-61 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA Implementation, WS-T Implementation > Reporter: Mark Little > Assignee: Jonathan Halliday > Fix For: future > > > Update the WS-T API to be compliant with the latest version of JSR 156 (JAXTX). -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBTM-111) Check QA into CVS

by Jonathan Halliday (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-111?page=com.atlassian.jira.plugi... ] Jonathan Halliday closed JBTM-111. ---------------------------------- Resolution: Duplicate Issue Covered by JBTM-357 (add DTF tests to repository) and JBTM-390 (add ability to run DTF tests locally) > Check QA into CVS > ----------------- > > Key: JBTM-111 > URL: https://jira.jboss.org/jira/browse/JBTM-111 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Testing > Affects Versions: 4.2 > Reporter: Mark Little > Assignee: Jonathan Halliday > Fix For: 4.6 > > -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-460) fix sybase locking in DTF JDBC tests

by Jonathan Halliday (JIRA)

fix sybase locking in DTF JDBC tests ------------------------------------ Key: JBTM-460 URL: https://jira.jboss.org/jira/browse/JBTM-460 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.5 Reporter: Jonathan Halliday Fix For: 4.6 Some DTF JDBC tests use multiple connections (i.e. XA tx branches) to manipulate the same table. Where the database does not share locks between tx branches and does not use row level locking this causes deadlock problems. For MS SQLServer we force row level locking by creating a uniq index on the table. For sybase this does not work. Therefore, we need to explicitly detect that the test is running against sybase and issue db specific SQL to force row level locking. -- 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

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-441) AppServerJDBCXARecovery does not cope with stale connections

by Jonathan Halliday (JIRA)

AppServerJDBCXARecovery does not cope with stale connections ------------------------------------------------------------ Key: JBTM-441 URL: https://jira.jboss.org/jira/browse/JBTM-441 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Application Server Integration Affects Versions: 4.2.3.CP02, 4.2.3.SP7 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.2.3.SP8, 4.2.3.CP03 If the db bounces whilst the app server stays up, the AppServerJDBCXARecovery is left holding an invalid connection, which causes XAResource on it to throw spurious errors. It should refresh the connection on every call, or at least check it for validity before handing out an XAResource based on it. -- 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

15 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBTM-442) AppServerJDBCXARecovery fails if datasource not yet deployed

by Jonathan Halliday (JIRA)

AppServerJDBCXARecovery fails if datasource not yet deployed ------------------------------------------------------------ Key: JBTM-442 URL: https://jira.jboss.org/jira/browse/JBTM-442 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Application Server Integration Affects Versions: 4.2.3.CP02, 4.2.3.SP7 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.2.3.SP8, 4.2.3.CP03 At As startup, the transaction manager may deploy before the datasources. If a recovery pass occurs before the datasource is deployed, Bad Things will happen. Either delay the first recovery pass at startup, or make the AppServerJDBCXARecovery rebust against this. -- 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

15 years, 10 months

2
2
0 / 0

← Newer
1
...
10
11
12
13
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues January 2009