August 2011 - jbossts-issues - Jboss List Archives

[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

11 years, 12 months

5
7
0 / 0

[JBoss JIRA] Created: (JBTM-831) performance tweaks

by Jonathan Halliday (JIRA)

performance tweaks ------------------ Key: JBTM-831 URL: https://issues.jboss.org/browse/JBTM-831 Project: JBoss Transaction Manager Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Jonathan Halliday Assignee: Jonathan Halliday assorted performance tweaks -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 12 months

3
7
0 / 0

[JBoss JIRA] Created: (JBTM-849) registerSynchronization fails with from status message

by Carlo de Wolf (JIRA)

registerSynchronization fails with from status message ------------------------------------------------------ Key: JBTM-849 URL: https://issues.jboss.org/browse/JBTM-849 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.15.1 Environment: https://github.com/jbossejb3/jboss-as/tree/991e836c1bcb6b471010c5930fc3f5... Reporter: Carlo de Wolf Attachments: JBTM-849-stracktrace.txt registerSynchronization is called from within a beforeCompletion of another Synchronization. I would expect the status to be PREPARING (or anything but RUNNING). {noformat} java.lang.IllegalStateException: Synchronizations are not allowed! Transaction status isActionStatus.RUNNING at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.registerSynchronizationImple(TransactionImple.java:367) at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.registerSynchronization(TransactionImple.java:344) at org.jboss.jca.core.connectionmanager.transaction.TransactionSynchronizer.getRegisteredSynchronizer(TransactionSynchronizer.java:198) at org.jboss.jca.core.connectionmanager.listener.TxConnectionListener.enlist(TxConnectionListener.java:210) at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.managedConnectionReconnected(TxConnectionManagerImpl.java:407) ... 104 more {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 12 months

5
14
0 / 0

[JBoss JIRA] Created: (JBTM-830) Wrong character encoding in HTML rendering of documentation

by Sanne Grinovero (JIRA)

Wrong character encoding in HTML rendering of documentation ----------------------------------------------------------- Key: JBTM-830 URL: https://issues.jboss.org/browse/JBTM-830 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Reporter: Sanne Grinovero Priority: Optional Documents as http://docs.jboss.org/jbosstm/docs/4.2.1/manuals/html/jts/ProgrammersGuid... (but not limited to) are rendered with � symbols -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 12 months

2
4
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

11 years, 12 months

3
11
0 / 0

[JBoss JIRA] Created: (JBTM-855) Create an example showing integration with Tomcat and Spring

by Tom Jenkinson (JIRA)

Create an example showing integration with Tomcat and Spring ------------------------------------------------------------ Key: JBTM-855 URL: https://issues.jboss.org/browse/JBTM-855 Project: JBoss Transaction Manager Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Tom Jenkinson Priority: Minor Simple example showing TS in use by tomcat and spring -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
4
0 / 0

[JBoss JIRA] Created: (JBTM-865) Make sure REST-AT is covered in docbook

by Michael Musgrove (JIRA)

Make sure REST-AT is covered in docbook --------------------------------------- Key: JBTM-865 URL: https://issues.jboss.org/browse/JBTM-865 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: REST Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.0.0.M2 Include a section on REST-AT in docbook -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
1
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, 1 month

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, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBTM-851) Transaction timeout in JBoss caused deadlock with spring transaction manager

by Sergey Astakhov (JIRA)

Transaction timeout in JBoss caused deadlock with spring transaction manager ---------------------------------------------------------------------------- Key: JBTM-851 URL: https://issues.jboss.org/browse/JBTM-851 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Affects Versions: 4.14.0 Environment: JBoss 6, JBoss TS 4.14.0.Final, Hibernate 3.6.4.Final, Spring 3.0.5 Reporter: Sergey Astakhov Priority: Critical Deadlock scenario: 1. Transaction started. At some point, jdbc connection allocated from poll and registered as transaction resource. 2. After timeout event occured, JBoss try to rollback this transaction. 3. In process of rolling back transaction, reaper process try to get lock on connection to do rollback and stopped at this point in waiting. 4. Due to cancelling state of the transaction, exception is rised in main process of transaction. 5. Spring catched this exception and invokes rollback to transaction. 6. Inside jboss transaction manager there is synchronized method for making transaction abort, so this rollback invocation is waiting another thread to complete. 7. At final: JBoss hold synchronized lock on abort method, but wait for releasing lock on connection. Main process hold lock on connection, but wait for releasing lock on abort method. Deadlock state. How this can be fixed: Before trying to invoke abort method, check transaction state. If it is already in state of aborting - just rise IllegalStateException. I'm also suggest to add similar check in spring code (https://jira.springsource.org/browse/SPR-8421), but such check should be in jboss code too, because any client code can suddenly get into this deadlock state. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues August 2011