February 2009 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-270) Add the performance test suite

by Mark Little (JIRA)

Add the performance test suite ------------------------------ Key: JBTM-270 URL: http://jira.jboss.com/jira/browse/JBTM-270 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Mark Little Priority: Critical -- 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

15 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBTM-261) Integrate WS-TX interoperability work into QA

by Mark Little (JIRA)

Integrate WS-TX interoperability work into QA --------------------------------------------- Key: JBTM-261 URL: http://jira.jboss.com/jira/browse/JBTM-261 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Testing, WS-T Implementation Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Jonathan Halliday -- 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

15 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBTM-292) For all supported databases, provide associated XAResourceRecovery plugin

by Mark Little (JIRA)

For all supported databases, provide associated XAResourceRecovery plugin ------------------------------------------------------------------------- Key: JBTM-292 URL: http://jira.jboss.com/jira/browse/JBTM-292 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Recovery Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Andrew Dinn Priority: Critical Fix For: 4.4 MR1 Currently we only ship with the OracleXARecovery class, a generic JDBCXARecovery implementation and an example. It's possible the generic one will work for many of the other databases, but it probably hasn't been checked in a while. -- 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

15 years, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (JBTM-260) Make sure we ship the ORB Portability manual

by Mark Little (JIRA)

Make sure we ship the ORB Portability manual -------------------------------------------- Key: JBTM-260 URL: http://jira.jboss.com/jira/browse/JBTM-260 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.3.SP5 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

15 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBTM-419) Hardcoded "1.5" java version check in com\arjuna\ats\internal\jdbc\ConnectionManager.java won't work on Java 1.6

by Sergey Proskurnya (JIRA)

Hardcoded "1.5" java version check in com\arjuna\ats\internal\jdbc\ConnectionManager.java won't work on Java 1.6 ---------------------------------------------------------------------------------------------------------------- Key: JBTM-419 URL: https://jira.jboss.org/jira/browse/JBTM-419 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.4.0.GA Environment: Sun's J2SE DevKit 1.6u10 Reporter: Sergey Proskurnya Priority: Minor There is a hard-coded version check in com.arjuna.ats.internal.jdbc.ConnectionManager in "create (String dbUrl, Properties info)" method: -------------------------------------------------------------------------------------------------------------------------- ... line 116: if(System.getProperty("java.specification.version").equals("1.5")) { // the 1.5 (JDBC3) wrapper version is loaded dynamically because classloading // it on earlier versions of the platform is not possible. .... } -------------------------------------------------------------------------------------------------------------------------- That piece of code will not work correctly on Java 1.6, because System.getProperty("java.specification.version") returns "1.6" on Java 1.6. It is needed to parse the result of System.getProperty("java.specification.version") and compare major and minor versions separately. -- 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, 7 months

4
14
0 / 0

[JBoss JIRA] Created: (JBTM-481) update docs for 4.6

by Jonathan Halliday (JIRA)

update docs for 4.6 ------------------- Key: JBTM-481 URL: https://jira.jboss.org/jira/browse/JBTM-481 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.5 Reporter: Jonathan Halliday 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-493) New API for creatiing suordinate AT transacctions needs to be documented

by Andrew Dinn (JIRA)

New API for creatiing suordinate AT transacctions needs to be documented ------------------------------------------------------------------------ Key: JBTM-493 URL: https://jira.jboss.org/jira/browse/JBTM-493 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: WS-T Implementation Affects Versions: 4.5 Reporter: Andrew Dinn Assignee: Andrew Dinn Fix For: 4.6 Need to document UserTransaction.beginSubordinate() and UserTransaction.beginSubordinate(int timeout) -- 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, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-416) When running in a server the Recovery Manager does not reuse the servers' orb

by Michael Musgrove (JIRA)

When running in a server the Recovery Manager does not reuse the servers' orb ----------------------------------------------------------------------------- Key: JBTM-416 URL: https://jira.jboss.org/jira/browse/JBTM-416 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Application Server Integration Affects Versions: 4.4.0.GA Reporter: Michael Musgrove Assignee: Jonathan Halliday Fix For: 4.4.0.GA Start two servers on the same host but bound to different interfaces. The Recovery manager on the second server fails to start since it tries to create a new ORB on the default jacorb address (see JacOrbRCServiceInit.java) - ie it neither reuses the existing server orb nor does it bind to the jboss.bind.address. -- 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, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBTM-496) make beforeCompletion sync behaviour configurable

by Jonathan Halliday (JIRA)

make beforeCompletion sync behaviour configurable ------------------------------------------------- Key: JBTM-496 URL: https://jira.jboss.org/jira/browse/JBTM-496 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration, JTA Implementation, JTS Implementation Affects Versions: 4.5 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.6 The JTA and JTS/OTS specs are ambiguous with respect to the circumstances in which beforeCompletion synchronizations should be invoked. "The Synchronization.beforeCompletion method is called prior to the start of the two-phase transaction commit process. This call is executed with the transaction context of the transaction that is being committed." "The beforeCompletion method is called by the transaction manager prior to the start of the two-phase transaction commit process. This call is executed with the transaction context of the transaction that is being committed." Interestingly the change log for the JTA spec also includes this revision: "Interface javax.transaction.Synchronization, method beforeCompletion, change the following phrase in the description "start of the transaction completion process" to "start of the two-phase transaction commit process"." which could be read as implying that beforeCompletion should not be called when a transaction is being committed via a onePhase commit optimization. However, that interpretation makes little sense and is accordingly rejected - beforeCompletions will always be run before a xa resource commit in either phase. Nevertheless, that still leaves open the question of the intended behaviour in cases such as the sequence setRollbackOnly(); commit(); In general we take the view that beforeCompletions are intended to allow cached data to be flushed to stable store and thus invoking them when it is already known the transaction cannot commit, is a waste of time. However, this is considered an optimization rather than an absolute requirement. A more extreme view appears to be taken by the EJB spec and testsuite, which expects the beforeCompletion will definitely NOT run after a setRollbackOnly, although it seems to have little basis for this assertion. To allow for this ambiguity, the behaviour of the system should be configurable. -- 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, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-447) Implement tests for WS-AT subordinate transaction recovery

by Andrew Dinn (JIRA)

Implement tests for WS-AT subordinate transaction recovery ---------------------------------------------------------- Key: JBTM-447 URL: https://jira.jboss.org/jira/browse/JBTM-447 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: WS-T Implementation Affects Versions: 4.5 Reporter: Andrew Dinn Assignee: Andrew Dinn 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, 9 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 February 2009