June 2010 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-531) com.arjuna.ats.internal.jdbc.DynamicClass.shutdownDataSource(XADataSource) is never called

by Mauro Molinari (JIRA)

com.arjuna.ats.internal.jdbc.DynamicClass.shutdownDataSource(XADataSource) is never called ------------------------------------------------------------------------------------------ Key: JBTM-531 URL: https://jira.jboss.org/jira/browse/JBTM-531 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Affects Versions: 4.6.0, 4.5.0 Reporter: Mauro Molinari Priority: Critical com.arjuna.ats.internal.jdbc.DynamicClass.shutdownDataSource(XADataSource) is never called by com.arjuna.ats.internal.jdbc.DirectRecoverableConnection. >From what I could understand (but I'm not sure of this), after calling com.arjuna.ats.internal.jdbc.DirectRecoverableConnection.closeCloseCurrentConnection() the DirectRecoverableConnection won't be used anymore, so that method could be a good candidate to call _dynamicConnection.shutDownDataSource(_theDataSource) and to null both _dynamicConnection and _theDataSource. This problem could be quite severe, because if the XADataSource needs to be shut down in order to release resources, this could lead to leaks. Moreover, I was wondering if a caching of the dynamic class wouldn't be a good idea... as of now, a NEW XA data source is created every time a new connection is requested... and this could be expensive... -- 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, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBTM-529) Provide a way to disable connection pooling within a transaction

by Mauro Molinari (JIRA)

Provide a way to disable connection pooling within a transaction ---------------------------------------------------------------- Key: JBTM-529 URL: https://jira.jboss.org/jira/browse/JBTM-529 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration, Documentation, JTA Affects Versions: 4.6.0, 4.5.0 Environment: JBossJTA + DataSource with connection pooling (i.e.: DBCP) + Spring Reporter: Mauro Molinari Priority: Critical Attachments: patch.txt Suppose you are using JBossTS within you webapp, configured using Spring. Suppose you're doing connection pooling over JBossTS: that is, you have your data source with connection pooling managing connections obtained from the TransactionalDriver of JBossJTA. As of now, com.arjuna.ats.jdbc.TransactionalDriver.connect(String, Properties) is calling com.arjuna.ats.internal.jdbc.ConnectionManager.create(String, Properties) to get a connection. The latter is behaving like this: - if an "equivalent" connection has been already created, it's not closed and it is associated with the same transaction, return that connection - otherwise create a new one In other words, as stated by the comments in ConnectionManager source, this class is pooling connections for the duration of a transaction. This however this can lead to severe and hard-to-find problems when you're doing your own connection pooling above JBossJTA using a data source like DBCP. These are two scenarios in which problems can occur: 1) suppose you have two different data sources that are modeling two logically different databases. However, suppose you're configuring both of them to point to the same physical database (that is: same URL, same username, same password) and you're off course using the same dynamic class to drive the TransactionalDriver to the actual JDBC driver. Suppose transaction 1 (tx1) is started and, within its duration, a connection is asked to data source 1 (ds1) and another connection is asked to data source 2 (ds2). ds1 and ds2 are initially empty, so the request leads to the creation of two new connections, through TransactionalDriver.connect. Therefore, ds1 asks the TransactionalDriver for a new connection (conn1) and the TransactionalDriver asks the ConnectionManager to create it. conn1 is created and put into ds1, then made available to the client code. But also ds2 is requesting a new connection to the TransactionalDriver: this asks the ConnectionManager, which in turns realizes that it has been requested a connection for the same transaction (tx1), for the same URL, username and password and using the same dynamic class... then, instead of creating another connection (conn2), thanks to its pooling algorythm it returns again conn1, which then goes into ds2! Anyway, tx1 terminates without problems, because the physical database is actually the same. However, after tx1 has terminated and new transactions are created, because conn1 is in both ds1 and ds2, it may happen that ds1 gives away conn1 to be used for a transaction tx2 while ds2 gives away conn1 to be used for another concurrent transaction tx3. Then, during tx2 or tx3 execution the "Checking transaction and found that this connection is already associated with a different transaction!" error occurs. To work around this problem you could configure each data source to use a different implementation (that is, different class names!) of the dynamic class. However, another problem could still happen. 2) suppose you work around problem 1) by using a different dynamic class implementation for each data source. Now, suppose tx4 is started and, during its execution, a thread requests two different connections to ds1. Because of the pooling done by ConnectionManager, it may happen that ds1 receives conn1 twice from the TransactionalDriver, while thinking to receive two DIFFERENT connections. Now, suppose that the data source implementation can handle that without corrupting its internal data structures (and, based on my experiences with DBCP, I wouldn't bet on this!), however this causes conn1 to appear twice in ds1. Then, if tx5 and tx6 are two new concurrent transactions during which requests to ds1 are made, it can happen that conn1 is given to be used in both tx5 and tx6, producing again the already mentioned error. So, my request is to support a configuration like the one I described by adding the ability to disable connection pooling at transaction level completely. I'm attaching a suggested patch that provides this functionality by: - adding support for a connection property named POOL_CONNECTIONS_WITHIN_TRANSACTION wich is assumed to be "true" by default but that can be set to "false" as needed - changing ConnectionManager.create(String, Properties) to honour that property: if it is set to "false", pooling is disabled and a new connection is always created -- 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, 5 months

4
8
0 / 0

[JBoss JIRA] Created: (JBTM-223) Check WL-to-JBossTS interoperability (via JTS).

by Mark Little (JIRA)

Check WL-to-JBossTS interoperability (via JTS). ----------------------------------------------- Key: JBTM-223 URL: http://jira.jboss.com/jira/browse/JBTM-223 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTS Implementation 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

12 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBTM-649) Support XAException.XA_RETRY in 2 phase commit -- Backward Compatibility issue

by Howard Gao (JIRA)

Support XAException.XA_RETRY in 2 phase commit -- Backward Compatibility issue ------------------------------------------------------------------------------ Key: JBTM-649 URL: https://jira.jboss.org/jira/browse/JBTM-649 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.6.1 Reporter: Howard Gao Fix For: 4.6.1.CP04 After upgrading from 4.4.0 to 4.6.1 (release for AS5), one of the JBoss Messaging test starts to fail. The scenario is: 1. We have two XAResources res1 and res2. Both are enlisted in a Transaction. 2. res1 sends a message to Queue1 (server1), res2 sends a message to Queue2 (server2). 3. delist res1 and res2 and commit the transaction. 4. During the commit process, we simulate a failure on res2.commit() so that the res1.prepare(), res2.prepare() and res1.commit() are all successful but res2.commit() will throw XAException.XA_RETRY exception -- eventually leaving the transaction in a Heuristic state. 5. Then we restore res2 back to normal, hoping that the Recovery Manager will kick in and recover the transaction. So we expect that the two sent messages will be received by the receiver. To allow the recovery to happen we give a 60 second timeout to receive the second message. But the result is the first message is received but the second message isn't. We know that it is not JTA compliant. But some users may still rely on the old behavior to work. Suggestion: a system property can be provided to enable the old behavior if specified by user. -- 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, 7 months

5
11
0 / 0

[JBoss JIRA] Created: (JBTM-622) Support for crash recovery of tx-inflow with multiple resource managers

by Toshiya Kobayashi (JIRA)

Support for crash recovery of tx-inflow with multiple resource managers ----------------------------------------------------------------------- Key: JBTM-622 URL: https://jira.jboss.org/jira/browse/JBTM-622 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA, Recovery, Transaction Core Affects Versions: 4.7.0 Reporter: Toshiya Kobayashi JCA tx-inflow spec allows the external EIS to provide the Xid for the inflowed transaction. The TM handling the inflowed (i.e. subordinate) transaction uses this Xid verbatim when talking to RMs. In current implementation, each RM enlisted in the subordinate tx will see the same Xid as originally provided by the EIS. This screws recovery where multiple resources are involved, since a given Xid no longer belongs to exactly one RM, but may be shared by several. We can no longer return a single XAResource to drive the recovery for a given Xid. -- 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, 7 months

5
7
0 / 0

[JBoss JIRA] Created: (JBTM-259) Make sure the build system uses the version number

by Mark Little (JIRA)

Make sure the build system uses the version number -------------------------------------------------- Key: JBTM-259 URL: http://jira.jboss.com/jira/browse/JBTM-259 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Release Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Andrew Dinn Within the code we have some Info.java classes that are supposed to be able to give back important build-time information. Looks like that is being lost or incomplete these days: <module-info name="arjuna"><source-identifier>unknown</source-identifier><build-information>JBoss Inc. [kevin] (Linux 2.6.17-1.2157_FC5)</build-information><version>unknown</version><date>2006/Aug/04 15:26</date><notes></notes><configuration><properties-file dir=".">jbossjta-properties.xml</properties-file><object-store-root>/Users/bas/Documents/workspace/adhoc/ObjectStore</object-store-root></configuration></module-info> -- 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, 7 months

3
11
0 / 0

[JBoss JIRA] Created: (JBTM-477) ControlWrapper.getStatus rolledback status versus unknown

by Mark Little (JIRA)

ControlWrapper.getStatus rolledback status versus unknown --------------------------------------------------------- Key: JBTM-477 URL: https://jira.jboss.org/jira/browse/JBTM-477 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTS Implementation Affects Versions: 4.5 Reporter: Mark Little Assignee: Mark Little currently returns unknown since a remote transaction could be terminated (committed) by different threads, so OBJECT_NOT_EXIST may not mean 'rollback'. Could tie this into checked transaction semantics to get the definitive answer. -- 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, 8 months

5
15
0 / 0

[JBoss JIRA] Created: (JBTM-731) refactor qa tests to reduce code duplication

by Jonathan Halliday (JIRA)

refactor qa tests to reduce code duplication -------------------------------------------- Key: JBTM-731 URL: https://jira.jboss.org/jira/browse/JBTM-731 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.10.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.11.0 The qa tests include a massive about of almost but not quite identical code. Refactor to reduce duplication. -- 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, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBTM-264) Improve tooling

by Mark Little (JIRA)

Improve tooling --------------- Key: JBTM-264 URL: http://jira.jboss.com/jira/browse/JBTM-264 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Mark Little Priority: Critical We need better tools support. -- 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, 8 months

3
7
0 / 0

[JBoss JIRA] Created: (JBTM-741) Remove redundant XTS classes and code paths identified from coverage data

by Andrew Dinn (JIRA)

Remove redundant XTS classes and code paths identified from coverage data ------------------------------------------------------------------------- Key: JBTM-741 URL: https://jira.jboss.org/jira/browse/JBTM-741 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: XTS Affects Versions: 4.11.0 Reporter: Andrew Dinn Assignee: Andrew Dinn Fix For: future Coverage analysis of the XTS code base has idenitifed a lot of unexercised classes and code paths. These need pruning in order to simplify maintenance and testing. -- 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, 8 months

4
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues June 2010