July 2008 - jbossts-issues - Jboss List Archives

[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-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-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

[JBoss JIRA] Created: (JBTM-297) Improve XID printing

by Mark Little (JIRA)

Improve XID printing -------------------- Key: JBTM-297 URL: http://jira.jboss.com/jira/browse/JBTM-297 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 Priority: Minor Fix For: 4.4 Printing the byte array through String loses information. -- 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-238) Add property to disable warning about multiple 1PC resources

by Mark Little (JIRA)

Add property to disable warning about multiple 1PC resources ------------------------------------------------------------ Key: JBTM-238 URL: http://jira.jboss.com/jira/browse/JBTM-238 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 Currently we always print a warning on multiple 1PC resources. Support for that has to be explicitly enabled. We print the warning in case the user set the wrong property, doesn't know the implications, forgot to set it back etc. For those users who never make mistakes and always know the implications, maybe we should have another property that basically means "only output warning once per VM run". -- 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

1
4
0 / 0

[JBoss JIRA] Created: (JBTM-257) Add more logging to participants when they fail

by Mark Little (JIRA)

Add more logging to participants when they fail ----------------------------------------------- Key: JBTM-257 URL: http://jira.jboss.com/jira/browse/JBTM-257 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Implementation, JTS Implementation, Transaction Core, WS-T Implementation Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Mark Little Customer request: "It would be very useful for us if the transaction manager would tell me on WARN level or INFO level which resource causes a roll back to happen. Applications run sometimes well for quite some time in PROD and suddenly there is a roll back and we have no hint why this happens." -- 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

1
3
0 / 0

[JBoss JIRA] Created: (JBTM-327) Memory leak bug in org.jboss.txbridge.TxBridgeManager

by Pavel Kadlec (JIRA)

Memory leak bug in org.jboss.txbridge.TxBridgeManager ----------------------------------------------------- Key: JBTM-327 URL: http://jira.jboss.com/jira/browse/JBTM-327 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 There is no way to dispose InboundBridge from memory in class org.jboss.txbridge.TxBridgeManager. There should be some method that does it. That method should be called from org.jboss.txbridge.BridgeParticipantAT when commit or rollback is received. -- 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
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues July 2008