jbossts-issues June 2007

jbossts-issues@lists.jboss.org

1 participants
43 discussions

[JBoss JIRA] Created: (JBTM-232) setRollbackOnly works differently in local JTA to JTS/JTA

by Mark Little (JIRA)

setRollbackOnly works differently in local JTA to JTS/JTA --------------------------------------------------------- Key: JBTM-232 URL: http://jira.jboss.com/jira/browse/JBTM-232 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3.SP4 Reporter: Mark Little Assigned To: Mark Little Priority: Critical Fix For: 4.2.3.SP5 In OTS, calling rollback_only can throw exceptions that JTA doesn't require. In JTA, if the outcome of the transaction is already aborted, for example, that doesn't have to be an error. Make things consistent. -- 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

16 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-231) syncwhenaborted I18N message not in resource bundle causes JCA import to fail

by Mark Little (JIRA)

syncwhenaborted I18N message not in resource bundle causes JCA import to fail ----------------------------------------------------------------------------- Key: JBTM-231 URL: http://jira.jboss.com/jira/browse/JBTM-231 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3.SP4 Reporter: Mark Little Assigned To: Mark Little Priority: Blocker Fix For: 4.2.3.SP5 The /* * @message com.arjuna.ats.internal.jta.transaction.arjunacore.syncwhenaborted * [com.arjuna.ats.internal.jta.transaction.arjunacore.syncwhenaborted] * Can't register synchronization because the transaction is in aborted state */ occurs in a normal comment which means that the doclet-based resource bundle generation mechanism fails to put it into the resource bundle. In some circumstances, when this error would normally be required, the logger doesn't find it and throws an exception that may cause the application to fail. -- 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

16 years, 11 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBTM-214) Transactions are not removed on completion resulting in OOMEs

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-214?page=all ] Mark Little closed JBTM-214. ---------------------------- Resolution: Done > Transactions are not removed on completion resulting in OOMEs > ------------------------------------------------------------- > > Key: JBTM-214 > URL: http://jira.jboss.com/jira/browse/JBTM-214 > Project: JBoss Transaction Manager > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: JTA Implementation > Affects Versions: 4.2, 4.2.1, 4.2.2, 4.2.3 > Reporter: Leon van Zantvoort > Assigned To: Jonathan Halliday > Priority: Critical > Fix For: 4.2.3.SP4 > > Attachments: TransactionReaper.java > > > Please find attached a patched TransactionReaper class. This patch fixes a memory issue, which is seen in JavaSE (stand-alone client) applications integrating JBossTS. An OOME is raised in case the client application starts multiple (timeout bound) transactions concurrently. > More information can be found at line 374 of the patched class. -- 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

16 years, 11 months

1
0
0 / 0

← Newer
1
2
3
4
5
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues June 2007