February 2009 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-298) There is no way for recovery through JCA to indicate temporary failure to recover

by Mark Little (JIRA)

There is no way for recovery through JCA to indicate temporary failure to recover --------------------------------------------------------------------------------- Key: JBTM-298 URL: http://jira.jboss.com/jira/browse/JBTM-298 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.4 This means client-driven recovery sees a failure to recover and doesn't try again. We should give a "try again later" option (XA_RETRY). -- 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, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBTM-432) Authentication support on AppServerJDBCXARecovery plugin

by Tyronne Wickramarathne (JIRA)

Authentication support on AppServerJDBCXARecovery plugin -------------------------------------------------------- Key: JBTM-432 URL: https://jira.jboss.org/jira/browse/JBTM-432 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.2.3.SP5 Environment: JBoss-EAP-4.3_CP3, jdk 1.5.0_15-b04 Reporter: Tyronne Wickramarathne The present implementation of AppServerJDBCXARecovery plugin has a limitation on its usage when the invokers are secured. Hence, to overcome this limitation AppServerJDBCXARecovery plugin has to support authentication so this could be used even when the invokers are secured. -- 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, 4 months

4
12
0 / 0

[JBoss JIRA] Created: (JBTM-329) When BridgeParticipantAT receives prepare, participant should associate current thread with corresponding JTA transaction

by Pavel Kadlec (JIRA)

When BridgeParticipantAT receives prepare, participant should associate current thread with corresponding JTA transaction ------------------------------------------------------------------------------------------------------------------------- Key: JBTM-329 URL: http://jira.jboss.com/jira/browse/JBTM-329 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBoss-4.2.1.GA, JBossTS-4.2.3.SP7 Reporter: Pavel Kadlec When participant receives prepare from coordinator, it calls prepare on jta transaction. SubordinateAtomicAction.doPrepare then calls beforeCompletion() method. Hibernate registers Synchronization object which is called in beforeCompletion() method. In that synchronization object, when hibernate cannot find transaction on current thread, it flushes all entites into database, which is bad. When Hibernate cannot find transaction on thread, it logs WARN [AbstractEntityManagerImpl] Transaction not available on beforeCompletionPhase: assuming valid Fix is easy, BridgeParticipantAT should associate current thread with the corresponding JTA transaction. And finally it should suspend that JTA transaction. -- 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, 4 months

3
6
0 / 0

[JBoss JIRA] Created: (JBTM-484) Transaction timeout notifier

by Mark Little (JIRA)

Transaction timeout notifier ---------------------------- Key: JBTM-484 URL: https://jira.jboss.org/jira/browse/JBTM-484 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.5 Reporter: Mark Little Assignee: Mark Little Fix For: 4.7 Provide a means whereby listeners can be informed of timeouts. Should try to work with rollback-only too. -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-230) Put xaRecoveryNode in configuration

by Mark Little (JIRA)

Put xaRecoveryNode in configuration ----------------------------------- Key: JBTM-230 URL: http://jira.jboss.com/jira/browse/JBTM-230 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3.SP4 Reporter: Mark Little Assigned To: Mark Little Priority: Minor -- 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, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBTM-438) Consider flattening the property file (again)

by Mark Little (JIRA)

Consider flattening the property file (again) --------------------------------------------- Key: JBTM-438 URL: https://jira.jboss.org/jira/browse/JBTM-438 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.4.0.GA Reporter: Mark Little Assignee: Mark Little At one time the configuration file was relatively straightforward. Then we added support for nested scopes and dependencies between scopes. This is overkill these days, so we should consider going back to a nice straightforward property file. -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBTM-235) Check thread creation for context inheritance

by Kevin Conner (JIRA)

Check thread creation for context inheritance --------------------------------------------- Key: JBTM-235 URL: http://jira.jboss.com/jira/browse/JBTM-235 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Mark Little All threads created in the transaction manager should be checked to make sure they are not inheriting anything unexpected (classloader/thread locals etc) -- 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, 5 months

4
9
0 / 0

[JBoss JIRA] Created: (JBTM-281) Make sure docs and web page information about supported JDBC drivers is up-to-date

by Mark Little (JIRA)

Make sure docs and web page information about supported JDBC drivers is up-to-date ---------------------------------------------------------------------------------- Key: JBTM-281 URL: http://jira.jboss.com/jira/browse/JBTM-281 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: Jonathan Halliday 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBTM-365) addSynchronization calls during beforeCompletion are problematic

by Steven Hawkins (JIRA)

addSynchronization calls during beforeCompletion are problematic ---------------------------------------------------------------- Key: JBTM-365 URL: http://jira.jboss.com/jira/browse/JBTM-365 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.3.0.GA Reporter: Steven Hawkins Asynch calls to com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.addSynchronization during beforeCompletion are problematic since access to _currentRecord and _synchs is unsynchronized in addSynchronization wrt beforeCompletion. This is similar to JBTM-188. -- 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

4
12
0 / 0

[JBoss JIRA] Created: (JBTM-359) Transaction Bridging can timeout b ecause it bundles phase zero work into prepare

by Andrew Dinn (JIRA)

Transaction Bridging can timeout b ecause it bundles phase zero work into prepare --------------------------------------------------------------------------------- Key: JBTM-359 URL: http://jira.jboss.com/jira/browse/JBTM-359 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: WS-T Implementation Affects Versions: 4.3.0.GA Reporter: Andrew Dinn Assigned To: Andrew Dinn Fix For: 4.6 Bridged (from XTS to JTA) transaction synchronizations currently get executed at prepare time which can cause very long delays. This may cause the transaction coordinator to timeout the prepare or cause another participant to timeout. It would be better if the JTA brdge manager intercepted add synch requests and registered its own phase zero synchronization to run them. -- 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
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues February 2009