June 2011 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-268) Change SynchronizationRecord so it is an AbstractRecord

by Mark Little (JIRA)

Change SynchronizationRecord so it is an AbstractRecord ------------------------------------------------------- Key: JBTM-268 URL: http://jira.jboss.com/jira/browse/JBTM-268 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Core 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

12 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBTM-856) Create an example showing rest-tx

by Tom Jenkinson (JIRA)

Create an example showing rest-tx --------------------------------- Key: JBTM-856 URL: https://issues.jboss.org/browse/JBTM-856 Project: JBoss Transaction Manager Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Documentation Reporter: Tom Jenkinson Assignee: Michael Musgrove Would be good to see participant enlistment with Rest-TX -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBTM-853) Optimize performance of code path for new TSR based integration for AS 7.

by Andrig Miller (JIRA)

Optimize performance of code path for new TSR based integration for AS 7. ------------------------------------------------------------------------- Key: JBTM-853 URL: https://issues.jboss.org/browse/JBTM-853 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Affects Versions: 4.15.1 Reporter: Andrig Miller Priority: Critical Fix For: 4.15.2 Attachments: AS7CR1.txt In testing the pre-AS7 CR 1 release, we found a performance regression, related to the following attached OProfile data. com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance(java.lang.Class) is the main method involved from the profile data. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBTM-536) JTS compilation with IBM jdk1.5 fails due to "Fatal Error: Unable to find package java.lang"

by Ivo Studensky (JIRA)

JTS compilation with IBM jdk1.5 fails due to "Fatal Error: Unable to find package java.lang" -------------------------------------------------------------------------------------------- Key: JBTM-536 URL: https://jira.jboss.org/jira/browse/JBTM-536 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS Environment: IBM JDK 1.5, Apache Ant 1.6.5, Linux Reporter: Ivo Studensky Fix For: 4.6.1 Compiler cannot find java.lang package in case of compiling with IBM JDK 1.5. See the snippet of compilation output: ... [java] com.hp.mwlabs.orbportability.orbspecific.jacorb.compile: [java] [echo] Performing JacORB IDL compile [java] [classpath-builder] Property 'build.jacorb.classpath' set to classpath ... [java] [echo] Performing JacORB orb specific compile [java] [javac] Compiling 11 source files to /mnt/hudson_workspace/workspace/jbossts-testsuite-matrix/jdk/ibm15/label/RHEL4_x86/trunk/ArjunaJTS/orbportability/orbspecific-build [java] [javac] Fatal Error: Unable to find package java.lang in classpath or bootclasspath -- 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, 10 months

2
8
0 / 0

[JBoss JIRA] Created: (JBTM-835) Split the XTS documentation from a single developers guide to two developer guides, one in /docs for product/project and one in /XTS/docs for project only

by Tom Jenkinson (JIRA)

Split the XTS documentation from a single developers guide to two developer guides, one in /docs for product/project and one in /XTS/docs for project only ---------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBTM-835 URL: https://issues.jboss.org/browse/JBTM-835 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Andrew Dinn Fix For: 4.15.0 The summary sort of says it really, not certain on the timeframe required so I dropped it into the 4.15 timeframe, please feel free to discuss and move the fix version as I appreciate it is close to the deadline! I have already done this for JTA/JTS based on Marks split so can do the same for XTS but I do not know what is community and what is common so would need some clear pointers on this if you want me to split the doc. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBTM-848) Upod

by Andrew Dinn (JIRA)

Upod ---- Key: JBTM-848 URL: https://issues.jboss.org/browse/JBTM-848 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Andrew Dinn -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
6
0 / 0

[JBoss JIRA] Created: (JBTM-575) javax.transaction.RollbackException root cause

by Richard Kennard (JIRA)

javax.transaction.RollbackException root cause ---------------------------------------------- Key: JBTM-575 URL: https://jira.jboss.org/jira/browse/JBTM-575 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Affects Versions: 4.7.0 Environment: JBoss 5.1.0.GA Reporter: Richard Kennard In JBoss 4.2.3.GA and previous releases, when a transaction rolled back the RollbackException included the root cause of the exception. This enhancement was implemented in response to JBAS-4238 and JBTM-66. However, in JBoss 5.1.0.GA this enhancement has been lost in some scenarios. This does not affect manual debugging (the root cause is still logged higher up in the logs), but makes it difficult for application code that relies on being able to unwrap the RollbackException to determine its root cause and therefore take appropriate action. -- 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

13 years

8
36
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues June 2011