June 2009 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-565) fix ExceptionInInitializerError usage

by Jonathan Halliday (JIRA)

fix ExceptionInInitializerError usage ------------------------------------- Key: JBTM-565 URL: https://jira.jboss.org/jira/browse/JBTM-565 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Application Server Integration, Common, JTA, JTS Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.7.0 For reasons beyond mortal understanding, ExceptionInInitializerError does not permit initCause() to be called. Remove such usage. -- 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] Closed: (JBTM-221) Improve WS-T example

by Andrew Dinn (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-221?page=com.atlassian.jira.plugi... ] Andrew Dinn closed JBTM-221. ---------------------------- Resolution: Done This has already been resolved by previous changes. > Improve WS-T example > -------------------- > > Key: JBTM-221 > URL: https://jira.jboss.org/jira/browse/JBTM-221 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator, XTS > Affects Versions: 4.2.3 > Reporter: Mark Little > Assignee: Andrew Dinn > Fix For: 4.7.0 > > > It would be nice if the various windows could be displayed outside of a browser, for example. -- 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
0
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-561) merge jbossts-common into jbossjta.jar/jbossjts.jar

by Jonathan Halliday (JIRA)

merge jbossts-common into jbossjta.jar/jbossjts.jar --------------------------------------------------- Key: JBTM-561 URL: https://jira.jboss.org/jira/browse/JBTM-561 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build System, Release Process Affects Versions: 4.6.1 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.7.0 As no other project consumes jbossts-common as an independent entity, it makes little sense to preserve it as such. For ease of embedding we should have all the files in a single .jar. Remove jbossts-common.jar and merge the contents into jbossjta.jar or jbossjts.jar according to distribution type. -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-562) clean up broken javadoc tags

by Jonathan Halliday (JIRA)

clean up broken javadoc tags ---------------------------- Key: JBTM-562 URL: https://jira.jboss.org/jira/browse/JBTM-562 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation, JTA, JTS, Transaction Core Affects Versions: 4.6.1 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.7.0 Some javadoc is broken and causes the doclet to whine annoyingly during builds. Placate it. -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-559) remove default properties from config file

by Jonathan Halliday (JIRA)

remove default properties from config file ------------------------------------------ Key: JBTM-559 URL: https://jira.jboss.org/jira/browse/JBTM-559 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.6.1 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.7.0 The jbossts-properties.xml is large and complex. There are many configuration options, but only a handful are changed from their defaults in most systems. We should remove the others from the properties file in order to reduce the clutter. -- 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, 6 months

1
1
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] Commented: (JBTM-44) Transaction bridging

by Jonathan Halliday (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-44?page=com.atlassian.jira.plugin... ] Jonathan Halliday commented on JBTM-44: --------------------------------------- Added support for Synchronization / VolatileParticipant phases, made possible by JBTM-560 > Transaction bridging > -------------------- > > Key: JBTM-44 > URL: https://jira.jboss.org/jira/browse/JBTM-44 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTA, JTS, XTS > Reporter: Mark Little > Assignee: Jonathan Halliday > Priority: Critical > Fix For: 4.8.0 > > Attachments: jbossxts-bridge.zip > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-564) TransactionReaper code is not waking up threads correctly

by Andrew Dinn (JIRA)

TransactionReaper code is not waking up threads correctly --------------------------------------------------------- Key: JBTM-564 URL: https://jira.jboss.org/jira/browse/JBTM-564 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.6.1 Reporter: Andrew Dinn Assignee: Andrew Dinn The code in TransactionReaper is using wait and notify to suspend and wake up threads contending to add and remove transaction controls and to manage transfer of expired controls between the main queue and the reaper worker queue. It should actually be calling notifyAll() since notify() only wakes up one thread and multiple threads may be queued. All occurences of calls to notify() need to be transformed to notifyAll(). -- 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, 6 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues June 2009