July 2011 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-770) incorrect cleanup registration causes memory leak

by Jonathan Halliday (JIRA)

incorrect cleanup registration causes memory leak ------------------------------------------------- Key: JBTM-770 URL: https://jira.jboss.org/browse/JBTM-770 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS Affects Versions: 4.6.1.CP06, 4.12.0 Reporter: Jonathan Halliday Assignee: Mark Little Fix For: 4.13.0, 4.6.1.CP08 jts.TransactionImple constructors attempt to optimize the cleanup callback needed to remove entries from _transactions, bypassing the ORB for interposition scenarios: theTx = (TwoPhaseCoordinator) BasicAction.Current(); if (theTx != null) { theTx.addSynchronization(new LocalCleanupSynchronization(this)); } else { registerSynchronization(new CleanupSynchronization(this)); } Unfortunately this does not work and leads to memory leaks on _transactions in certain cases. Specifically, where theTx is a ServerTransaction (i.e. extends ArjunaTransactionImple, which extends TwoPhaseCoordinator), the callbacks run (by ArjunaTransactionImple.do[Before|After]Completion()) are those in ArjunaTransactionImple._syncs, not the masked ones in TwoPhaseCoordinator._syncs. Thus using TwoPhaseCoordinator.addSynchronization registers a callback which is never invoked. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

9
15
0 / 0

[JBoss JIRA] Created: (JBTM-852) Setting SettingVolatile store still creates an ObjectStore directory on the disk

by Mircea Markus (JIRA)

Setting SettingVolatile store still creates an ObjectStore directory on the disk --------------------------------------------------------------------------------- Key: JBTM-852 URL: https://issues.jboss.org/browse/JBTM-852 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.15.0 Reporter: Mircea Markus Priority: Minor Even when configuring {code:java} arjPropertyManager.getObjectStoreEnvironmentBean().setObjectStoreType(VolatileStore.class.getName()) {code} an "ObjectStore" directory is created on the disk. After discussing with JTM team this doesn't cause any real problem in the sense that nothing is written to the disk, but this is annoying and might create confusion between the users. A workaround would be to add the following configuration together with the previously mentioned one: {code:java} BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class, "communicationStore").setObjectStoreType(VolatileStore.class.getName()) {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

6
21
0 / 0

[JBoss JIRA] Created: (JBTM-847) Look into how AssumedComplete works for ArjunaJTA (and jtax)

by Mark Little (JIRA)

Look into how AssumedComplete works for ArjunaJTA (and jtax) ------------------------------------------------------------ Key: JBTM-847 URL: https://issues.jboss.org/browse/JBTM-847 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Reporter: Mark Little Assignee: Tom Jenkinson When a transaction cannot be completed over a long period of time, a scanner is supposed to kick in and move the log elsewhere. Those scanners exist in ArjunaCore and ArjunaJTS, but do not appear to be there in ArjunaJTA. It should be straightforward to add them by using the base class in ArjunaCore, but investigate whether they are present already and just not obvious. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
8
0 / 0

[JBoss JIRA] Created: (JBTM-247) Update (if necessary) the new integration layer SPIs

by Mark Little (JIRA)

Update (if necessary) the new integration layer SPIs ---------------------------------------------------- Key: JBTM-247 URL: http://jira.jboss.com/jira/browse/JBTM-247 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Implementation, JTS Implementation Reporter: Mark Little Assigned To: Jonathan Halliday http://anonsvn.jboss.org/repos/jbossas/projects/integration/ -- 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

12 years, 2 months

3
8
0 / 0

[JBoss JIRA] Created: (JBTM-520) Include distribution information in MANIFEST.MF

by Jesper Pedersen (JIRA)

Include distribution information in MANIFEST.MF ----------------------------------------------- Key: JBTM-520 URL: https://jira.jboss.org/jira/browse/JBTM-520 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.6.0 Reporter: Jesper Pedersen Priority: Minor It would be nice if the jar files contain information inside the MANIFEST.MF files - like Implementation-Title Implementation-Vendor Implementation-Vendor-Id Implementation-Version -- 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

12 years, 2 months

4
14
0 / 0

[JBoss JIRA] Created: (JBTM-810) Set the default configuration to use socketless communication betweeen the transaction manager and recovery manager for JTA

by Tom Jenkinson (JIRA)

Set the default configuration to use socketless communication betweeen the transaction manager and recovery manager for JTA --------------------------------------------------------------------------------------------------------------------------- Key: JBTM-810 URL: https://jira.jboss.org/browse/JBTM-810 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 4.15.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

4
12
0 / 0

[JBoss JIRA] Created: (JBTM-759) Errors in the Failure Recovery Guide

by Mauro Molinari (JIRA)

Errors in the Failure Recovery Guide ------------------------------------ Key: JBTM-759 URL: https://jira.jboss.org/browse/JBTM-759 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Reporter: Mauro Molinari Priority: Minor While reading the Failure Recovery Guide I found some errors: - page 7: line 3 seems to be victim of an erroneous copy-and-paste - page 11: line 3 of the pseudo code for the first pass of AtomicAction is not clear, since the vector has been just created and transactions are added to it within the same loop body... - page 24: the chapter is named "Chapter 1", while it should be "Chapter 2" - page 30: I think "Configuration options" should be "Chapter 3"; moreover, there's no warning about the fact that the table is deprecated (because it shows the configuration options with the old names). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

4
10
0 / 0

[JBoss JIRA] Created: (JBTM-761) Errors in JBossTS JTA documentation

by Mauro Molinari (JIRA)

Errors in JBossTS JTA documentation ----------------------------------- Key: JBTM-761 URL: https://jira.jboss.org/browse/JBTM-761 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.11.0 Reporter: Mauro Molinari Priority: Minor While reading the JBossTS JTA documentation, I found the following problems: Administration Guide: - page 7: in the "ArjunaTA runtime information" chapter there's a typographic error ("<name>EnvironmentBean classes") - page 8: in the "Configuring the Recovery Manager" chapter I think that "arjuna.properties" should rather be "jbossts-properties.xml" Programmers Guide: - page 8: in the last paragraph there's a repetition: "and contains also contains a mapping of the X/Open XA protocol" - page 12: in the "Resource enlistment" chapter, second paragraph, there: "See [? missing reference?] for details on how the implementation of the XAResource can affect recovery..." Moreover, all the chapters are numbered as "Chapter 1". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

4
11
0 / 0

[JBoss JIRA] Created: (JBTM-758) Errors in documentation: Transaction Core Programmers Guide

by Mauro Molinari (JIRA)

Errors in documentation: Transaction Core Programmers Guide ----------------------------------------------------------- Key: JBTM-758 URL: https://jira.jboss.org/browse/JBTM-758 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.11.0 Reporter: Mauro Molinari Priority: Minor I'm going to highlight some errors I found during the reading of the Transaction Core Programmers Guide (TX-PG-5/11/10): - page 31: when describing LogManager: "The *shared* parameter only has meaning if *ot* is RECOVERABLE"; actually the two parameters are named *objectModel* and *ObjectType* respectively in the caption of the paragraph - page 36: in the example, I think the line with "A.add(new ShutdownRecord(...)" is not pertinent - page 64: the last sentence says that the issues described in that paragraph will be addressed in the next section, but the next section is about configuration - page 65: the second paragraph has some typographic problem (<module>propertyManager, <name>EnvironmentBean) - page 69: in the second paragraph: "All of the implementations are derived from the ObjectStore interface"; actually, ObjectStore is a class to extend, not an interface to implement Lastly, an observation about the depiction of finalizers as "destructors": in this guide, the finalize method is considered a destructor. However, in Java it is not actually. Anyway, it's not clear if calling terminate() in the finalize() is mandatory or not. If so, why isn't it called directly in com.arjuna.ats.arjuna.StateManager.finalize()? If not, I have another doubt. In all the examples of user classes (i.e. page 60) the finalize() is implemented as: public void finalize() { super.terminate(); } However, super.finalize() is not called. Isn't it risky? I mean, in this way the code in com.arjuna.ats.arjuna.StateManager.finalize() is never called... I think the documentation should be more clear on this subject. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

4
10
0 / 0

[JBoss JIRA] Created: (JBTM-829) update build to use AS7

by Jonathan Halliday (JIRA)

update build to use AS7 ----------------------- Key: JBTM-829 URL: https://issues.jboss.org/browse/JBTM-829 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Build System Affects Versions: 4.14.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.15.0 Since the 4.15 release is intended for use in AS7 we should use that to get dependency versions rather than the older AS6 as in 4.14. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
13
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues July 2011