January 2008 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-324) Enable Setting Port with com.arjuna.ats.arjuna.recovery.transactionStatusManagerPort

by Thomas Krieger (JIRA)

Enable Setting Port with com.arjuna.ats.arjuna.recovery.transactionStatusManagerPort ------------------------------------------------------------------------------------ Key: JBTM-324 URL: http://jira.jboss.com/jira/browse/JBTM-324 Project: JBoss Transaction Manager Issue Type: Patch Security Level: Public (Everyone can see) Components: Recovery Affects Versions: 4.2.3.SP5 Reporter: Thomas Krieger If you set <property name="com.arjuna.ats.internal.arjuna.recovery.recoveryPort" value="1213"/> <property name="com.arjuna.ats.arjuna.recovery.transactionStatusManagerPort" value="1214"/> you get the following Exception: com.arjuna.ats.arjuna.exceptions.FatalError: [com.arjuna.ats.internal.arjuna.utils.SocketProcessId_2] - SocketProcessId.getpid could not get unique port. at com.arjuna.ats.internal.arjuna.utils.SocketProcessId.getpid(SocketProcessId.java:122) at com.arjuna.ats.arjuna.utils.Utility.getpid(Utility.java:206) at com.arjuna.ats.arjuna.common.Uid.<init>(Uid.java:105) at com.arjuna.ats.arjuna.utils.Utility.getProcessUid(Utility.java:218) at com.arjuna.ats.internal.arjuna.recovery.TransactionStatusManagerItem.<init>(TransactionStatusManagerItem.java:323) at com.arjuna.ats.internal.arjuna.recovery.TransactionStatusManagerItem.createAndSave(TransactionStatusManagerItem.java:71) at com.arjuna.ats.arjuna.recovery.TransactionStatusManager.start(TransactionStatusManager.java:157) at com.arjuna.ats.arjuna.recovery.TransactionStatusManager.<init>(TransactionStatusManager.java:78) at com.arjuna.ats.arjuna.coordinator.TxControl.<clinit>(TxControl.java:312) at com.arjuna.ats.jbossatx.jta.TransactionManagerService.startService(TransactionManagerService.java:139) The first problem is that in TransactionStatusManager calling ServerSocket socket = SocketProcessId.getSocket(); returns null, so that a new ServerSocket is created in TransactionStatusManager getTsmServerSocket (int port) (line 218) The solution is, to call (new SocketProcessId()).getpid(); in the constructor. The second problem is that RecoveryManagerImple.activeRecoveryManager uses the wrong port (line 197): SocketProcessId uses Property com.arjuna.ats.arjuna.recovery.transactionStatusManagerPort and not com.arjuna.ats.internal.arjuna.recovery.recoveryPort. Solution is to change activeRecoveryManager (). Thomas Krieger for P&I Team Tess (Ralph-Rainer Welzel, Andreas Rugullies ...) -- 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, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (JBTM-274) JBossWorkManager converts from seconds to milliseconds

by Mark Little (JIRA)

JBossWorkManager converts from seconds to milliseconds ------------------------------------------------------ Key: JBTM-274 URL: http://jira.jboss.com/jira/browse/JBTM-274 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Mark Little Priority: Critical Fix For: 4.2.3.SP6 Transaction timeouts on the work manager were assumed to be in seconds. JBossWorkManager is converting them to milliseconds before we get the timeout. We then convert them to milliseconds (under the assumption they were defined in seconds). -- 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, 8 months

2
9
0 / 0

[JBoss JIRA] Created: (JBTM-320) jta/jtax cross-package logging broken

by Jonathan Halliday (JIRA)

jta/jtax cross-package logging broken ------------------------------------- Key: JBTM-320 URL: http://jira.jboss.com/jira/browse/JBTM-320 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS Implementation Affects Versions: 4.3.0.BETA2, 4.2.3.SP6 Reporter: Jonathan Halliday Assigned To: Jonathan Halliday Fix For: 4.2.3.SP8, 4.3.0.BETA3 Some classes in jtax i.e. the JTS based JTA implementation, use logging support from the jta rather than jtax pakage. This is the only instance of cross-package logging in the codebase. This is supported by the LoggerSetup helper class, which merges the jtax log messages properties file into the jta logger using addResourceBundle. That means that jtax code can call e.g. jtaLogger.loggerI18N.warn("com.arjuna.ats.internal.jta.transaction.jts.syncproblem"); and the message key will get resolved correctly. jtaLogger.logger.* is not internationalized i.e. does not use resource bundles, so it's fine too. The problem comes with jtax code's use of e.g. jtaLogger.logMesg.getString("com.arjuna.ats.internal.jta.transaction.jts.subordinate.invalidstate") as is found in many new Exception(...) type statements and elsewhere. Since this code bypasses the loggerI18N and goes direct to the un-merged message bundle, it can resolve only jta keys, not jtax ones. Because it's used mostly in exception handlers, the problem goes unnoticed until something breaks, at which point you fail to get a useful error message. -- 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, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBTM-278) XAResource.end error may not cause rollback

by Jonathan Halliday (JIRA)

XAResource.end error may not cause rollback ------------------------------------------- Key: JBTM-278 URL: http://jira.jboss.com/jira/browse/JBTM-278 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.3.SP5 Reporter: Jonathan Halliday Assigned To: Mark Little Fix For: 4.4 An XAResource.end call may return an XA_RB* error. In such case, the resource should (but currently does not) still get rollback called on it too. Update XAResourceRecord.java to fix. -- 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, 8 months

2
9
0 / 0

[JBoss JIRA] Created: (JBTM-288) Add suspend/resume to recovery manager

by Mark Little (JIRA)

Add suspend/resume to recovery manager -------------------------------------- Key: JBTM-288 URL: http://jira.jboss.com/jira/browse/JBTM-288 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.4 Start/Stop are really termination states. No way to restart a recovery manager once it is stopped. -- 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, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBTM-291) Change default timeout mechanism from NORMAL to DYNAMIC.

by Mark Little (JIRA)

Change default timeout mechanism from NORMAL to DYNAMIC. -------------------------------------------------------- Key: JBTM-291 URL: http://jira.jboss.com/jira/browse/JBTM-291 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Andrew Dinn Fix For: 4.4 MR1 -- 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, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBTM-307) Update xa_prepare handling for rm/err failures in light of modern RMs

by Mark Little (JIRA)

Update xa_prepare handling for rm/err failures in light of modern RMs --------------------------------------------------------------------- Key: JBTM-307 URL: http://jira.jboss.com/jira/browse/JBTM-307 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3.SP6 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.4 Initial RM implementations of XAResources that threw RMERR/RMFAIL on prepare didn't honour the XA spec, so TS had to assume heuristic outcome. That's no longer the case (probably hasn't been for many years). We can/should remove that option in the codebase. -- 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, 9 months

2
8
0 / 0

[JBoss JIRA] Created: (JBTM-323) TransactionSynchronizationRegistry should not be in JTA 1.0

by Jonathan Halliday (JIRA)

TransactionSynchronizationRegistry should not be in JTA 1.0 ----------------------------------------------------------- Key: JBTM-323 URL: http://jira.jboss.com/jira/browse/JBTM-323 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3.SP6 Reporter: Jonathan Halliday Assigned To: Jonathan Halliday Fix For: 4.2.3.SP8 TransactionSynchronizationRegistryImple is present in the 4.2.3 branch (i.e. JTA 1.0.1b impl) but is really a feature for the JTA 1.1 i.e. TS 4.3+. Its presence in the app server's JNDI is causing problems as the 4.2.3 branch has a non-serializable prototype which does not play nice with JNDI, unlike the finished version in trunk. However, it should not be in JNDI in the first place. -- 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, 9 months

1
2
0 / 0

[JBoss JIRA] Work logged: (JBTM-123) Integrate with AS 5.0

by Andrew Dinn (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-123?page=worklog#action_12394670 ] Andrew Dinn logged work on JBTM-123: ------------------------------------ Time Spent: 2 days Remaining Estimate: 0 minutes Time Spent: 2 days modified XTS to conform to AS 5.0 > Integrate with AS 5.0 > --------------------- > > Key: JBTM-123 > URL: http://jira.jboss.com/jira/browse/JBTM-123 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTS Implementation, JTA Implementation > Affects Versions: 4.2.1 > Reporter: Mark Little > Assigned To: Jonathan Halliday > Fix For: 4.4 > > Time Spent: 2 days > Remaining Estimate: 0 minutes > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-322) remove obsolete JBossAS patches

by Jonathan Halliday (JIRA)

remove obsolete JBossAS patches ------------------------------- Key: JBTM-322 URL: http://jira.jboss.com/jira/browse/JBTM-322 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Implementation, JTS Implementation Affects Versions: 4.3.0.BETA2 Reporter: Jonathan Halliday Assigned To: Jonathan Halliday Fix For: 4.3.0.BETA3 The TS 4.3 release supports integration with JBossAS 5.0, not earlier releases. Therefore we no longer need to ship patches for JBossAS 4.0.x with it. -- 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, 10 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues January 2008