October 2007 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Reopened: (JBTM-217) Contention on SychronizedMap in TransactionLocalDelegateImpl.java

by Jonathan Halliday (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-217?page=all ] Jonathan Halliday reopened JBTM-217: ------------------------------------ > Contention on SychronizedMap in TransactionLocalDelegateImpl.java > ----------------------------------------------------------------- > > Key: JBTM-217 > URL: http://jira.jboss.com/jira/browse/JBTM-217 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA Implementation > Affects Versions: 4.2.3 > Reporter: Phillip Thurmond > Assigned To: Andrew Dinn > Fix For: 4.3.0.BETA2 > > Time Spent: 1 day > Remaining Estimate: 0 minutes > > Under heavy loads, I'm seeing contention on the object map in TransactionLocalDelegateImpl.java. Can this variable be changed to use ConcurrentHashMap? -- 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

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBTM-104) Unify the way in which JTA default timeouts are set

by Jonathan Halliday (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-104?page=all ] Jonathan Halliday closed JBTM-104. ---------------------------------- Fix Version/s: 4.3.0.BETA2 (was: 4.4) Resolution: Duplicate Issue > Unify the way in which JTA default timeouts are set > --------------------------------------------------- > > Key: JBTM-104 > URL: http://jira.jboss.com/jira/browse/JBTM-104 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA Implementation, JTS Implementation, Documentation > Affects Versions: 4.2.1 > Reporter: Mark Little > Assigned To: Mark Little > Fix For: 4.3.0.BETA2 > > > Setting of default timeout values in local JTA and remote JTA use ArjunaCore or JTS properties. We should have a jta one too for consistency across different implementations. -- 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

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBTM-246) Release WS-Context implementation and re-factor

by Jonathan Halliday (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-246?page=all ] Jonathan Halliday reopened JBTM-246: ------------------------------------ > Release WS-Context implementation and re-factor > ----------------------------------------------- > > Key: JBTM-246 > URL: http://jira.jboss.com/jira/browse/JBTM-246 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: WS-T Implementation > Reporter: Mark Little > Assigned To: Mark Little > Fix For: 4.3.0.BETA2 > > > The ESB architecture has a notion of a message context. In Web Services, the standard approach for this is OASIS WS-Context. Although our ESB is not tied to Web Services, it makes sense that we should support WS-Context. We already have an implementation that has been tested for interoperability with IONA and Oracle, so this is a good starting point. It will need some updating to bring it in line with the latest version of the specification. -- 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

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-241) Improve tooling

by Mark Little (JIRA)

Improve tooling --------------- Key: JBTM-241 URL: http://jira.jboss.com/jira/browse/JBTM-241 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tooling Reporter: Mark Little Assigned To: Mark Little 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

17 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBTM-290) Check why CPU reaches 100% on recovery scans

by Mark Little (JIRA)

Check why CPU reaches 100% on recovery scans -------------------------------------------- Key: JBTM-290 URL: http://jira.jboss.com/jira/browse/JBTM-290 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Implementation Reporter: Mark Little Assigned To: Andrew Dinn -- 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

17 years, 3 months

2
3
0 / 0

[JBoss JIRA] Reopened: (JBTM-104) Unify the way in which JTA default timeouts are set

by Jonathan Halliday (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-104?page=all ] Jonathan Halliday reopened JBTM-104: ------------------------------------ > Unify the way in which JTA default timeouts are set > --------------------------------------------------- > > Key: JBTM-104 > URL: http://jira.jboss.com/jira/browse/JBTM-104 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA Implementation, JTS Implementation, Documentation > Affects Versions: 4.2.1 > Reporter: Mark Little > Assigned To: Mark Little > Fix For: 4.4 > > > Setting of default timeout values in local JTA and remote JTA use ArjunaCore or JTS properties. We should have a jta one too for consistency across different implementations. -- 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

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBTM-246) Release WS-Context implementation and re-factor

by Jonathan Halliday (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-246?page=all ] Jonathan Halliday closed JBTM-246. ---------------------------------- Fix Version/s: 4.3.0.BETA2 (was: 4.4) Resolution: Duplicate Issue > Release WS-Context implementation and re-factor > ----------------------------------------------- > > Key: JBTM-246 > URL: http://jira.jboss.com/jira/browse/JBTM-246 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: WS-T Implementation > Reporter: Mark Little > Assigned To: Mark Little > Fix For: 4.3.0.BETA2 > > > The ESB architecture has a notion of a message context. In Web Services, the standard approach for this is OASIS WS-Context. Although our ESB is not tied to Web Services, it makes sense that we should support WS-Context. We already have an implementation that has been tested for interoperability with IONA and Oracle, so this is a good starting point. It will need some updating to bring it in line with the latest version of the specification. -- 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

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-275) Make sure TransactionReaper doesn't wrap checkPeriod

by Mark Little (JIRA)

Make sure TransactionReaper doesn't wrap checkPeriod ---------------------------------------------------- Key: JBTM-275 URL: http://jira.jboss.com/jira/browse/JBTM-275 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 Fix For: 4.4 MR1 May no longer be applicable in 4.4 because of recent reaper changes. But check recent modification to _checkPeriod assignment in SP6 to be sure. -- 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

17 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBTM-273) Print statements in TransactionReaper should use debug stream

by Mark Little (JIRA)

Print statements in TransactionReaper should use debug stream ------------------------------------------------------------- Key: JBTM-273 URL: http://jira.jboss.com/jira/browse/JBTM-273 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: Andrew Dinn Priority: Minor Fix For: 4.4 MR1 There are some print statements in TransactionReaper. These should either be removed, or made to use the debug mechanism. -- 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

17 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBTM-249) Transactions Core Programmers Guide

by Daniel Bevenius (JIRA)

Transactions Core Programmers Guide ----------------------------------- Key: JBTM-249 URL: http://jira.jboss.com/jira/browse/JBTM-249 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Daniel Bevenius Assigned To: Mark Little Priority: Trivial I've been reading the Transactions docs and found a duplication of text on page 15 in the Transactions Code Programmers Guide. I'll attached the doc with the two sections highlighted. /Daniel -- 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

17 years, 3 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues October 2007